Skip to content

Call Handling Playbooks

Mapping Your Call Flow: From Ring to Resolution

Map your business call flow: list every call type, give each an outcome, draw paths by time of week, find the dead ends where callers get lost, then test.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing8 min read

On this page
  1. Follow real calls, not the diagram
  2. Step 1: list every kind of call you get
  3. Step 2: give every call type an outcome
  4. Step 3: draw the path for each part of the week
  5. Step 4: find the dead ends
  6. Example: one call type mapped end to end
  7. Step 5: test the map with real calls
  8. Keep the map where people use it
  9. Frequently asked questions
  10. References
Call Handling Playbooks: Mapping Your Call Flow: From Ring to Resolution30%: of employed people in the US worked on an average weekend day in 2025, against 81% on a weekdayCALL HANDLING PLAYBOOKSMapping Your Call Flow: FromRing to Resolution30%of employed people in the US worked on an average weekend dayin 2025, against 81% on a weekdayAssistCallInsightsCall Handling Playbooks: Mapping Your Call Flow: From Ring to Resolution30%: of employed people in the US worked on an average weekend day in 2025, against 81% on a weekdayCALL HANDLING PLAYBOOKSMapping Your CallFlow: From Ring toResolution30%of employed people in the US worked onan average weekend day in 2025,against 81% on a weekdayAssistCall
Figure source: U.S. Bureau of Labor Statistics, 2025[1]

Key takeaways

  • Map from real calls: a week of logs shows the call types you actually get, and each one needs a defined outcome.
  • 'Left a voicemail' is not an outcome; a message only counts once it has an owner and a callback time.
  • Draw separate paths for open hours, lunch, after hours and weekends; only 30% of employed people work on an average weekend day[1].
  • Hunt the dead ends: transfers into unchecked voicemail, loops, emergency numbers that ring the office, callbacks with no owner.
  • Test every path with calls from an unknown mobile, and retest after any change to staff, hours or phone settings.

Follow real calls, not the diagram

A call flow drawn on a whiteboard always looks fine. Every arrow lands somewhere and every box has a name in it. The trouble shows up when you follow real calls through it: the transfer that rings out at 12:40 because both people in the box are at lunch, the voicemail box that has been full since August, the after-hours message that tells people to ring the office.

Mapping your call flow means tracing each kind of call from the first ring to a defined end, at each part of the week, and fixing the places where callers get lost. A small office can do it in an afternoon with a week of call logs, a sheet of paper and a phone that isn't saved in anyone's contacts.

The stakes are not abstract. Google's help pages for Local Services Ads say missed calls may count against a provider's responsiveness, one of the factors in how those ads rank[2]. A dead end in your flow is a missed call by another name, and it costs you twice: the caller now, and your visibility later.

Step 1: list every kind of call you get

Start with a week of your phone log, voicemails and call notes, and give each call a type. Example: a small service business might find eight to twelve types; the long tail of oddities can share one box.

  • New customer inquiry: wants a price, a booking or to know whether you do something.
  • Existing customer, routine: a reschedule, a question about a visit, a document request.
  • Urgent: something is broken, leaking or locked, or a deadline is today.
  • Billing and payments: invoices, refunds, disputes.
  • Vendors, partners and other businesses: suppliers, referral partners, other firms.
  • Sales and spam: people selling to you, robocalls and recorded messages.
  • Job applicants and personal calls for staff.
  • Relay calls: callers using 7-1-1 through a communications assistant.

Robocalls get their own type because they distort the count. Do Not Call complaints to the FTC rose in fiscal 2025, though unwanted-call complaints remain well below 2021 levels, and robocalls make up most of them[3]. They need a quick, polite end, not a place in the queue. Relay calls need the opposite: under the ADA, businesses must accept them and staff must treat them like any other call[4], so they follow the same path as everyone else, with a little more patience in the first seconds.

Step 2: give every call type an outcome

A call type without a defined end is where dead ends breed. For each type, write the outcome that closes it, who owns it and how fast it must happen. Five outcomes cover nearly everything: answered on the spot, booked, transferred to someone who actually picked up, message taken with a callback time, or politely ended. BLS describes referring customers to supervisors or more experienced colleagues as a routine part of customer service work[5]; the outcome table is where you write down who that is.

Example outcome table for a small service business; set your own owners and time limits
Call typeOutcome that closes itOwnerExample time limit
New customer inquiryBooked, or a callback at an agreed timeFront deskCallback within one business hour
Existing customer, routineAnswered, rescheduled, or a message to the named personFront deskSame day
UrgentTransferred to the on-call person who answers; otherwise an urgent messageOn-call rotaTransfer tried at once; urgent callback within 15 minutes
BillingMessage to the bookkeeper with the invoice numberBookkeeperNext business day
Vendors and partnersMessage or email to the right personOwner or managerTwo business days
Sales and spamPolitely endedWhoever answersUnder one minute
Relay callsSame outcome as the caller's actual requestWhoever answersSame as that request

Notice what is missing from the outcome column: 'left a voicemail' and 'someone will call you'. Neither closes anything. A message only counts when it has an owner and a time, and the new customer intake questions make sure it carries everything that owner needs. Answers for the 'answered on the spot' outcome come from your caller FAQ list.

Step 3: draw the path for each part of the week

The same call type takes different paths at 10 am on a Tuesday, at 12:30, at 7 pm and on Sunday afternoon. Draw one path per time band: open hours, lunch and other thin moments, after hours, and weekends and holidays.

Employed people in the US who worked on an average day, 2025
Employed people in the US who worked on an average day, 2025Comparison. Average weekday: 81%; Average weekend day: 30%.81%Average weekdayAverage weekday: 81%30%Average weekend dayAverage weekend day: 30%Employed people in the US who worked on an average day, 2025Comparison. Average weekday: 81%; Average weekend day: 30%.81%Average weekdayAverage weekday: 81%30%Average weekend dayAverage weekend day: 30%

Source: U.S. Bureau of Labor Statistics, 2025[1]

Show the data
ItemValue
Average weekday81%
Average weekend day30%

Weekends need the most thought. In the 2025 American Time Use Survey, 81% of employed people worked on an average weekday but only 30% on an average weekend day[1]. That cuts both ways: most of your team is off, and many of your customers are home with time to deal with the dripping tap or the estimate they have been putting off. A weekend path that ends in 'call back Monday' is one of the most common dead ends on a small-business map.

For each band, write where the call physically goes. If you forward your number, note which kind: all day, after hours on a schedule, or overflow when lines are busy or unanswered. The guide to call forwarding codes and gotchas explains each type, and overflow calls covers what happens when every line is busy at once.

Step 4: find the dead ends

Now walk each path and mark anywhere a caller can end up without an outcome. These are the ones that turn up most often:

  • Transfers into nowhere: a desk phone that rings out into a voicemail box nobody checks, or a cell that drops into a personal greeting.
  • Full or unchecked voicemail. If a box is the end of a path, emptying it daily must be somebody's named job.
  • Loops: a menu option that returns to the main menu, or forwarding that sends the call back to the line it came from.
  • Emergency instructions that point back to the office: 'For emergencies, please call our main number.'
  • Callbacks with no owner: 'someone will get back to you', with no name and no time.
  • Silence traps: a system or a person that hangs up after a few quiet seconds, which drops relay calls and callers hunting for an invoice number.

Callbacks deserve a special look because they depend on the caller picking up. Pew found that 67% of adults let unknown numbers ring and then check voicemail, while 14% generally ignore voicemails[6]. A path that ends in a callback therefore needs a voicemail script and a second attempt, or it is a dead end that simply takes longer to reach. The callback script has wording for both.

Example: one call type mapped end to end

Here is a single path drawn the way your map should look: one call type, one time band, every branch ending in an outcome. The business is a fictional heating company with an SI Employee covering its forwarded line after 6 pm.

Example: a no-heat call at 9 pm at a fictional heating company
  • Caller
  • SI Employee
  • System
  • Your team
  1. 01Caller

    Caller reports no heat

    Forwarded after-hours line; the furnace has stopped and the house is getting cold.

  2. 02SI Employee

    Answers and captures

    Approved greeting; name, number, address and the problem, read back.

  3. 03SI Employee

    Checks the urgent rules

    The owner's list says no heat in winter is urgent; routine work would be booked.

  4. 04System

    Transfers to on-call tech

    Plain transfer to the approved on-call number, then the backup.

  5. 05SI Employee

    No answer: caller told

    If nobody picks up, the call comes back and the caller hears what happens next.

  6. 06System

    URGENT email to the team

    Summary, recording and transcript saved; the message is marked urgent.

  7. 07Your team

    Morning review

    The office checks the outcome and closes the loop with the customer.

Example only. The urgent rules, transfer numbers and wording are the owner's; every branch ends in an outcome.

Two details in that path are easy to miss. The call cannot be transferred back to the same line that forwarded it, so the on-call number must be a different phone. And the no-answer branch is designed, not improvised: the caller is told plainly that the technician did not pick up and what happens next, rather than being left on hold. The owner can also listen to a call in progress, whisper guidance the caller does not hear, or take the call over.

Draw every high-value call type this way, starting with new inquiries and urgent calls. For a company with several trades, the home services guide to call routing across trades shows the same idea with one path per trade, and SI Employee vs AI receptionist sets out what changes for the caller on an after-hours path.

Step 5: test the map with real calls

  1. Script one test call per path

    A new inquiry at lunch, an urgent call after hours, a billing question on Saturday, and on through your outcome table.

  2. Call from an unknown mobile

    Use a phone nobody has saved, so you hear exactly what a new customer hears, menus and all.

  3. Time each call

    Note the seconds to answer, any hold, and where the call finally ended.

  4. Mark pass or dead end

    A pass reaches the outcome in your table within its time limit. Anything else is a dead end.

  5. Fix and retest

    Change the route, the greeting or the owner, then make the same call again the next day.

Repeat the test after anything changes: new staff, new hours, a new phone system or carrier, holiday schedules. Phone settings drift quietly, and the first person to find a broken forward is usually a customer. Keep the results alongside your call disposition codes so the outcome labels in your reports match the ones on the map.

Keep the map where people use it

The finished map is one page per time band, pinned where phones are answered and saved wherever the person who changes phone settings will see it. Give it an owner and a review date like any other standard. When the outcome table and your call standard agree, staff stop guessing; call handling best practices covers the standard itself.

The five-truck plumbing company example applies an after-hours map like this one to a weekly on-call rota, and how an AI receptionist works explains what happens inside the answering step when software takes it.

Frequently asked questions

What is the difference between a call flow and a phone tree?

A phone tree is the menu callers hear, such as 'press 1 for service'. A call flow is the whole route a call takes from the first ring to its outcome, menu or not, including transfers, voicemail and callbacks. Plenty of small businesses have a call flow and no phone tree at all.

How many call types should a small business map?

List every type you find in a week of calls, but draw full diagrams only for the ones that bring in money or carry risk, usually new inquiries and urgent calls. The rest fit in the outcome table.

Who should own the call flow?

One person, usually the office manager or owner, who controls the phone settings or knows who does. Changes to forwarding, menus and on-call numbers go through them so the map stays true.

How often should we test the call flow?

After any change to staff, hours, numbers or phone provider, before holidays, and otherwise once a month. A round of eight test calls takes well under an hour.

What should happen when nobody answers a transfer?

The call should come back, the caller should be told plainly what happens next, and a message with an owner and a callback time should be created. A transfer that falls into a voicemail box nobody checks is the most common dead end of all.

References

  1. U.S. Bureau of Labor Statistics (2025). American Time Use Survey: 2025 Results (opens in a new tab) ↑

  2. Google (2026). About ad rankings (Local Services Ads Help) (opens in a new tab) ↑

  3. Federal Trade Commission (2025). FTC Releases Annual Do Not Call Registry Data Book (opens in a new tab) ↑

  4. U.S. Department of Justice, Civil Rights Division (ADA.gov) (2020). ADA Requirements: Effective Communication (opens in a new tab) ↑

  5. U.S. Bureau of Labor Statistics (2025). Customer Service Representatives: Occupational Outlook Handbook (opens in a new tab) ↑

  6. Pew Research Center (2020). Most Americans don't answer cellphone calls from unknown numbers (opens in a new tab) ↑

Book a demo

Meet your SI Employee.

Book a short demo. We walk through calls like yours and show what your SI Employee would answer, book and follow up.

Book a demo