How to Audit Your Service Business Follow-Up Process in 30 Minutes
A time-boxed way to map your lead follow-up process: seven lead sources, five questions each, and one fix to test for a week.
What this audit checks
Our lead response time post covers speed to lead: how fast you reply. This audit asks an earlier question: does a follow-up happen at all, and whose job is it?
A lead nobody owns sits in a log until the customer books with someone else. You need no new software to find those leads. A sheet of paper with five columns works.
Minutes 0 to 5: open every place a lead lands
Pull these up before you start the clock:
- The call log from your phone system or carrier app.
- Voicemail, including any personal cell that takes business calls.
- Website form notifications and the inbox they go to.
- Your business texting inbox.
- The estimate tool or folder of sent quotes.
- The calendar where appointments live.
- Your CRM, spreadsheet or lead list, if you have one.
If a source lives on someone's personal phone, write that down now. You will need it in minute 20.
Minutes 5 to 20: map the follow-up for each lead source
Give each lead source one row and five columns.
| Column | The question | A weak answer sounds like |
|---|---|---|
| Owner | Which named person is responsible? | "Whoever sees it" |
| Trigger | What tells them to act? | "They just know" |
| Message | What do they send or say? | "Depends on the day" |
| Next step | What should the customer do next? | "We wait to hear back" |
| Tracked in | Where is the follow-up recorded? | "My head" or "my texts" |
Spend about two minutes per source.
Calls answered live
Who picks up when the owner is under a house? After the call, does the lead go into a list or CRM, or onto a notepad by the phone?
Missed calls
Check the first few minutes after a call rings out. Does a text go back, does someone get a task, or does the call wait until somebody scrolls the log?
Hold queues belong in this row too. CallRail, a call-tracking company, surveyed 1,000 US consumers in September 2025, and 41% said they hang up after 1 to 2 minutes on hold. Check whether your phone system logs those hang-ups at all.
Voicemails
In the same CallRail survey, 42% of consumers said they leave a voicemail. That makes voicemail a follow-up trigger, and a trigger needs an owner. Write down who checks it, how often, and whether the callback gets logged.
Web forms
Find the inbox where form notifications land, and note it if nobody watches it on weekends. Then check whether the person who submitted gets a reply that says what happens next. Our form-first lead capture post covers the form itself.
Texts
Inbound texts often land on one person's phone. When that person is off, who sees them?
Estimates sent
A sent estimate is a warm lead that has gone quiet. Who follows up, on what day, and with what message? If the answer is "when I get around to it," mark the row.
No-shows
When a customer misses an appointment, does anyone try to rebook them, or does the slot close out as a loss?
Minutes 20 to 25: flag every handoff that runs on memory
A memory handoff is any step in your lead follow-up system that happens only if one specific person remembers to do it. Go back through your map and put a mark next to each one. Read the answers out loud and listen for "I usually," "whoever's around" and "I'll see it." Sticky notes, personal cell phones and leads tracked only in someone's text thread count too. Each mark is a spot where a sick day or a packed schedule can drop a customer without anyone noticing. A handoff that does not depend on memory has three parts: a trigger the system creates on its own, a named owner with a backup, and a record showing the follow-up happened. Count the marks in each row. The row with the most marks is the first place to look, because nothing alerts anyone when it fails.
Minutes 25 to 30: pick one fix
Choose one row to fix this week and leave the rest on the list. To choose, do the math with your own numbers: leads through that source in a normal week, times your average job value. The row with the most marks and the most money behind it goes first.
Write the fix as one sentence with an owner and a start date. Fixes at this size look like:
- Missed calls get a text back within a set number of minutes, and the office gets a task to call.
- A named person checks voicemail at fixed times each day, with a named backup.
- Every sent estimate gets a follow-up on a set day after it goes out.
Let the repeatable step run on its own. Keep pricing, judgment calls and difficult customers with a person.
Run a 7-day follow-up test
A 7-day test tells you whether the fix holds before you build anything bigger. On day one, put the fix in place and tell the owner and the backup what changed. For the next seven days, log every lead that comes through that one source: the time it arrived, the time of the first response, who responded, and what happened next. A CRM follow-up field, a shared spreadsheet or a paper log by the phone all work. On day seven, read the log and answer three questions. Did every lead from that source get a response? Does any step still depend on someone remembering? Did a lead show up somewhere you never mapped? If the answers are yes, no and no, move to the next row on your list. If not, adjust the fix and run another week.
The bottom line
Your lead follow-up process is only as dependable as its weakest handoff. Thirty minutes of mapping shows you where follow-up depends on memory, and seven days of logging shows you whether your fix holds. For the deeper version, our free Follow-Up Audit Guide walks through the five follow-up moments where booked jobs get lost and helps you pick which leak to fix first.
Common questions
How long does a follow-up audit take? The mapping takes about 30 minutes if your call log, texts, form inbox, estimates and calendar are open before you start. The 7-day test after it takes a few minutes a day.
What is a memory handoff? It is a follow-up step that happens only if one person remembers to do it. Checking voicemail "when I can," chasing estimates from memory, and answering texts that go to one employee's personal phone are all memory handoffs.
Do I need a CRM to run this audit? No. Paper or a spreadsheet works for the map and the 7-day test. A CRM helps later because it can create follow-up tasks and record them, but the audit shows you what to set up first.
How is this different from the Follow-Up Audit Guide? This post maps who owns each lead source and where handoffs depend on memory. The free Follow-Up Audit Guide goes deeper on the five follow-up moments where booked jobs get lost and helps you decide which leak to fix first.