Marketing-to-Sales Lead Handoff: Fields, Owner and Feedback Loop

A lead can reach sales without enough information to act. It may have a campaign source but no explanation of the prospect’s request, or be assigned to someone who is away. A useful handoff checklist specifies what makes a lead ready, who takes responsibility and how both teams learn from the outcome.

Record those decisions in a one-page contract agreed by marketing and sales. Include minimum context, routing, response states and reasons a lead can be returned.

Agree on qualification before routing

Define when sales should contact a lead. A marketing-qualified lead should meet stated criteria, rather than receive that label solely for reaching a score or completing a form. Salesforce’s guide to sales and marketing alignment calls for common stage definitions and context about why a prospect is ready for a conversation. Make the criteria checkable against an individual record.

Separate fit from intent. Fit asks whether the person or organisation matches the audience sales serves. Intent asks what the person has done or requested that justifies contact now. A request to discuss a specific need warrants different handling from a content download; a campaign name alone does not explain either signal.

Specify the minimum handoff fields:

• Identity and contact route: the prospect or account, a usable contact method, and any stated preference about how to respond.
• Source and trigger: where the lead came from, what action prompted the handoff, and when it happened.
• Qualification reason: the fit and intent criteria met, with a short explanation when a judgment call was required.
• Conversation context: the question, product interest or problem the prospect described, using their own words where available.
• Next action: what sales is expected to do first and any relevant prior interaction.

Distinguish required fields from useful extras. A source field does not explain why someone wants to speak, while a clear request may be actionable without optional company details. Salesforce’s lead implementation planning guidance asks teams to decide what information belongs on leads and how incoming leads should be routed. It identifies Lead Source and Lead Status as fields teams can adapt to their process.

For each required field, name its source and who corrects it when missing. Hold a record with missing context for correction rather than marking it sales-ready. Leave fields optional if they do not help qualification, routing or the first conversation.

Write down what happens when fields conflict. A form answer may describe a new request while an older CRM note describes an earlier one. Keep both with their dates, and identify which value the first sales message should use. If the same person submits twice, link the newer action to the existing record where appropriate so the assignee sees the most recent request without losing the earlier conversation. A handoff should show the evidence for its qualification decision, not only the final label.

Define the owner, queue and response state

Routing says where a record goes; ownership says who takes the next action. A named assignee may suit an account already in conversation, while a staffed queue may suit new enquiries. Name who watches records that have arrived but have not been accepted.

Salesforce documents assignment rules that assign leads to a user or queue. Rule entries are evaluated in order; when none matches, the record can take a different ownership path. Test that path explicitly.

Give routed leads a few response states with plain meanings: queued awaits an owner; accepted has an owner; working means follow-up is under way; and returned has a reason marketing can act on. A closed record should retain its outcome. Document when each state changes.

Agree on a response window for each type of enquiry. Record when it starts, which hours count and who monitors overdue leads. Assignment alone does not show that anyone read a record; check that an owner accepted it and took the agreed first action.

Plan for an unavailable assignee. Define how absence is detected, when the lead moves to a monitored queue or backup, and who resolves exceptions. Keep the routing and reassignment history visible. If no rule matches, verify that someone monitors the resulting owner or queue.

Make routing precedence explicit when more than one rule could apply. For example, an existing account owner and a general enquiry queue may both seem eligible. Decide which receives the record and how the other team can see the decision. Include a route for records that need manual review, such as an uncertain account match. The exception owner should have authority to assign a next step, not merely a notification that a rule failed.

Make rejection reasons useful

Agree on specific return reasons: outside the agreed audience, insufficient buying signal, missing contact or request context, duplicate record, already in an active conversation, or unable to reach after the agreed follow-up. Add a note when the category alone cannot explain the decision.

Separate qualification problems from follow-up outcomes. “Outside the agreed audience” suggests revisiting targeting; “no response after follow-up” does not establish that qualification was wrong. “Missing request context” points to collection or data transfer. Each reason should suggest a possible repair.

After a return, marketing may complete context and resubmit the record, continue a suitable follow-up path, or close it with a reason. Require a new fact or a named decision maker before a disputed lead moves between teams again.

Review outcomes together each month

At a monthly review, sample accepted, returned and unclaimed leads, and count outcomes by source and qualification reason. Examine each record as it appeared at handoff, its owner, response state and follow-up result. This helps distinguish weak criteria from missing fields or ownership gaps.

Ask which missing details marketing could collect and which supplied fields sales does not use. Repeated returns from one route call for a check of its criteria and fields; complete but unclaimed records call for a check of queue coverage. Clarify inconsistently used return categories before relying on their counts.

Review delays from the handoff time as well as from acceptance. A short period after acceptance can conceal a long wait in an unmonitored queue. Record how many leads lacked an owner, how many exceeded the agreed response window and which route produced each exception. Compare like periods and routes before changing a qualification rule; a coverage gap does not establish that the leads themselves were poor.

End with one checkable change: a revised criterion, field instruction, routing test or return reason. Give it an owner and effective date. Preserve the previous definition so older records remain interpretable.

A one-page handoff contract

Keep the agreed version beside the records people review. It should state:

• Ready for sales: fit and intent criteria, the handoff trigger and who approves exceptions.
• Required context: minimum fields, their sources and who repairs missing values.
• Routing: the owner or queue rule and the path when no rule matches.
• Acceptance: response states, the response window and who watches unclaimed records.
• Backup: how an unavailable assignee is identified and when reassignment happens.
• Return and review: return reasons, the resubmission rule and review owners.

Test the contract with sample records. Send one complete lead through each important route and confirm its owner and first response state. Then test two failures:

1. Missing owner: Create a qualifying lead that matches no routing rule, or make its first assignee unavailable. Confirm who monitors the resulting record and that any reassignment is recorded.
2. Incomplete context: Create a lead with a contact method but without its required request or qualification reason. Confirm it is held for correction and assigned to the team responsible for completing it.

Repeat these tests when qualification fields, routing rules or queue coverage change. Record the owner and next action even when the lead is not yet ready for sales.