5 Things to Include When Handing a Lead to Sales

A new owner should not have to search several inboxes to find out what a potential customer asked. A useful handoff preserves the request, separates facts from guesses and makes the next action clear.

This is about the information passed between people, not another lead-scoring system.

1. The Original Request

Pass along the person's own message or a link the receiving salesperson is allowed to open. Include when and where it arrived. A summary helps someone scan the inquiry, but it should not replace the original words when details matter.

Don't turn "we may review this next quarter" into "ready to buy next quarter." Preserve uncertainty. If a form field was blank, record it as unknown rather than filling it from an assumption.

Share only information relevant to the inquiry and permitted for that recipient. Internal access isn't a reason to copy unrelated personal details into a sales note.

2. A Short, Factual Summary

Use a consistent order: what the person wants, what they have already been told, what is confirmed, what is still unknown and what should happen next.

For an invented example: "Asked whether the service covers two locations. We confirmed receipt only. Location addresses and start date are not yet known. Next step: ask which locations need support."

That is more useful than "hot lead" because it tells the salesperson what to do without inventing buying intent. If you include a qualification label, explain the evidence behind it.

3. Promises Already Made

Record any price, deadline, availability or follow-up promise already communicated, with its source. Don't hide an agreed commitment inside general notes.

Label suggested next steps as suggestions until someone accepts them. "Could offer a call" and "call booked for Tuesday" are different facts. Include the actual date, time and time zone for a booked meeting, not just a relative weekday.

If an earlier message contains an error or an unapproved promise, flag it for the responsible person. Don't let a cleaner summary erase the issue.

4. The Current Owner

Name the receiving owner and the next action in the shared record. Decide how the team will recognize acceptance: for example, an explicit status change or acknowledgement in the agreed system.

A forwarded message is evidence that something was sent, not proof the new owner has taken it on. Keep the original owner responsible until the team's agreed transfer condition is met.

Avoid sending the same customer separate replies while the transfer is unresolved. Check the latest conversation before acting.

5. The Next Action and Acceptance Check

Write an action someone can carry out: ask for the two location addresses, check service coverage, then reply through the original conversation. Add a date only when it reflects a real agreement or your team's response rule. Give the receiving person a way to mark it accepted or completed.

Ask someone who did not handle the original inquiry to read the note. Can they answer what the person asked, what has already happened and what they need to do next? Can they open the source without requesting extra access?

Fix missing context in the record rather than relying on a private explanation that the next person will never see.

Practice with a Handoff Someone Can Use

Write a note for an invented inquiry: "A local tutoring business asks whether monthly support covers two locations. We sent an acknowledgement only. Budget and start date are unknown. The original form is linked. Sam owns the next reply and will ask which locations need support."

Have a colleague check the five parts against the original request. Remove an assumption if it can't be traced to a message or record. Check the link using the access the receiving person actually has.

Then add a change: the potential customer replies before the handoff is accepted. Decide how that new message reaches the current owner. A useful note must stay connected to the conversation as it changes.

If you're moving this information between systems, this migration overview explains why activities, notes, permissions and workflows matter alongside contact records. It's background reading from a CRM provider, not a recommendation to change tools.

---