The situation
Fictional planning example. These are sample decisions, not customer results or a demonstration of a live configuration.
A fictional small service business receives opening-hours questions and appointment requests. The owner wants to start with one clearly defined job, rather than assuming every call needs the same configuration.
Sample intake record
Use the distinction between reported information and confirmed outcomes when reviewing your own process.
| Field | Sample entry | How to use it |
|---|---|---|
| Routine question | What time do you close on Friday? | Use current, owner-approved business information. |
| Primary appointment need | A caller wants to request a first visit. | Identify required details and eligible appointment types. |
| Availability | No suitable slot has been confirmed yet. | Do not describe a request as a booked appointment. |
| Exception | Caller asks about a service outside the approved list. | Needs an owner answer rather than an invented service promise. |
| Starting scope | Compare reception and appointment-booking use cases. | Confirm the selected package’s scope with the team before purchase or setup. |
Walk through the decisions
- Name the primary job. Decide whether the first project is mainly about answering common questions and taking messages, or about a supported appointment path.
- Compare the published starting points. Use the selector to organize the discussion. Its recommendation is a planning aid; it does not activate service or guarantee that every requested feature is included.
- Gather the business choices. Prepare the greeting, current hours, approved services, intake questions and human fallback. Confirm any booking connection and required access during sales-assisted setup.
- Walk through an exception. Test what happens when the service is outside scope or the caller cannot accept an offered time. Agree on the message and owner route before launch.
Example handoff note
Primary need: first-visit appointment requests. Secondary need: approved hours/service answers. Open decisions: appointment eligibility, supported calendar setup and unavailable-owner fallback. No appointment or package configuration is confirmed by this worksheet.
When the routine path does not fit
- Most calls turn out to be simple questions: Revisit reception as the initial use case rather than adding unnecessary booking complexity.
- A caller needs something outside the package: Document the request and confirm scope separately; do not imply an upgrade or custom integration is automatic.
- No appointment fits: Offer the approved message or human follow-up route and keep the request visibly unconfirmed.
Use this with your team
Which job matters first? What must the caller provide? Which answers are approved? What does the selected package include, and what needs a separate discussion?
Replace the fictional choices with your approved process before configuring service. This page does not collect or send your answers.