The office manager at a small electrical contractor gets a vendor's setup form with one big box: “Describe how you'd like calls handled.” She writes: be friendly, book jobs, transfer important calls.
Two weeks later, the assistant has booked a panel upgrade into a 30-minute slot and transferred a sales call to the owner while he was on a roof. It did exactly what it was told. It just wasn't told much.
Why vague instructions fail
People fill gaps with judgment built over years at your front desk. An assistant fills gaps with guesses. The fix isn't a longer description of your business; it's turning each wish into a rule with a number, a list or a phone number attached.
Before and after
A vague script vs. one it can follow
Wishes
- 01“Be friendly and helpful.”
- 02“Book appointments when possible.”
- 03“Transfer important calls.”
- 04“Answer questions about our services.”
ResultGuesses at every turn
Rules
- 01Exact greeting, with “automated assistant” in the first sentence
- 02“Book 90-minute estimates Tue–Thu, 8–11 AM, in these ZIP codes”
- 03“Burning smell, sparks or a hot panel: safety line, then [on-call mobile]”
- 04“Answer only from the FAQ list; otherwise take a message”
ResultPredictable calls you can check
The seven-part template
Copy this into a document and fill in the brackets. The examples come from three very different front desks: a small law firm, an electrical contractor and a dental practice.
1. Greeting and disclosure
Word for word, under 20 seconds: “[Business], this is the automated assistant. Calls are recorded so we get your details right. What can I help you with?” The disclosure and recording notice come first; the legal overview explains why. The legal points in this post are general background, not legal advice; disclosure and recording rules differ by state.
2. Call types
List the five to eight reasons people call, with the phrases they actually use. The assistant matches callers to these, and anything that matches none goes to a person: a transfer in office hours, a message with a summary after.
| Business | Call type | What callers say |
|---|---|---|
| Law firm | New matter | “I need a lawyer,” “I got served,” “Do you handle DUIs?” |
| Law firm | Existing client | “I'm calling about my case,” “Is my hearing still on?” |
| Electrician | Service call | “Half my outlets stopped working,” “The breaker keeps tripping” |
| Electrician | Estimate | “I want an EV charger,” “How much for a panel upgrade?” |
| Dental | Booking | “I need a cleaning,” “Are you taking new patients?” |
| Dental | Change | “I need to move my appointment,” “I'm running late” |
Then give each call type its own card. Copy this skeleton once per call type and fill in every bracket; the example column shows one finished card.
| Field | Fill in | Example: electrician service call |
|---|---|---|
| Call type | [name] | Service call |
| Callers say | [3–5 real phrases] | “Outlets stopped working,” “breaker keeps tripping” |
| Must ask, in order | [questions] | Burning smell, sparks or heat? Name, address, callback number, what's happening |
| Never ask or say | [topics] | Diagnoses, prices not on the approved list, breaker or wiring steps |
| Book | [type, length, days and hours, ZIP codes] | 90-minute service visit, Mon–Fri 8 AM–3 PM, listed ZIP codes |
| Escalate if | [triggers] → [direct number], backup [number] | Any safety word → safety line, then on-call mobile; backup owner |
| Close with | [read-back and next step] | Address, time window, confirmation text |
3. Intake questions by call type
For each call type, write the must-ask questions in order, plus a never-ask list. Keep must-ask short: every extra question is another chance for the caller to give up.
- Electrician service call: name, address, callback number, what's happening, and whether there's a burning smell, sparking or heat. A yes plays the safety line in section 5 and fires the escalation rule before anything else.
- Law firm new matter: name, contact details, who's on the other side (people or businesses), type of matter, any court date or deadline. Never the story yet; conflicts come first.
- Dental new patient: name, date of birth, contact details, reason for the visit, insurance plan name. Nothing about symptoms beyond what the emergency rules need.
4. Booking rules
Write limits, not preferences: each appointment type with its length, the days and hours it can go, the buffer between jobs, service-area ZIP codes, how far ahead people can book, and what always needs a person to confirm, such as any estimate over two hours or a new patient asking about sedation.
5. Escalation rules
Each rule has a trigger and a destination. Triggers: safety words, named key clients, an upset caller, anyone who asks for a person, and any question the assistant fails to understand twice. Destinations must be direct numbers that don't forward to your main line, or the transfer loops straight back to the assistant.
| Trigger | What the caller might say | What happens first | If no one answers |
|---|---|---|---|
| Electrical safety | “Burning smell,” “sparks,” “the panel is hot” | Safety line, then transfer to the on-call electrician's mobile | Owner texted; caller told when to expect a call |
| Key client | Property manager or general contractor on your list | Transfer to the owner's mobile | Message marked priority |
| Asks for a person | “Can I talk to someone?” | Transfer to the office direct line | Callback within two business hours |
| No match, or confused twice | Assistant can't place the request | Transfer to the office direct line in office hours | Message with the call summary |
| Dental: swelling with trouble breathing or swallowing | “My face is swelling and it's hard to swallow” | Your dentists' approved emergency-room wording, read word for word | Call logged for the dentist |
| Dental: knocked-out permanent tooth | “His front tooth came out at practice” | Transfer to clinical staff now | On-call dentist paged |
| Law firm: arrest or court date tomorrow | “My son was arrested tonight” | Alert the on-call attorney | Caller told when to expect a call |
6. Approved answers
Your FAQ in short answers you'd stand behind: hours, service area, insurance plans you accept, payment methods, parking. The assistant answers from this list and nothing else. That isn't caution for its own sake. In Moffatt v. Air Canada (2024), the airline had to pay a customer who relied on incorrect bereavement-fare advice from its own chatbot. Whatever your assistant says, your business said.
Then write the line for questions that aren't on the list, because it will be used every day: “That's a good question for [owner or office manager]. I'll pass it on with your number, and someone will call you back [today / tomorrow morning].” A clear handoff sounds far better to a caller than an improvised answer.
7. Closing
Read back the essentials, say what happens next and send a text: “You're booked for Tuesday at 9 AM at 14 Elm Street. You'll get a confirmation text in a minute, and the electrician will call when they're on the way.”
Keep one version of the truth
Store the script as a single shared document with one owner, usually the office manager, and a date at the top. When hours, prices or staff change, the owner updates the document first and the assistant second, never the other way round. A short change log at the bottom (“March 3: added Saturday estimates”) makes it easy to tie a strange call to the edit that caused it.
How the script runs on a live call
Flowchart
One call through the seven-part script
- StartGreeting with disclosure and recording notice
- Step“How can I help?” The assistant listens for triggers and call types
- DecisionEscalation trigger heard?YesA personSafety line if needed, then live transfer to the number on your listNo
- DecisionMatches a known call type?NoA personTransfer to the office line; after hours, a message with a summaryYes
- StepAsks that call type's must-ask questions, in order
- DecisionBooking allowed by your rules?NoStepDetails collected; staff confirm by textYes
- StepReads back the details, books and sends the confirmation
- DoneCall summary lands with your team
Notice that escalation is checked before intake. A caller who mentions a melted outlet in their first sentence shouldn't have to spell their street name before reaching a person.
Try to break it before your customers do
Call the assistant yourself, then have two colleagues do the same, and work through this list. Note every miss and fix the script, not the caller.
- 01Make two requests at once: “I need to reschedule, and I have a question about my bill.”
- 02Mumble your address, then correct it halfway through.
- 03Ask, “Am I talking to a real person?”
- 04Ask for a price that isn't in the approved answers.
- 05Mention an emergency casually: “Oh, and the outlet looks a bit melted.”
- 06Sound angry and demand the owner.
- 07Hang up mid-booking, then call straight back.
- 08Call from a noisy truck or a busy kitchen.
- 09Ask a legal or medical question: “Do I have a case?” “Is this swelling serious?”
- 10Ask to book outside your hours or service area.
Run the drill again after every script change, and listen to a handful of real calls each week for the first month. The misses you hear tell you which part of the template needs another line. If you'd like help turning your front desk's habits into rules, that's how our AI receptionist setups begin.