A lead arrives by email, the salesperson sees it forty minutes later, calls back, and the customer has already booked someone else. A week on, the owner asks where customers actually come from and hears "advertising, probably". Both problems are the same problem: there is no system between the form on the website and the person who sells. Below is how to connect every lead source to a CRM, which fields must travel with each lead, how to set up stages and reminders, and where to start if you have no CRM at all.

Five places where leads disappear

Before choosing a system, look honestly at where the losses happen. In most small companies they are spread fairly evenly across these five points, and not one of them is fixed by hiring another salesperson.

1. 1Email. The form notification lands in a shared inbox next to spam and invoices. If that person is on holiday, the lead surfaces a week later.
2. 2Personal messengers. The customer messaged the owner directly, who forwarded it to sales as a voice note. Two days later nobody remembers whether anyone called back.
3. 3Untracked calls. A missed call at 18:10 exists nowhere. Without telephony wired into the CRM you do not even know how many there were.
4. 4Bot and chat conversations. The thread stayed in the app and never became a record. This is the most common oversight after launching a Telegram bot.
5. 5Long deals with no reminders. The customer asked to be called back in a month. That reminder lives in someone’s memory, which means it lives nowhere.

What to connect, and how

The goal is blunt: no enquiry should exist outside the system. Every channel is connected separately, and each has its own price and its own traps.

One specific warning about forms: email forwarding is not an integration. A message is easy to lose in a spam filter, carries no status, and cannot trigger a task automatically. A webhook from your backend takes a few hours to build and then works for a decade.

Attribution: what to send along with the lead

The question "where did this customer come from" is not answered by asking the salesperson. It is answered by three fields that travel with the lead from first visit to payment. Technically it is simple: store the tags in a cookie on the first visit and add them to the payload when the form is submitted.

{
  "name": "Elena",
  "phone": "+441234567890",
  "message": "Looking for a store with about 200 products",
  "page": "/services/web-development",
  "utm_source": "google",
  "utm_medium": "cpc",
  "utm_campaign": "web-dev-emea",
  "first_touch": "2026-02-03T11:04:22Z",
  "client_id": "GA1.2.1837462.1738574662",
  "form_id": "services-inline"
}

• First touch, not last. Keep the first-visit tags in a separate 90-day cookie, otherwise organic and paid traffic both get credited to direct visits.
• The analytics identifier. A single client_id field lets you later join the deal to on-site behaviour. Setting that up properly is covered in our analytics setup walkthrough.
• Page and form. Knowing that leads come from the inline block halfway down a service page rather than the contact page is a direct input into conversion work.
• Time of enquiry. Shows how much arrives outside working hours. This is frequently where a bot covering nights turns out to pay for itself in a month.

Stages and automations that actually get used

The classic launch mistake is a fourteen-stage pipeline that the sales team quietly abandons in week two. A working pipeline fits into five to seven steps, and every step has an explicit condition for moving on rather than depending on how a salesperson feels.

1. 1

   New lead

   Created automatically the moment the form is submitted, with an owner assigned by rota and a "call" task due in 15 minutes. The notification is mirrored into the team chat.

2. 2

   In progress

   The condition for this stage is that contact happened, not that somebody looked at it. If the status has not moved in two hours, the system escalates to a manager. Of every automation on this list, this one moves revenue the most.

3. 3

   Qualified

   Budget, timeline and task are clear. This is where you fill the fields your reports will later be built from: project type, approximate value, source. Unqualified leads get closed with a reason rather than quietly vanishing.

4. 4

   Proposal sent

   Automatic follow-up tasks on day three and day seven. Two thirds of lost small-business deals die right here — not from a refusal, but from silence on both sides.

5. 5

   Decision

   The deal closes as won or lost, and lost always carries a reason from a fixed list: price, timeline, chose a competitor, went quiet. Within a quarter that list becomes the most useful document in the company.

If you have no CRM yet: the order of work

Do not start by choosing a system — that is the least important decision at this stage. Start by describing what you want to see in a report three months from now, then work backwards to the fields and stages that produce it. In practice two weeks is enough for a first version.

From there the system grows naturally: inventory connections, automatic documents, segmented campaigns to your own opt-in list. That is the next level though, and it is worth building only once the basic stages get filled in without anyone nagging. Our general approach to projects like this is set out in the guide to business process automation.

Frequently asked questions about CRM integration

In short

• Leads leak in five places: email, personal messengers, calls, bots, and long deals with no reminders.
• Email forwarding is not an integration. A backend webhook into the CRM is the baseline.
• Pass first-touch tags, the source page and the analytics identifier, or no channel report is possible.
• A 5–7 stage pipeline with a mandatory loss reason works; a fourteen-stage one does not.
• Write down how leads should be handled first, and only then pick the software.