- Available appointments
- Documented invoiced value
- Available travel fees
Start with the situation that most closely resembles your week.
An option is added, a referral code is presented, a visit changes position, a past appointment must be found, a response needs follow-up, a number changes, or an assumption needs to be tested. Each case shows what needs to be checked, what MapMyStaff lets the team review or adjust, and the limitation to keep in mind.
The customer adds an option. Does the selected period still work?
Services and options affect appointment duration and feasibility. An option can add time or a constraint and become incompatible with the selected period.
The customer selected a period, then adds an option that increases the required time.
Duration, selected period, availability, employee, service area, and travel must remain compatible with the request.
The workflow connects address, territory, period, employee, duration, travel, services, options, and validations before confirmation.
Final validation is checked again server-side before confirmation. If the context or rules no longer allow the option, it must be refused cleanly.
The request can continue toward final verification.
A new customer presents a code. Is the discount eligible — and what happens to the referrer’s reward?
The code is checked against program rules before an eligible referred-customer discount changes the booking. The referred-customer discount and the referrer reward remain two separate decisions.
A referral code is presented during the booking workflow.
Program status, dates, eligibility, duplicates, self-referral, and applicable limits must satisfy the configured rules.
The system checks the code before the discount. At closeout, the referral record can begin as pending; reward payment remains a separate state.
Applying the referred-customer discount does not mean the referrer reward has already been paid.
An appointment is moved. Compare the day’s order before applying it.
Changing a visit’s position changes the day’s sequence as well as the times, distances, and appointment times recalculated from the retained order.
A visit changes position in a day that has already been prepared.
Exact stop order, breaks, travel times, distances, and recalculated appointment times should be reviewed before applying the plan.
The office can reorder appointments, recalculate the day, and compare the sequence before retaining the schedule.
The schedule changes only after dispatcher confirmation. Distances and times remain estimates based on calculated routes.
You need to find a past visit. Open the specific appointment from the history.
The Customer Directory lets the team start from the customer record, review the history, and open a recorded appointment to read the available detail.
A past intervention must be found in a customer’s history.
Customer identity, recent activity, available history, and the relevant appointment help place the record in context.
Appointments in the history are clickable and can open the appointment document with recorded data, including package, option, employee, and payment status when those fields exist.
The Directory displays data recorded in the customer record and appointment, so the reading depends on the information that is actually available.
- Service
- Regular cleaning
- Status
- Completed
- Associated employee
- Employee recorded on the appointment
A response needs follow-up. What has been handled — and what is still waiting?
When a response requires follow-up, the management centre lets the team review the record, its status, and the latest recorded action, then see which records remain open or overdue.
A reviewed response requires follow-up in the management centre.
Available context, Urgent or Watch category, status, latest action, author, time, and backlog help the team review recorded progress.
The management centre shows, among other things, open records, handled records, records marked recovered, overdue backlog, and the latest action.
A workflow status describes progress on the record; by itself, it does not prove that the customer actually returned.
A number has changed. How far can you go into the detail before drawing a conclusion?
The Financial Dashboard puts invoiced values alongside available operational data in the same scope and signals when the available detail does not support a finer reading.
An invoiced value or metric in the active scope shows a difference that deserves review.
Scope, freshness, close state, worked time, travel, bookings, cancellations, and available detail should be reviewed before drawing a conclusion.
The Operations view relates these data points to other indicators in the scope; the Detail view can go by month, employee, territory, package, or option when the granularity allows it.n/a, unavailable, partial, or overall view only indicate when the required detail is not available.
Operating profit remains equal to total revenue while some costs are not deducted, and margin can therefore appear artificially high. An observed difference is not automatically a cause.
- Overall view
- Breakdown by employee, territory, or package when available
- Simplified operating profit and margin
n/a- Unavailable or partial
- Overall view only
The structure shows invoiced value, available detail, and the limitations signalled by the module.
You are considering a change to volume, price, or capacity. What does the scenario show?
The Growth Simulator starts from an explicit historical reference, applies the selected assumptions, and presents simulated results together with scenario capacity and limits.
A decision needs to be tested before operations change: volume, price, cost, capacity, route, or territory according to the supported levers.
Active reference, modified assumption, simulated result, and scenario capacity should remain distinct throughout the comparison.
The module compares a reference — an exact closed month or historical average — with assumptions and simulated results, and keeps any capacity exceedance visible.
A scenario is not a guaranteed forecast. Its reading depends on the reference, available data, assumptions, and the model’s methodological limits.
Start with the situation that most closely resembles your week.
Bring one service, one important rule, and one recent case. They will serve as the basis for verifying the most relevant behaviours during the demo.