A sales handoff should tell the assigned representative what the prospect asked for, what has already happened, and what action is due next. Store this information on the enquiry record and use a short notification to bring the owner to it.
Picture an enquiry that says, “We need a patient portal for three clinics. We already use an appointment system. Can you tell us what integration would involve?” The rep receives a notification with the sender's name and a generic “new lead” label. They ask the prospect what they are looking for, and the prospect has to repeat the original message. The assignment worked. The handoff lost the context.
What should a sales handoff include?
| Field | What it helps the owner do |
|---|---|
| Enquiry ID and submitted time | Find the correct request and assess its age |
| Request summary and submitted requirement | Prepare a relevant first response |
| Contact and account match status | See whether there is an existing relationship |
| Previous interactions on this enquiry | Avoid repeating questions or work |
| Campaign and landing page, if captured | Understand what the prospect was reading |
| Owner, next action and due time | Know who is accountable and when to act |
| Open questions | Focus the first conversation on what is missing |
Keep the summary short enough to scan. Keep a reference to the underlying enquiry so the owner can check the wording. Label assumptions as such. For instance, a visitor who viewed an integration page may be researching options. That page view does not establish their preferred platform.
A worked handoff for a patient portal enquiry
Enquiry ENQ-3024. The prospect operates three clinics and asks how a patient portal would integrate with their existing appointment system. They requested an integration explanation before discussing a quote. The appointment platform and authentication requirements are open questions. The integration specialist owns the enquiry. The first response is due by 4 PM IST.
From that summary, the representative can prepare a specific reply: “Which appointment system do you use, and should the portal support booking across all three clinics?” The same context helps a second representative take over if the first is away.
Handle reassignment and late updates
Save the owner and action due time on the enquiry. When ownership changes, update any open task according to your reassignment policy. Record the previous owner, new owner, change time, and reason. Use the same enquiry ID so the new owner sees the original conversation.
Decide what happens when more information arrives. A new message about the same request should update the enquiry and notify its current owner if action is needed. A separate request from the same contact may need its own enquiry record and owner. Treat these as two different workflows.
If a notification fails, retry that notification without changing ownership. For chat or email alerts, send only the necessary summary and a reference to the restricted CRM record. Keep attachments and sensitive details in the appropriate system.
Verify the handoff from the rep's perspective
Give someone who did not build the workflow a test enquiry and ask them to prepare the first response. Check whether they can identify the request, see which questions have already been answered, and find the next action without searching multiple inboxes.
Then test reassignment, a late reply, a notification failure, and two enquiries from the same contact. Track unowned enquiries and overdue first responses after launch. These measures reveal whether context reaches the person who can act on it.
