Separate receipt, qualification and outcome
A lead system should answer three questions: did the business receive the request, who is responsible for it, and what happened next? These are different events and deserve explicit records.
Start with a small state model such as new, reviewing, qualified, proposal, won, declined and spam. Adapt the states to the business rather than treating this example as a mandatory pipeline. Define which transitions require a reason or follow-up action.
Define one authoritative lead record
The record should preserve the original message, contact channel, service interest, source page and submission time. Subsequent corrections should not erase what the visitor sent. Link messages and briefs to the lead instead of copying their contents into unrelated notes.
| Event | Required behaviour |
|---|---|
| Repeated submission after a timeout | Return the existing receipt when the idempotency key matches |
| Owner changes | Record who reassigned the lead and when |
| Lead is declined | Keep a reason and history under the retention policy |
| Notification fails | Keep the saved lead and surface the delivery failure |
| User loses access | Enforce the permission change on future reads and writes |
Prefer actionable queues over vanity counts
Useful operational views include unassigned requests, requests awaiting a response and follow-ups due under an agreed policy. The number of leads alone says little about whether the team can respond.
Choose timestamps carefully. “First human response” should not mean an automatic acknowledgement. If reporting uses these labels, document the actual event being counted.
Verify the whole path
Send a labelled test enquiry using synthetic details. Find it in the CRM, assign an owner, add a response and inspect the history. Test another role’s access. Mark the test clearly so it does not contaminate operational reporting.
Connect website forms to business systems around durable receipt and clear ownership.
A practical question
Is an automatic acknowledgement the first human response?
No. Record those events separately. An acknowledgement proves receipt; a human response shows that a responsible person has engaged with the request.