LOCAL

Missed call and enquiry leak audit

Use when the profile shows plenty of calls and clicks but the enquiry log does not match the volume.

missed-call-enquiry-audit.md

Download .md

You are finding where local enquiries are lost between a profile action and a booked job. You work only from the numbers supplied.

Profile activity for the period, with calls, direction requests and website clicks: {{PROFILE_ACTIVITY}}
Enquiries we actually recorded, by source: {{ENQUIRY_LOG}}
Who answers the phone, when, and what happens when they cannot: {{ANSWERING_SETUP}}
Quotes sent and jobs booked in the same period: {{CONVERSION_OUTCOMES}}

Produce:

1. A funnel table: Stage, Count, Drop from the stage above, Which input the number came from. Use these stages: profile action, call connected, call answered, enquiry recorded, quote sent, job booked, drawing on {{PROFILE_ACTIVITY}}, {{ENQUIRY_LOG}} and {{CONVERSION_OUTCOMES}}.

2. The three largest drops. For each, the most likely explanation that {{ANSWERING_SETUP}} actually supports, plus one alternative explanation worth ruling out.

3. A fix table: Fix, What it costs, Who does it, Which number should move, When to check.

4. What to start recording, covering every stage where you had to write not measured.

Rules:
- Where a stage has no number, write not measured and carry it into section 4. Never estimate a missing count or interpolate one.
- Do not attribute a drop to anything {{ANSWERING_SETUP}} does not describe.
- If call tracking numbers come up, say what has to happen to keep the published number consistent everywhere it appears.
- No em dashes.

Fill in before running

Replace each placeholder with your own detail. The more specific you are, the less the model invents.

{{PROFILE_ACTIVITY}}
{{ENQUIRY_LOG}}
{{ANSWERING_SETUP}}
{{CONVERSION_OUTCOMES}}

Getting a better result

Pull the profile activity and the enquiry log for exactly the same dates, or every drop in the table is fiction.
The gap between calls connected and calls answered is usually the largest leak and the cheapest to close.
Start recording the missing stages now, so the next run of this has numbers rather than blanks.

Questions about this prompt

When should I audit the funnel rather than buy more visibility?

When profile activity looks healthy and the enquiry log does not match it. The leak is usually between a call being placed and someone recording it, and pushing more calls into the same funnel widens the gap rather than closing it. Fix the leak first, then spend on visibility.

What numbers do I need?

Profile activity and the enquiry log pulled for exactly the same dates, quotes sent and jobs booked for that period, and an honest description of who answers the phone and what happens when they cannot. Mismatched date ranges make every drop in the table fiction. Find the quotes sent figure before you start.

What comes back?

A funnel table from profile action to booked job with the source of each number, the three largest drops with a supported explanation and one alternative to rule out, a fix table, and a list of what you are not measuring. Stages with no number come back as not measured, never estimated.

What is the mistake?

Explaining a drop with something your answering setup does not actually describe. The prompt will not do it and neither should you in the meeting afterwards. Start recording the not measured stages now, and if call tracking numbers come up, keep the published number consistent everywhere a customer might see it.