A reply is valuable context, but it is not automatically an opportunity. The handoff should preserve the conversation and make the next action clear to the person taking responsibility.
Classify the request without over-reading it.
Separate requests for information, referrals, objections, future interest and opt-outs. Use the actual words in the reply to explain the classification. “Send specifications” confirms a request for information; it does not prove budget, authority or buying intent.
Answer within approved knowledge.
Use current, approved material for routine factual questions. Pricing, special terms, product suitability or uncertain facts should go to the accountable person. Keep the original thread and the relevant source material together so the owner does not have to reconstruct the context.
Make the handoff complete.
Record company, contact role, mission, expressed need, open questions, owner and agreed next step. Distinguish a proposed meeting from a confirmed booking. In the current setup, meeting arrangements stay with the team; do not describe a suggested time as a completed calendar booking.
IN PRACTICE
Keep expressed interest separate from qualification.
They asked for a brochure. Mark the opportunity qualified and book a meeting.
They requested specifications. Share approved information, identify their role and ask what they are evaluating before deciding the next commercial step.
A request gives you something to respond to. Qualification requires evidence about relevance and an owner willing to progress the relationship.
| Signal | What it establishes |
|---|---|
| Request for specifications | A need for information. |
| Relevant role and application | Evidence of commercial fit. |
| Owner accepts the next step | An accountable handoff. |
Write a handoff that a colleague can understand without opening other tools: who replied, what they said, which mission it belongs to, what remains unknown and who must act next. Keep the original thread linked for context.
A worksheet for your team.
Use this as a starting point. Replace the fields with verified information about your own business.
Company, contact and role: Mission: Original reply or thread reference: Expressed need: Qualification evidence: Approved material shared: Questions or commitments requiring review: Assigned owner: Next step and due date: Meeting status: proposed / confirmed / not requested Owner acceptance:
Before you move on.
- Intent is grounded in the actual reply.
- Open questions and commitments are visible.
- A named person accepts ownership.
- The next step is agreed, proposed or pending—not ambiguous.
Editorial guidance for planning and review. Examples are illustrative. Confirm your workspace’s available controls and configuration before live execution.