Use when the profile shows plenty of calls and clicks but the enquiry log does not match the volume.
missed-call-enquiry-audit.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.
استبدل كل فراغ بتفصيلة من عندك. كلما كنت أدقّ، قلّ ما يخترعه النموذج.