Give customers a clear way to request or book the right time. Ember configures the selected calendars, service rules and messages around how your business actually schedules work.
Requested — not confirmed
Team checks the request and confirms the arrangement.THE RULES BEFORE THE SLOT
A useful booking system needs more than an open time slot. Appointment types, durations, team availability, buffers and conflict calendars determine which times should be offered.
Ember configures the selected booking path around those rules. The customer-facing page and messages need to describe the outcome accurately.
A request and a confirmed appointment are different outcomes.
Example appointment request · Fictional scenario · No calendar is connected.
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | 6 | 7 |
| 8 | 9 | 10 | 11 | 12 | 13 | 14 |
| 15 | 19 | 20 | 21 | |||
| 22 | 23 | 24 | 25 | 26 | 27 | 28 |
| 29 | 30 |
Requested — not confirmed
Tuesday, 16 June · 10:00 AM
Team checks the request and confirms the arrangement.
Try a date or time. This changes the example only; availability is not checked and no appointment is submitted.
Customers should know whether they submitted a request or secured a confirmed appointment. The page, assistant and messages must describe the same status and explain the next step accurately.
A request-only flow needs different wording from a system that immediately confirms an eligible time. An appointment can be a consultation, inspection or service visit. Booking that time does not automatically confirm the final job scope or price; we agree what each appointment means for your business.
The team may still need to check eligibility, timing or another detail. Say what is awaiting review and who will respond.
Use confirmation wording only when the selected system has actually recorded the eligible appointment. A selected time alone is not that evidence.
Fictional unavailable-time example
This example time is unavailable. Choose another displayed time or contact the team.
In a real setup, the next step follows the current calendar rules. This illustration does not check availability or connect to a calendar.
The selected setup starts with your actual services and calendar process. These are decisions to agree, not preset values or promised integrations.
Confirmations, reminders, cancellations and rescheduling need to follow your actual policies. The selected scope defines the permitted actions, customer instructions and person responsible for exceptions.
Help the customer choose the appointment that matches their need. Explain any information the team requires before it can review or confirm that request.
Apply the agreed availability, duration and conflict rules. Include a clear next step when no suitable time is available or a request needs manual review.
Check what the selected system has actually recorded. Keep a preferred time, a submitted request and a confirmed appointment distinct in the customer-facing status.
Tell the customer what happens next and where to ask for a change. After a cancellation or reschedule, the appointment status and selected messages should remain consistent.
Review available times, blocked times, overlapping calendars and changes before release. Check the record created by a successful booking and the message a customer receives when a time cannot be used. Your team also needs to know who reviews pending requests and how to handle a cancellation or reschedule that requires manual help.
The proposal confirms the selected booking and communication scope.
The selected setup uses the agreed availability and calendar rules. We verify working hours, buffers and relevant conflicts for the actual implementation. Where team review is still required, the customer should see a request status rather than an immediate booking confirmation.
A selected booking path can be used when its channel actions and calendar rules are supported and tested.
The options depend on your policies and selected setup. We agree which changes customers can make, when a person must help, and what confirms that the appointment record has changed. Reminders and customer instructions need to follow the updated status.
Bring your appointment types and current calendar process. We will walk through the rules your setup needs to respect.
Book a demo