Outbound resource

Sales appointment qualification checklist and handoff template

Agree what a useful meeting looks like before a campaign starts. This checklist helps SDRs and account executives record fit, the reason for meeting and the information still needed, without treating a calendar booking as an opportunity.

Editorial update:

Use the template ↓Discuss your outbound plan →

Copyable SDR-to-AE handoff emails and CRM fields

The first two drafts have different audiences: keep internal qualification notes out of the prospect introduction. Replace every bracket and verify recipients, facts and links. The six CRM fields below preserve the supporting record; these are original planning templates, not tested conversion winners.

  1. Internal handoff email to the account executive

    Subject: Handoff for review: [account] / [meeting date] Hi [AE name], [Prospect name and confirmed role] booked [date, time and time zone] to discuss [agreed topic]. Why they agreed: [quote or faithful summary] Confirmed fit: [criterion, evidence and source] Still unknown: [question; do not infer budget or authority] Commitments already made: [material/action, owner and date] Meeting and conversation record: [internal CRM link] Please review against [criteria version] by [agreed date] and record accepted, pending or rejected with the reason. Until ownership is confirmed, [named owner] handles scheduling and outstanding questions. [SDR name]

  2. Prospect-facing introduction after ownership is confirmed

    Subject: Your [agreed topic] conversation with [AE name] Hi [Prospect name], As discussed, I am introducing [AE name], who will join our conversation about [agreed topic] on [date, time and time zone]. I have shared your question about [confirmed priority] so we can pick up from there. [AE name] will [specific agreed next action]. Please reply here if the agenda or timing needs adjusting. [SDR name]

  3. 1. Account and fit

    Company and CRM record: [name / internal link] Acceptance criteria version: [version/date] Matched required criteria: [criterion / evidence / source / observed date] Unresolved prerequisite: [unknown or none] Evidence owner and next check: [person / action / due date]

  4. 2. Participant and role

    Attendee: [name and role] Relationship to workflow: [confirmed responsibility] Other stakeholders mentioned: [confirmed names/roles or unknown]

  5. 3. Reason for meeting

    Prospect's question or goal: [quote or faithful summary] Agreed agenda: [topic] Do not assume: [unconfirmed pain, budget or authority]

  6. 4. Timing and open questions

    Timing stated by prospect: [answer or unknown] Remaining discovery questions: [questions] Materials promised: [item and owner]

  7. 5. Meeting logistics

    Meeting ID and original booking: [stable reference] Scheduled time and time zone: [details] Invite and conversation record: [internal links] Receiving owner and review due date: [name / agreed date] Reschedule linked to original meeting: [reference or not applicable]

  8. 6. Post-meeting decision

    Meeting status: [held / no-show / cancelled / rescheduled / not yet due] Held date, if applicable: [timestamp] Sales acceptance: [accepted / pending / rejected] Criterion checked and supporting evidence: [rule / note or source / date] Reason code: [criteria met / missing evidence / account mismatch / role mismatch / unsupported use case / other explained reason] Next action, owner and due date: [details] Reviewed by and at: [owner / timestamp] Prior decision and reason for change: [reference or first review]

Separate meeting stages
3
Handoff fields
6
Acceptance owner
Named

Sales acceptance decisions and the next action

Scroll the table sideways to compare all columns.

Sales acceptance decisions and the next action
DecisionEvidence to retainNext action
AcceptedEach written required criterion is met; receiving owner records the evidence and review timeAssign the agreed sales next step. Apply separate opportunity-creation rules.
PendingA required criterion is unknown or conflicting; name exactly what is missingAssign an evidence check and review date. Do not count pending as accepted or automatically reject it.
RejectedA confirmed mismatch to a named requirement; preserve the source and explanationRecord the reason and an appropriate close-out or later-review action. A blank field alone is not a confirmed mismatch.

Use agreed definitions for each stage

For the reporting convention in this guide, booked means an appointment was scheduled; held means the conversation occurred; sales-qualified means the receiving sales owner accepted it against agreed criteria. These are separate fields. A prospect can attend and still be a poor fit, while a good-fit account may need more discovery before an opportunity is created.

Qualify enough to make the meeting useful

Confirm account fit, the participant's relationship to the workflow and the reason they want to talk. Ask about timing as a question, not a condition you silently assume. Some offers require budget confirmation before a meeting; others use discovery to establish the business case. Put that choice in the written acceptance criteria so the SDR does not invent an answer to satisfy a quota.

Let the receiving owner accept or return the handoff

Name the person responsible for reviewing meeting notes and give them a way to record an accepted, pending or rejected outcome with a reason. Rejection reasons such as wrong account, wrong participant and no relevant use case call for different fixes. Preserve the original notes when a status changes so the team can see what was known at booking time.

Keep internal review separate from the buyer introduction

The internal email asks the receiving owner to review evidence; it is not proof that the handoff was accepted. Link to the CRM record instead of forwarding an entire thread containing unrelated contacts or internal judgments. After the owner confirms responsibility, use the separate introduction only if that change was discussed with the prospect. Do not expose qualification scores, rejection reasons or internal CRM links in the buyer email.

When the receiving owner has not acknowledged the handoff

Keep a named interim owner for scheduling and promised materials. At the agreed review deadline, ask the designated backup to resolve ownership; do not assume that an unread email or a calendar invitation transferred responsibility. Record who accepted the action and when. If the meeting changes, update the existing record and notify the responsible colleague through the established internal workflow.

Set the acceptance agreement before using the checklist

Write the required account, participant and use-case criteria with the receiving sales owner. Separate hard exclusions from preferences and questions that can wait for discovery. Set a review deadline appropriate to your process and a named backup for absence; this guide does not prescribe a universal response-time commitment. Keep booking-time notes as a snapshot, then add dated decisions rather than overwriting the evidence. Missing a review deadline creates an overdue task, not automatic acceptance.

Worked handoff: a fictional dispatch software meeting

Illustrative example only, not a LeadFlow customer or result. Assume the offer requires UK delivery operations, a relevant dispatch stakeholder and a workflow supported by CSV import. Budget confirmation is a discovery question, not a hard requirement. After a held call, an operations manager confirms all three requirements in the call notes; sales can accept the handoff under this written rule even while budget is unknown. If the import requirement is unresolved, mark pending and ask the technical owner to confirm it by an agreed date. If the prospect confirms a mandatory live integration the product cannot support, reject with an unsupported-use-case reason. The same account can move from pending to accepted or rejected when evidence arrives; retain both decisions and their dates.

Keep meeting attendance separate from sales acceptance

A no-show does not prove the account is a poor fit, and attendance does not prove qualification. Record the meeting outcome independently, keep reschedules linked to the original meeting and make the acceptance decision against evidence. For reporting, export the stable meeting and prospect references, attendance date, decision timestamp, criteria version and reason. Use the reporting template for denominators and observation windows rather than treating every calendar event as another qualified prospect.

Action checklist

Before marking a meeting ready

  • Account matches the written ICP

    Record which criteria match and any unresolved prerequisite. A correct title is insufficient.

  • Participant has a relevant role

    Ask how they relate to the process. Do not assume final authority from seniority.

  • Reason to meet is explicit

    Confirm the topic the prospect expects to discuss so the sales call does not start with a different pitch.

  • Logistics and next owner are clear

    Check the time zone, invite details and internal owner. Record reschedules separately from completed conversations.

  • Open questions remain visible

    Unknown budget or timing should be marked unknown, with the next discovery question attached.

Who this helps

  • SDR teams agreeing meeting standards with account executives
  • Founders reviewing outsourced appointment setting
  • Revenue teams separating activity from qualified pipeline

Work through the process

  1. 01

    Agree acceptance criteria

    Choose the required account, role and use-case conditions together with the sales owner. Define how unknowns will be handled.

  2. 02

    Capture the prospect's words

    Use a short quote or a faithful summary for the reason to meet. Mark your interpretation separately.

  3. 03

    Send the handoff

    Attach the conversation context, agenda, time zone and remaining questions to the meeting record.

  4. 04

    Close the feedback loop

    After the call, record held status and the sales owner's decision. Review rejected reasons by source and segment.

Questions and answers

Does a booked meeting count as an SQL?
Only if it independently meets your agreed SQL criteria and the owner accepts it. In this guide, booking status and sales qualification are recorded separately.
Must every prospect have a confirmed budget?
That depends on your offer and sales process. Specify whether budget is required before booking or is a discovery question. Never fill the field with a guess.
How should we count a rescheduled call?
Keep one meeting record or link the replacement to the original. Update its date and status so a reschedule does not appear as an additional unique meeting.

Sources and editorial notes

Original AI-assisted editorial templates and planning conventions prepared for LeadFlow. Examples are illustrative; they are not independently tested results, customer evidence or performance benchmarks. Check facts and adapt the material to your own workflow before use.

Keep reading