How to find lost leads between your website, messaging and CRM

1. List every place a customer can contact you

Website forms, calls, WhatsApp, other messaging apps, social media and personal staff contacts may operate in separate systems. For each source, identify where the enquiry is stored and who should receive it.

Before buying another CRM, establish which enquiries the current process tracks and which fall outside it.

2. Check receipt, not just submission

For a test enquiry, compare the website confirmation, receipt in the destination channel and the CRM record. Check whether the contact details, message and source survived. For calls, check routing and what happens after a missed call.

Tell the team about the check and mark test enquiries. Keep them out of reporting on real leads.

• Submitted but not received: check delivery and integration.
• Received but absent from CRM: check registration rules.
• Recorded twice: check duplicates and contact-merging rules.

3. Identify who owns the first action

A shared queue without an owner creates ambiguity: everyone can assume a colleague picked it up. Check assignment rules, working hours and cover for absent employees.

The HANSA case includes lead-routing widgets and shared processes in Bitrix24. The principle extends beyond one platform: an enquiry needs a clear route and owner. The public case does not quantify response-time improvements, so it cannot supply a numerical benchmark.

4. Look beyond the first reply

An enquiry can be lost after a proposal, a request to call back or a handover to another department. Reconstruct several unfinished conversations: who promised what, when they should return and what is needed from the customer.

An “in progress” record without a next action provides little management value. Required fields should still reflect what employees and leaders actually need.

5. Keep a short checking log

Start with a small sample across channels to identify types of failure. Such a sample can reveal a problem, but cannot establish the overall share of lost leads. A quantitative conclusion requires complete records for a defined period.

• Enquiry source and time.
• Where and when it was received.
• Assigned owner and time of first reply.
• Current stage, next action and reason for stopping.
• Confirmed technical error or process gap.

Match the fix to the finding

A failed transfer calls for an integration check. An unassigned enquiry calls for routing rules. A forgotten conversation needs a task and a clear working process. Missing sources call for better tracking to assess acquisition outcomes.

At Treejar, advertising, WhatsApp, calls and forms were connected with CRM and analytics, while routing and data transfers were automated. This illustrates several parts of the process working together. The necessary scope in your business depends on the losses found.

After the fix, repeat the test journey, including exceptions. Then observe real enquiries: successful technical delivery should be followed by action from the team.

Project experience

Each case identifies the task, work delivered, my role and the context behind the outcome.