Business guide
From website enquiry to won job: a practical lead-tracking workflow
Connect a delivered website enquiry to follow-up, quotes and accepted jobs using clear statuses and a reliable business record.
Give each business milestone a clear meaning
A website can record a visit, a phone-button click or a form submission. None of those events proves a job was won. To understand the result, connect the contact to the way the business handles enquiries: someone responds, checks the scope, prepares a quote and records whether the customer accepts. This is an operational workflow as well as a measurement question.
Agree a small set of statuses that staff can apply consistently. New, contacted, qualified, quoted, won and lost may be enough, with an open or waiting state where useful. Define “won” for your business: an accepted quote, a paid deposit and a completed job are different milestones. Keep the definition visible rather than allowing each person to interpret it differently.
Create a durable record when a genuine enquiry arrives
A delivered form can create a lead record with a unique internal reference. Phone and email enquiries need a route into the same process if they are to appear in the operational report. A spam submission or a deliberate honeypot response should not become a genuine lead. Keep delivery, acceptance and qualification distinct so the system reports what it knows.
Store a limited amount of useful context: requested service, broad location, contact preference, who is responsible and when a response is due. Keep customer details in the business’s authorised system. Do not place names, emails, personal telephone numbers or private messages in analytics event parameters just to make a dashboard easier to read.
- Received
Create the record after the enquiry is genuinely accepted.
- Assigned
Give a staff member responsibility and a next action.
- Quoted
Associate the quote and its status with the same enquiry.
- Won or lost
Apply the agreed outcome definition and keep the reason where useful.
Record source evidence without pretending it is perfect
Where available and appropriate, preserve the landing page, campaign information and measured source alongside the enquiry. An organic visit, paid click, referral and direct visit should not all become “Google” simply because a customer has used Google before. Keep a customer-reported answer separately from technical attribution because each can describe a different part of the journey.
Some enquiries will have an unknown source. Consent choices, browsers, repeat visits and different devices can limit what is observed. Preserve uncertainty rather than filling gaps with a guess. Aggregate Search Console query data is useful for understanding website visibility, but it does not identify which exact search query belongs to an individual customer who later called.
Make the next action easier to see than another dashboard
A lead list should answer who is responding, what happens next and which enquiries are overdue. A quote-follow-up reminder can be useful when staff agree the interval and circumstances. Avoid automatically chasing customers after they have declined or opted out. The person handling the enquiry needs a simple way to update its status and stop unnecessary reminders.
Link new contact attempts to the existing lead where the match is reliable. A customer who calls after submitting a form should not automatically count as another new opportunity. At the same time, a repeat customer requesting a separate job may need a new opportunity associated with the same customer. Separate the person from the individual piece of work.
- Agree what new, qualified, quoted, won and lost mean.
- Create a stable enquiry reference and assign responsibility.
- Keep source evidence and customer-reported source separate.
- Record next actions and distinguish duplicate contacts from new jobs.
Use outcomes to choose the next improvement
Review suitable enquiries, quotes, acceptance and the time spent waiting at each stage. If plenty of relevant enquiries arrive but quotes are delayed, more traffic may not be the immediate priority. If a service page brings the wrong requests, clearer scope may help. A meaningful report connects marketing activity with the part of the business that can act on it.
My custom business systems work can scope this process around your team rather than require a large system on day one. A shared, well-maintained record can establish the workflow before more automation is added. Feeding eligible outcomes back to advertising platforms is a separate integration, with its own matching, permission and testing requirements. Start with an outcome record the business trusts.