Outbound Messaging
Part of Sales development for B2B teams
Choosing a useful outcome beyond booked meetings
Choose a sales development outcome that reflects appropriate next decisions, including accepted discussions, useful referrals and justified closes.
For an initial sales development conversation, a useful outcome is an appropriate, documented next decision. It may be an agreed sales discussion, a focused information check, a referral to the customer’s account owner or a justified close. A calendar booking records an action; on its own, it does not show the action was useful.
Define a useful next decision
Write criteria another person can apply to a record. For a proposed sales discussion, ask whether:
- the prospect described an issue, goal or question relevant to the offer;
- no confirmed requirement rules the offer out;
- the next discussion has a stated purpose;
- the prospect agreed to it; and
- the person who will continue it accepts the handoff.
Keep unknowns visible. An early conversation may justify a specialist check without establishing budget, timing or a purchase decision. A polite agreement to meet does not make an unrelated enquiry relevant.
Count sound decisions without meetings
A representative may answer a factual question in writing, refer an existing customer to their account owner, identify a condition the offer cannot meet or close contact at the prospect’s request. Record these decisions and their reasons, so sensible stops are not hidden by a booking count.
One review method classifies each conversation by its next decision: accepted sales discussion, focused information check, customer-owner referral, deferred by the prospect or closed as irrelevant. The labels are examples; choose categories that describe the decisions your team actually makes.
Outcomes of Initial Sales Development Conversations
- Accepted sales discussion
- Agreed meeting with clear purpose and relevance
- Focused information check
- Answering a factual query without a meeting
- Customer-owner referral
- Referral to existing account owner with context
- Deferred by prospect
- Prospect requested delay; no immediate action
- Closed as irrelevant
- Offer does not meet prospect’s needs; documented reason
Make acceptance consistent
Ask the representative and receiving owner to apply the criteria to the same records. If their decisions differ, clarify the rule before using it to assess work. One person may count any attended meeting while another expects a relevant question from the prospect.
Give handoff acceptance an owner and a decision point. Record a returned handoff and why it was returned: poor fit, missing context or a change in the prospect’s plans. Do not recast a sound initial decision solely because a deal later fails for reasons the representative could not have known.
Key Principles for Consistent Handoff Acceptance
- Owner of handoff acceptance
- Designated person responsible for accepting handoffs
- Decision point for handoff
- Clear criteria applied consistently across team
- Record returned handoffs
- Include reason: poor fit, missing context, changed plans
- Do not recast valid decisions
- Even if deal later fails due to unknown factors
Watch the side effects
Keep booked meetings visible as an activity signal, and review whether agreed meetings took place and served their stated purpose. Watch declines, opt-outs and complaints for signs the chosen outcome encourages unwanted contact. Respect a prospect’s request to stop contact, whatever outcome target is in use.
If real cases expose ambiguity, update the definition and record when the new wording starts to apply.
