How to audit a lead-handling process

Sample real journeys

Pick recent enquiries across channels: web form, phone, email, chat, and referral where applicable. Trace each from first touch until closed, lost, or stalled.

Document timestamps, owners, messages sent, customer-record updates, and gaps. Spreadsheets beat memory. Ten journeys often reveal patterns that anecdotes hide.

Include at least one enquiry that converted and one that did not. Success paths show what should happen; failures show where the system breaks.

Checklist areas to cover

Review sources and capture, speed to first meaningful contact, ownership and routing, qualification logic, customer-records completeness, quote and appointment flows, follow-up sequences, and reporting.

Note where automation should run but does not, and where it runs incorrectly. Broken workflows sometimes hurt more than no automation.

Consent and communication preferences belong in the audit too. Outreach that ignores opt-outs is both a compliance risk and a trust problem.

• Source capture and field mapping
• Response time by channel and hour
• Handoffs between marketing, ops, and sales
• Quote and appointment follow-through
• Reporting visibility at each stage

Journey worksheet (copy this)

For each sampled enquiry, fill one row. Incomplete cells are findings: missing timestamps usually mean the process was never designed, not that the data was lost by accident.

Compare the worksheet against what the team says happens. Gaps between stated process and recorded reality are the highest-value audit results.

• Enquiry ID or anonymised name, channel, and source
• Created at / first acknowledgement / first meaningful contact
• Named owner at each stage (or blank if nobody owned it)
• Qualification answers captured (or blank)
• Next step promised vs next step actually done
• Final status and reason if lost or stalled

Interview stakeholders

Sales, marketing, operations, and customer service often describe different realities. Compare their accounts against journey evidence.

Ask where they work around the system. Workarounds reveal design flaws: duplicate spreadsheets, personal inboxes, or manual texts mean the official process failed.

Management views on priorities may differ from front-line experience. Align on facts from sampled journeys before debating solutions.

Prioritise fixes by impact

Rank leakage points by volume and commercial value. Slow first response on your highest-volume channel usually beats polishing a low-traffic edge case.

Separate quick wins from structural projects. An acknowledgement email can deploy in days. Customer-records redesign takes longer but may unlock reporting.

Each fix should connect to a metric you can review in four weeks. Audits that end in slide decks without ownership change nothing.

• Quick win: acknowledgement, routing alert, or missed-call callback queue
• Medium: qualification questions, status definitions, handoff brief
• Structural: CRM fields, reporting, coverage outside business hours

Document and revisit

Produce a short findings summary: current state, top three leaks, recommended sequence, and named owners. Long reports rarely get read.

Re-audit after major changes or quarterly in high-growth businesses. Process drifts as teams, tools, and volume change.

A lead-handling audit is operational, not a marketing critique. It asks whether enquiries you already pay for become conversations and revenue.