Name the next owner of the enquiry.
A useful handover says who will review the brief and what they need.
Start with the responsibility
Agree which team takes the next conversation before adding another enquiry destination. Product advice, local installation review, and commercial approval can belong to different people. A destination should reflect the responsibility you actually want that person to take.
Send the useful context
A handover needs the current configuration, the customer’s question, and the proposed next step. Include location or channel information only where it helps route the enquiry. Review the fields with the receiving team so the brief does not leave them reconstructing the conversation.
Keep the customer informed
Explain the expected next step in plain language. A request for a product discussion should not look like a confirmed appointment or order. When timing depends on team review, say what will be reviewed and avoid promising a response window that has not been agreed.
One useful question.
Choose one sales channel and write down who owns the enquiry immediately after it arrives.
Save this note ↓