What Happens After the Inquiry? How Leads Get Lost After Contact

An inquiry is a request to start a conversation. It is not automatically a qualified lead, and a qualified lead is not automatically a customer. Treating those stages as one number can make an advertising problem appear where the real gap is after contact.

Map what happens after someone reaches out

Write down the path a real person takes. For a call, where does the published number route? Who answers during business hours? What happens when everyone is busy, after hours, or when the call is forwarded? For a form, where does the submission arrive? Does it create an email, a CRM record, or both? Who is responsible for seeing it? The path ends only when someone has taken ownership and the customer knows what comes next.

Hypothetical example: A roofing company gets a form request on Monday. The form shows “sent,” but the message is placed in an inbox nobody checks. The advertising created an inquiry; the delivery and ownership process lost it. Changing the headline on the ad would not repair that handoff.

Test phone calls beyond the tap

Call the published number from an outside phone, including the number used in an ad if it differs from the website. Check whether a person, answering service, or voicemail identifies the business and gives a usable next step. A working tap-to-call link only proves that the phone can start a call. A missed call may still be returned; an answered call may still fail to become a relevant conversation. Inspect call records, voicemail, and any answering-service handoff before deciding what happened.

Google Ads explicitly distinguishes calls, call conversions, and clicks on a mobile phone number. A click on a number can be tracked without confirming that a conversation occurred; some call conversions depend on a duration threshold chosen in the account. Google Ads: phone call conversion tracking Google Ads: call reporting data The platform metric and the actual customer outcome answer different questions.

Trace form delivery and ownership

Submit a controlled test with permission, then locate it at every step: confirmation screen, notification email, shared inbox, integration, CRM record, and assigned person. A confirmation screen can show that the browser completed a step; it does not prove the right person received the request. Check spam filtering, forwarding rules, integration errors, and duplicate records if the trail stops. For incomplete records, record what is missing before assuming the customer gave bad information. Avoid putting sensitive personal details into a test.

A clear confirmation should say what was received and what the person can reasonably expect next. This is a usability principle, not a promise of a particular response time. GOV.UK Design System: confirmation pages

Decide who acts and what they say

Make one person or role responsible for each incoming channel, with a backup when that person is unavailable. Define how a missed call, voicemail, form, or answering-service message becomes a task someone can see. A useful process records whether the inquiry was received, whether it fits the service and area, who owns the next action, and whether the customer was told what happens next. It can be a simple shared log; no particular CRM is required.

Confirmation messages should match the real process. “We received your request and will contact you during business hours” is more useful than an unsupported promise of an immediate call. If a request needs more details before an estimate, say so. A response process should also avoid sending the same person conflicting replies from multiple inboxes or duplicated CRM entries.

Review several real inquiries carefully

Choose a small set of recent, traceable inquiries across the relevant channels and follow each from the first contact record to its current status. For each, ask: Was the contact received? Was it a genuine service request? Was it in the area you serve? Was a response attempted? What did the customer hear or see? Where does the evidence stop? Note whether attribution to a campaign is direct, inferred, or unknown.

One unanswered call is worth fixing for that caller, but it does not by itself establish a recurring failure rate. Repeated missed calls in the same period or repeated form requests that never reach an owner justify a broader process check. If only a few inquiries exist, describe the cases and keep the uncertainty visible; do not turn them into a precise benchmark.

Hypothetical example: Three recent calls from one campaign all reached a full voicemail box. That is a repeated observable path failure worth testing and repairing. One short call that ended before anyone spoke is less informative on its own; review the call path and a wider set before blaming either the ad or the team.

Inspect the right evidence before changing the ad

Compare campaign and website contact counts with phone, inbox, and CRM records, knowing that those systems may count different events. Google notes that reporting scope can differ by level: manually dialed calls can be counted for campaigns and ad groups while being absent from keyword- and ad-level call totals. Call conversions can also differ from the number of calls. Google Ads: call reporting data A lead may also contact you later or through another channel. Attribution can therefore be incomplete even when the inquiry itself is real.

If relevant inquiries arrive but are lost in routing or follow-up, repair that path before rewriting the ad or rebuilding the page. If the inquiries are repeatedly for the wrong service or outside your area, examine traffic relevance and the ad promise. If the contact action itself is hard to use, revisit the click-to-inquiry diagnosis and test the Click-to-Inquiry Audit. These are different problems with different evidence.