A service menu is the receptionist's operating contract. If it contains ambiguous names, missing durations, or stale staff rates, the agent will inherit those problems even with a carefully written prompt.
Inventory the current menu with the salon owner or booking lead. Identify services eligible for direct booking, services that require consultation, and enquiries that should go to staff. Preserve technical service decisions with qualified salon professionals.
Build a service definition staff can approve
For each service, record a stable identifier, customer-facing name, approved description, eligible staff, location, planning duration, price meaning, prerequisites, and exception route. Store aliases separately so callers can use ordinary language without creating new menu items.
Distinguish fixed prices from ranges and starting prices. Include effective dates and an owner for updates. A broad service called “colour” may be suitable for an enquiry category while remaining too ambiguous for direct scheduling.
Work through a fictional menu cleanup
A salon has three similarly named cut services used by different staff tiers. One old item is hidden in the website but still active in the scheduling backend. The receptionist's initial menu import includes all four.
Before launch, staff identify the approved current services and map each rate and duration. The obsolete item is excluded from the booking allowlist. Test calls confirm that asking for the old service name produces clarification or staff routing rather than a stale-price appointment.
| Menu check | Acceptance evidence |
|---|---|
| Similar service names | Clear disambiguation rule |
| Staff eligibility | Correct service-to-stylist mapping |
| Prerequisite required | Dependent workflow defined |
| Price varies | Applicable context and approved wording |
| Retired service | Not directly bookable |
| Unsupported scope | Owned consultation or callback route |
Test the menu through actual conversations
Use fictional calls that ask for services by nickname, change scope, request an unavailable stylist, and cite an old promotion. Inspect resulting records, not just spoken answers. Confirm that the final service identifier matches the approved menu.
A detailed menu takes time to maintain. A small allowlist of common services can be easier to launch and verify, with staff handling exceptions. Expand when reviewed requests show a repeatable need and the corresponding rules are ready.
Assign a change owner and rerun affected cases when prices, durations, staff, or prerequisites change. Review appointment state boundaries before allowing direct booking for newly added services.
Questions about menu onboarding
Can the agent invent a menu match from a description?
It can apply approved aliases and clarification rules, but it should not create a new technical service or select an unsupported substitute.
Should every service launch at once?
No. Start with the services whose rules and recovery paths can be verified.
What is the most consequential onboarding mistake?
Treating a familiar service label as complete configuration. The identifier, staff eligibility, duration, pricing meaning, and prerequisites all affect the real booking.