Map the client's top call reasons before you write a word
List why customers call this business before you write the call flow.
Read the lesson
Goal: Build a call map. It lists why customers call, how often, and what the AI agent does with each reason.
You need: Access to the client's call log or a week of call notes. No plan level needed. Read Operations Audit lesson 5 first.
Why this matters
Most bad AI receptionists fail for one reason. The Operator wrote the agent before learning why people call. The agent then sounds polite but does the wrong thing.
The money is real. Home service businesses miss 14% to 27% of their calls. Fewer than 3% of callers sent to voicemail leave a message. When a call is answered, about 42% of calls book a job across all trades.
Why every missed call matters
Take Northside Plumbing. The audit found 25 calls a business day and a 14% miss rate. Over 22 business days, that is 77 missed calls. At a 42% booking rate, that is about 32 jobs. At $380 a job, that is about $12,289 at risk each month.
What Northside's missed calls cost
The AI agent can catch those calls. It can only book them if it knows what each caller wants. The call map tells it.
What a call map is
A call map is a one-page table. Each row is one reason people call. Each row has four columns:
| Column | What goes in it |
|---|---|
| Reason | The caller's goal in plain words, such as "burst pipe" |
| Share | How many calls out of 100 have this reason |
| Outcome | One action: book, escalate, answer, take a task, or end politely |
| Owner rule | The words or limits the owner sets for this reason |
Every reason gets exactly one outcome. Two outcomes on one row confuse the agent. If a reason needs two paths, split it into two rows.
The five outcomes mean this:
- Book: The agent checks the calendar and books the visit.
- Escalate: The agent sends the call live to a person with
Transfer to your team. If nobody answers, it takes details for a fast call back. - Answer: The agent answers from approved facts and ends the call.
- Task: The agent takes details and creates a follow-up task for the office.
- End politely: For spam, sales calls and wrong numbers.
One outcome for every call reason
- Caller says why they calledThe agent matches one call map row
- Is it on the emergency row?YesEscalate with Transfer to your teamEnds hereNoCheck the next outcome
- Is it a Book row?YesCheck the calendar and bookEnds hereNoCheck the next outcome
- Can approved facts answer it?YesAnswer, then offer to bookEnds hereNoCheck the next outcome
- Is it spam, a vendor or a wrong number?YesEnd politelyNoCreate a task for the office
- Every call ends with one outcome
Spam and vendor calls still get a row. If they are not on the map, the agent may try to book them.
How to sample calls by business size
The sample size depends on the business.
- Owner-operator (1 to 3 people): Tag the last 50 calls. These owners often take calls from a truck, so ask what they hear most.
- Fleet (10 to 30 techs): Tag 100 to 200 calls across a full week. Include nights and weekends. Ask the dispatcher, not only the owner.
- Multi-location: Build one map per location first. Then merge rows that match. Keep local rules, such as service areas, on separate rows.
Always include after-hours calls. Owners often think nights are quiet. HVAC businesses get 9.8% to 14.1% of their calls outside business hours, depending on the month.
Tag calls fast
Tagging 100 calls sounds slow. It takes about an hour once you have a method.
- Read only the first 30 seconds of each call. The reason almost always shows up there.
- Write the reason as the caller says it, then group later. "Toilet won't stop running" and "running toilet" become one row.
- Mark the time of day next to each call. You need it in lesson 10, when you plan for busy hours.
- Mark any call where the caller sounded scared or angry. These calls often belong on the emergency row.
- Do not judge outcomes while you tag. Agree outcomes with the owner afterward.
Turn the map into build priorities
The map is also your work plan. Sort the rows by share, biggest first. Build and test the top three rows before anything else. On most maps, the top three rows cover more than half of all calls.
Then sort by risk. The emergency row is rarely the biggest, but a mistake there can hurt someone. Give it the most test calls, even if it is only 9 of 100.
Rows with the outcome "Task" are cheap to build. The agent takes details and creates a task for the office. Build them last, but never skip them. A caller who gets a clear promise of a call back stays calm.
Which call map rows to build first
Build it in ServiceAgent
You do not build the map inside the app. You build it first, then use it in every later lesson.
- Ask the client for last month's call log, with nights and weekends included.
- If the client already forwards calls to ServiceAgent, open
Voice Agentsand read recent call transcripts. You can also checkAnalytics→Callsfor volume by hour. - Read or listen to each call. Write one reason per call in a spreadsheet.
- Group the reasons. Aim for 6 to 10 rows. Put rare reasons under "Other" with the outcome "Task".
- Count the share of each row out of 100.
- Sit with the owner and the person who books jobs today. Agree one outcome per row.
- Write the owner's rule for each row in their own words. For emergencies, get clear cases, not "anything urgent".
- Date the map and get the owner's written yes.
- Check it works: pick 5 random calls from the log. Each one must fit exactly one row.
Worked example: Northside Plumbing
You tag 100 calls from Northside's log. The map below shows the result, sorted by share. Each row has one share and one outcome.
Northside Plumbing call map
| Reason | Share | Outcome |
|---|---|---|
| New repair request (leak, clog, no hot water) | 38 | Book |
| Reschedule or cancel | 12 | Book |
| Price question | 11 | Answer, then offer to book |
| Emergency (burst pipe, sewage backup) | 9 | Escalate |
| "Where is my tech?" | 8 | Task |
| Water heater replacement quote | 7 | Book an estimate visit |
| Vendor or spam | 6 | End politely |
| Billing question | 5 | Task |
| Other | 4 | Task |
Now read the map. Book rows are 38 + 12 + 7 = 57 calls. Add the 11 price calls that can end in a booking. The agent can finish about 68 of 100 calls without a person. Escalate is only 9 of 100. Task rows are 8 + 5 + 4 = 17.
What the agent can finish alone
- Book or answer68
- Task for the office17
- Escalate to a person9
- End politely6
Calls tagged100
This tells you where to spend your build time. The booking flow matters most. The emergency row needs the most care, because it is about safety.
Common mistakes
- Writing from the owner's memory only. Owners remember the dramatic calls. Fix: count real calls from the log.
- Leaving spam off the map. The agent then tries to book vendors. Fix: give spam its own row with a polite close.
- Two outcomes on one row. "Book or transfer" confuses the agent. Fix: split the row by a clear test, such as "water on the floor now".
- Skipping after-hours calls. Night calls are often the urgent ones. Fix: sample nights and weekends every time.
- No date and no sign-off. Months later, nobody knows who agreed to what. Fix: date the map and get the owner's written yes.
Do this now
Take one real or practice business. Tag 50 calls, or 20 if you only have notes. Build the four-column map with 6 to 10 rows. Check that the shares add up to 100. Write one sentence on which row needs the most build time, and why.
Practice the conversation
- Operator Before I set anything up, I want to know why people call you.
- Owner Mostly repairs. You know, plumbing stuff.
- Operator Can you send me last month's call log, nights and weekends too?
- Owner Nights are quiet. Do you need those?
- Operator Yes. Night calls are often the emergencies, so I need to see them.
- Owner Fine. What do you do with it?
- Operator I sort 100 calls by reason. Then you tell me what the AI does with each one.
- Owner And emergencies?
- Operator You give me the cases in your own words. The AI sends those straight to your on-call person.
- Owner Good. I don't want it guessing.
Quick check
- You tag 100 calls for a plumbing shop. 6 are vendor calls and spam. What do you do with them?
- Give them their own row, with a polite way to end the call
- Leave them off the map, because they never become jobs
- Mark them "book" so the agent offers each a visit
- Send each one to the owner's cell so they can decide
- A map row says "Water in basement: book or transfer". What is the problem?
- Water calls should always go to voicemail
- The row has two outcomes, so the agent cannot choose
- The share is missing a percent sign
- Basement calls belong under "Other"
- A 20-tech HVAC fleet sends you only business-hours calls. Which sample do you ask for?
- The 50 most recent business-hours calls
- The owner's list of common calls from memory
- 100 to 200 calls across a full week, nights and weekends included
- Only the emergency calls from last winter
ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.