Agree the lead definition with sales
B2B lead generation needs a shared handoff definition for enquiry, suitable lead, opportunity and sale. Not every submitted form represents a qualified opportunity. Sales should state the information needed to accept or reject the work. Marketing capture and the sales team assuming responsibility are separate stages with separate evidence.
Describe acceptance using a limited set of useful fields, such as the service need, business context and an appropriate contact route. If budget or company size is necessary, explain why; every request need not use the same mandatory fields. Missing information, poor fit and suspected spam should not collapse into one indistinguishable rejection category.
Include stage, decision owner, acceptance condition and next task in the handoff worksheet. Do not leave an individual employee’s interpretation as the unstated system definition. Resolve disputed cases using controlled example records. Record the reason for qualified, rejected and information-pending examples, so another team member can reach the same decision using the documented criteria.
Captured enquiry
A request accepted by the backend, which may still await a sales suitability decision.
Sales acceptance
A named owner agrees to work the enquiry under defined conditions.
Opportunity
A separate business stage in the CRM, not an automatic consequence of creating a contact row.
Standardize source and contact fields
Transferring lead sources to sales should distinguish acquisition context, contact information and the stated business need. Use an agreed source dictionary and preserve missing campaign information as missing. Assigning an unknown enquiry to the latest campaign can distort later analysis. A technical source label is different from the problem described by the person.
Store necessary contact information in the CRM with appropriate purpose and access; do not copy it into Analytics. Include checks for email or phone values in form URLs and redirects. Avoid forwarding the complete enquiry message as an anonymous event parameter. For field mappings, document how empty or absent values affect the destination.
Define an incomplete state and follow-up task where required information is missing. Do not invent a value and mark it as verified. Review service type, contact route, source, decision owner and necessary context at handoff. Use controlled fictional records and redact contact values from evidence shared beyond the appropriate operational team.
FROM READING TO A NEXT STEP
Review the gaps in your sales handoff
Bring a redacted field map and controlled handoff scenarios. We can build acceptance evidence for ownership, sales decisions and recovery from partial failures.
Test duplicates and ownership assignment
Lead ownership assignment must distinguish a repeated enquiry from a new request made for another business. The same contact route can appear in different commercial contexts. Define the relationship between person, organization and enquiry. Merging everything can erase history, while treating every submission as a new person can create duplicate work.
Prepare cases for a repeated request, another organization and a changed owner. Describe how existing open work should be updated. Establish the evidence needed to overwrite old information; the latest submitted value is not automatically the most accurate. If an owner cannot be found, the fallback team queue should remain visible and assigned.
Review duplicate decisions without losing source history. A proposed merge is different from a permanent merge; uncertain relationships can remain under review. Acceptance evidence should show that replaying one enquiry creates no second task while a genuinely different business request remains intact. Similar contact details are not a substitute for enquiry identity.
| Controlled case | Decision | Expected evidence |
|---|---|---|
| Same enquiry delivered again | Relate it to the existing request | No second task; history remains available. |
| Another organization represented | Review the business context separately | Contact relationship remains; the request is preserved. |
| No matching owner | Use the agreed team queue | The record and next responsible owner are visible. |
Connect sales acceptance with the next task
A sales-ready lead handoff should continue beyond an owner’s name. Acceptance needs a next task, relevant context and a response target. Rejection needs a reason. When ownership changes, open work should transfer visibly. An unassigned notification or unread message is insufficient evidence that responsibility has been accepted.
Walk through a controlled record as the sales representative would see it. Match the service request to the terms used by sales, and ensure the source summary makes no unsupported promise. Completing an approval field and creating the actual follow-up task are separate checks. Delivery of a notification also does not prove human acceptance.
Set response targets according to team capacity and identify them as internal operating goals, not unverified public service guarantees. Document a fallback for absence or staff changes. The evidence should show decision, task owner and next action together. A notification being created and a person accepting responsibility are separate states; record who took ownership, when they did so and which fallback applies to unclaimed work.
Review the error queue and retries
Reliable lead delivery includes the case where CRM access fails temporarily. If the backend accepted the enquiry, the user-visible state should reflect that real acceptance. Failure to reach the CRM immediately differs from never accepting the request. Define a recovery owner and visibility for pending work rather than silently losing it.
Replay should use the same enquiry identity, with checks for duplicate contacts and tasks. Include partial success: a contact may be created while the task fails. Restarting every step can cause duplication unless completed steps are distinguishable. Do not approve a claim of safe retries before seeing evidence that the intended workflow preserves completed work.
An error queue should not become a widely accessible copy of the complete enquiry. Technical cause, a necessary control label, owner and recovery decision may suffice. Determine retention and access separately. Incomplete requests also need review, completion or reasoned closure states instead of disappearing without a documented decision.
Monitor handoff time and rejection reasons
Lead-process performance review should measure capture-to-assignment and assignment-to-sales-decision separately. A duration is ambiguous without defined start and end states. Do not hide waiting enquiries inside an average of completed cases. Review queue age and unresolved workload independently so the team can distinguish throughput from a growing backlog.
Use a bounded rejection dictionary. Wrong service, missing information and an unreachable contact imply different improvement decisions. Process counts should not contain actual email, phone or free-text messages. The CRM can retain necessary personal information within its appropriate purpose; Analytics can observe anonymous process categories. These storage purposes remain distinct.
Finish with definitions, field mapping, repeat-enquiry evidence, sales decisions, task output and recovery scenarios. Hand over unresolved issues with owners. A large contact count does not establish a strong sales outcome. Handoff acceptance demonstrates information and responsibility quality; commercial qualification still depends on the source decisions.
Review the gaps in your sales handoff
Your email and phone are used for this request. This does not subscribe you to a newsletter.
BEFORE YOU DECIDE
Frequently asked questions
Does a CRM record mean a qualified lead?
No. A CRM record may establish storage, while sales acceptance and opportunity status are separate decisions. Define the acceptance criteria and owner before presenting the record count as the number of qualified leads.
How should repeat enquiries be handled?
First distinguish a replay of the same enquiry from a new commercial request. Preserve the person and organization relationship and update relevant open work. Use a controlled case to verify that redelivery does not create duplicate tasks.
Should an incomplete record be discarded?
Define incomplete, follow-up, review or reasoned-closure states instead of automatically discarding it. Retention and access requirements are separate decisions. Do not guess missing information and store it as a verified fact.
Which fields are needed for sales handoff?
Business context, an appropriate contact route, source, decision owner, acceptance state and next task are a useful starting set. Agree the complete set for your process. Making every field mandatory does not guarantee a usable handoff.
Should lead contact data be sent to Analytics?
Keep contact information out of Analytics. Use bounded anonymous categories for process states and counts. Check URLs and free text for exposure too, and design CRM storage separately with the appropriate access and purpose.
LET’S DEFINE THE SCOPE
Review the gaps in your sales handoff
Bring a redacted field map and controlled handoff scenarios. We can build acceptance evidence for ownership, sales decisions and recovery from partial failures.
Discuss lead handoff