- Caller
- “Y’all closed? I need somebody out this week.”
- Desk
- “We can take care of that. Let me get your address and the best callback number, and I’ll hold the first supported window.”
- The limit
- Booking happens only where the calendar truly supports it—otherwise the desk records a callback request for your named person.
- Caller
- “Just tell me what it costs.”
- Desk
- “I can share a posted fee only if it is on this company’s approved fact sheet. An estimate for your job needs a person. I’ll capture what you need and request a callback.”
- The limit
- Approved routine facts, such as a posted service-call fee, may be repeated when supplied. Estimates, discounts and pricing decisions stay with a person; no fee is invented in this example.
- Caller
- “Something’s burning—I don’t know what to do.”
- Desk
- “I’m trying the person assigned to urgent calls. If they cannot connect, I’ll tell you and record your callback details. This service cannot dispatch emergency help.”
- The limit
- Hazard language leaves routine scripting for the approved escalation route. If a person cannot accept the call, the desk states that clearly and records a callback request without promising a response time. No advice, troubleshooting or emergency dispatch.
Fictional, scripted demonstration. A real deployment answers only from facts your business approved, and every route is tested with you before launch.