What is lead tracking? From the first enquiry to a real outcome

An enquiry comes from a person: someone who filled in a form, sent an email or left a message because they want work done. Lead tracking follows that person's enquiry as one record with a history, from the moment it lands to the moment it is resolved. The record is the unit. A count is not.

That distinction matters because counting can be mistaken for tracking. Website sessions, clicks on an ad, and the number of form submissions this week are all useful figures, and none of them tells you what happened to the plumber's enquiry from Tuesday afternoon. Analytics can tell you a form was submitted. Lead tracking tells you whether anyone opened it, what was done about it and when, whether a quote went out, and whether the job was won. It answers a different question: not "how many?", but "and then what?"

Three things it is not

• It is not a traffic count. Visits and sessions describe people who looked. A lead is a person who asked. Tracking starts when the asking happens.
• It is not a submissions total. Knowing that twelve forms came in says nothing about the eleven that still need a reply.
• It is not the reply itself. Tracking records what was done and when. The calling, quoting and turning up are still yours to do.

A useful lead record is small. It holds the handful of facts that let someone who was not there work out what to do next, and later work out what happened. Not every enquiry needs every field, and a record with three honest entries beats one with twelve blanks.

• Who enquired and how to reach them. A name and at least one way to make contact: a phone number, an email address, or both.
• What they asked about. The job, the address if it matters, and anything they wrote in the form. This is what makes the follow-up call specific.
• When it arrived. The timestamp of the enquiry landing, not of someone noticing it. How long the enquiry has been waiting is counted from here.
• Where it came from, when that was captured. The source and context recorded at the moment the lead was created, such as an ad, a search, a referral or a direct visit. When nothing reliable was captured, the record should say so rather than guess.
• Whether anyone has seen it. When a person first opened the record.
• Whether anyone has acted on it. When the first action was taken, and what it was.
• Its current stage. New, contacted, quoted, and then won or lost. One stage per lead, so the list can be read at a glance.
• Its value, when it was won. What the work was worth, entered by the person who knows.

The pattern in that list is how much of it is timestamps and stages rather than prose. A timestamp written by the system at the moment something happened is evidence. A note typed in on Friday about what happened on Tuesday is a memory.

Tools name the stages differently and some collapse two into one, so treat the list below as the shape of the thing, not a standard.

1. An enquiry arrives. A website form is submitted, an email lands, a message comes in.
2. A record is created, with the contact details and the message.
3. Source and context are attached when they were captured with the enquiry: where the person came from, if that is known.
4. Received is stamped: the moment the enquiry landed.
5. First Seen is stamped when a person first opens the record.
6. First Action is stamped when a person first does something about it from the record: tapping its call, text or email link, or moving the lead out of the new stage.
7. Contacted is a stage the person sets once they judge the customer has been reached.
8. Quoted when a price has gone out.
9. Won or lost, and on won work, the value when there is one to record.

Read in order, those steps separate three things that get mixed up in an inbox: what arrived, what someone did about it, and what it turned into. The timestamps in the middle are difficult to reconstruct reliably afterwards, which is why a system should record them when they happen. The stages at the end are judgements, which is why a person should set them.

Lead generation is everything that creates or attracts enquiries: ads, search rankings, directory listings, referrals, the sign on the van. Lead tracking begins where generation ends, at the point where an identifiable person has asked for something, and records what happens after that.

Some products sell the two together, and the boundary is drawn differently by different products, which is fine. The useful test is the question each one answers. Generation answers "how do we get more enquiries?" Tracking answers "what happened to the ones we got?" A business can be good at one and blind to the other, and one version of that is more enquiries arriving than anyone is keeping track of.

Four neighbouring terms overlap with lead tracking, and each is broader or narrower in a specific way. None of them is wrong to use; they just answer different questions, and it helps to know which one you are asking.

CRM

A CRM (customer relationship management system) is the wider record of a customer over time, built to hold contacts, notes, tasks, deals, emails and marketing. Lead tracking is a narrower slice, focused on the enquiry from arrival to outcome. A CRM may include some form of it, and a business that already runs one may be doing lead tracking inside it. Whether that is lead tracking as this guide uses the term does not depend on the label on the box. It depends on whether the CRM keeps the per-enquiry moments described above: arrival, first seen, first action and stage.

Lead management

Lead management is the broader operational process: who receives enquiries, how they are assigned, how they are qualified, who follows up, how reminders work, and what gets escalated. Tracking is the record inside that process. You can track leads without a formal management process, and a process without a record is the one where, afterwards, what happened is a matter of memory.

Web analytics

Web analytics measures visits, pages, events and behaviour on a site. It can count form submissions and tell you which pages people came through, and it is the right tool for those questions. What it does not do on its own is keep an operational record of one person's enquiry, with a name, a phone number, a first-seen time and a stage. The two sit side by side: analytics for the site, lead tracking for the people who asked.

Lead attribution

Attribution, as a discipline, is about where a lead came from and how credit for the enquiry is read across the sources that led up to it. In a lead record, the evidence it works from is one field group, the "where from" part, and attribution is only as good as what was captured at the moment of the enquiry. LC Flow records that context as separate fields rather than sharing credit between them; the companion guide to lead attribution takes that layer on its own. A recorded source without lead tracking stops at the enquiry: a label sitting on a form fill. A recorded source attached to a tracked record lets you see which recorded sources appear on leads that later became work, because the source stays with the lead through to its outcome. That is an association you can read, not proof that the source caused the job.

For an owner or a small crew, good lead tracking is not a dashboard. It is being able to answer a short list of questions on any given day without opening three inboxes and a call log:

• Which enquiries are still new, and how long have they been waiting?
• Which have been opened but not yet acted on?
• Which have actually been actioned, and by what: a call, a text, an email?
• Which have been quoted?
• Which became work, and what was it worth?
• What source or context was recorded for each, and for which ones nothing was?
• Which enquiries still need someone's attention today?

If the record can answer those, it is doing its job. If it can only answer the last two from memory, it is an inbox. Those questions hold whatever you use. This is how LC Flow's website lead tracking for small service businesses approaches it: enquiries from your website forms land in one workspace once your site is connected and your domain is verified, each one stamped Received on arrival, First Seen when you open it, and First Action when the first tracked action is taken. An email alert goes out when a lead arrives, with up to five reminders while it sits unactioned, and the reminders stop as soon as someone acts. Call, SMS, WhatsApp and Email links on the lead open your own phone and apps; nothing is sent to the customer from inside LC Flow. Each lead then moves through contacted, quoted and won or lost, with the value of won work recorded by you, and carries whatever source context was captured when it was created.

If you would rather see the record than read about it, you can start a 14-day free trial, no credit card required.

Lead response time is one measurement inside the record: the gap between an enquiry arriving and someone first acting on it. It is worth its own attention, because it is where enquiries can go cold, and it is hard to measure reliably unless the arrival and the first action were both timestamped when they happened. That is the point of tracking them. How to measure it, what the research behind the usual advice actually says, and why the delay happens in a service business are covered in the companion piece on lead response time. This article stays on the wider record that makes that measurement possible.

A record is only as honest as the events behind it, and a good one is clear about its limits. These are the ones worth knowing before you trust any lead report, including ours.

• A first action is not a successful contact. A First Action timestamp says someone acted: they tapped to call, opened a text or an email to the customer, or moved the lead on. It does not say the call connected, the message was sent, the customer replied, or a conversation happened. Whether the customer was actually reached is a judgement a person records as the contacted stage.
• Source data is only as good as what was captured. If nothing reliable arrived with the enquiry, the honest record says "not captured" and leaves it there. A source reconstructed afterwards from a hunch is a guess with a label on it.
• Won, and the value of won, are entries, not observations. A won stage and a job value mean what a person recorded. The record described here does not see your invoices or your bank account; it holds what you told it, so the outcome is only as real as the entry.
• Tracking a lead does not generate the lead. The record starts when an enquiry exists. It does not bring the next one in.
• Tracking does not reply for you. A record of an enquiry, an alert that it arrived, and a reminder that it is still waiting are all prompts to a person. None of them answers the customer. The reply is still yours to make; the record shows whether anyone acted on the enquiry, and when, and what you recorded about the outcome.

None of that is a weakness of tracking. It is what makes a tracked record worth reading: the timestamps in it are moments the system saw, the stages are judgements a person made, and you can tell which is which.