Cold Call Wrap-Up & Disposition Code Cheat Sheet
Exact CRM disposition codes, follow-up time windows, next-touch channels, and note templates for every cold call outcome a rep actually encounters. Keeps pipeline hygiene intact in the 90 seconds after the call ends.
How to use it
Print this or pin it in a browser tab next to your CRM. After every call, match your outcome to the table, log the exact disposition code listed, paste the note template, and set the follow-up task before you dial the next number. Review your team's disposition code usage weekly for the first month to catch old habits.
What's inside
- Full outcome-to-disposition-code reference table covering nine distinct call results
- Specific follow-up time windows for each outcome (e.g. call back in 2 business days, not same day)
- Next-touch channel guidance per outcome (call, email, LinkedIn, remove)
- Copy-paste CRM note templates with bracketed fill-ins for every scenario
- Named rules for gatekeeper blocks versus actual buyer refusals
- DNC trigger recognition and immediate action protocol
- Dead number and wrong number handling with record-update instructions
- Two most common post-call logging mistakes with explanations of exactly what breaks when you make them
- Quick-reference decision tree for the nine-second moment of "what do I do now"
- When NOT to use standard disposition codes (bespoke CRM environments)
Why the 90 seconds after the call matter
Most reps mentally move on the moment the line goes dead. That 90-second window, from hanging up to dialling the next number, is where pipeline hygiene silently breaks down. Wrong dispositions corrupt sequence logic, duplicate follow-ups, and mis-attributed "not interested" flags that write off prospects who were never actually spoken to.
This cheat sheet gives you one decision per outcome, made in advance. No thinking required post-call.
The Master Reference Table
| Outcome | CRM Disposition Code | Follow-Up Window | Next-Touch Channel | CRM Note Template |
|---|---|---|---|---|
| Connected, meeting booked | CONNECTED - MEETING BOOKED | Send calendar invite within 15 minutes. Confirmation email same day. | Email (confirmation) | "Spoke with [Name], [Title]. Booked [meeting type] for [date/time]. Confirmed via calendar invite. Decision-making context: [one sentence on situation/need mentioned]." |
| Connected, not interested (said by the actual buyer) | CONNECTED - NOT INTERESTED | No follow-up for 6 months minimum. Set a re-engage task for month 6. | None until re-engage date | "Spoke with [Name], [Title], confirmed decision-maker. Declined. Reason given: [exact words if stated, or 'none given']. Re-engage task set for [date]." |
| Connected, call-back requested | CONNECTED - CALL BACK REQUESTED | Call back on the date/time they specified. If no time given: 2 business days, not same day. | Call (specified time), then email if no answer | "Spoke with [Name], [Title]. Requested call back [on specific date/time OR 'at a better time, scheduled for 2BD']. No objection raised, timing issue only." |
| Voicemail left | VOICEMAIL LEFT | Call again in 3 business days. Do not call back same day or next day. | Email within 2 hours of voicemail | "Voicemail left [timestamp]. Message referenced [one-line hook used]. Follow-up email sent [timestamp]. Next call attempt: [date]." |
| No answer, no voicemail | NO ANSWER - NO VM | Call again in 2 business days. Maximum 6 no-answer attempts before pausing cadence. | Email on attempt 3 if not already sent | "No answer, no voicemail option available [OR voicemail full OR rang out]. Attempt [number] of 6. Next attempt: [date]." |
| Gatekeeper blocked (buyer not reached) | GATEKEEPER - NOT REACHED | Call back in 2 business days. Try a different time of day. | LinkedIn connection request within 24 hours | "Reached [gatekeeper name/role if given]. [Name of target] not available. Reason given: [in meeting / not in / unavailable]. No message left [OR message left with gatekeeper, not a voicemail disposition]. Next attempt: [date], try [earlier/later] in day." |
| Wrong number | WRONG NUMBER - UPDATE RECORD | No follow-up. Update contact record immediately. Flag for data cleanse. | None | "Number [number dialled] confirmed incorrect for [Name]. Update required. Source of number: [CRM field / list / LinkedIn]." |
| DNC trigger (prospect asked not to be called) | DNC - DO NOT CONTACT | Remove from all sequences immediately. Apply DNC flag to record before closing CRM. | None | "Prospect explicitly requested no further contact on [date]. DNC flag applied. No further outreach to be made." |
| Number dead / disconnected | NUMBER DEAD - UPDATE RECORD | No follow-up until number is verified. Research alternative number via LinkedIn or company switchboard. | LinkedIn or switchboard research | "Number [number dialled] dead/disconnected. Alternative number research required. Flagged for data cleanse. Do not re-dial until record updated." |
The Two Most Common Post-Call Mistakes
Mistake 1: Logging "No Answer" when a voicemail was left
These are different disposition codes and they behave differently inside most sales engagement platforms. "No Answer" typically resets the sequence step and allows an immediate retry. "Voicemail Left" should pause the sequence for your defined window (3 business days in this cheat sheet) and trigger the follow-up email step.
If you log "No Answer" after leaving a voicemail, the platform may queue an immediate call-back, you may call again the same day, and you look like you have no idea what you said to someone 6 hours ago. Over a 200-prospect cadence, this compounds into a broken sequence that neither you nor your manager can trust.
Rule: If you heard a beep and spoke words into a phone, it is VOICEMAIL LEFT. Full stop.
Mistake 2: Marking a prospect "Not Interested" after a gatekeeper refusal
A gatekeeper saying "he's not available" or "we're not interested in any calls" is not a buyer disposition. It is a gatekeeper disposition. The actual decision-maker has not been spoken to.
Logging CONNECTED - NOT INTERESTED in this scenario permanently flags a live prospect as dead and removes them from cadences they should still be in. This is one of the most common reasons reps underperform on total meetings booked relative to total dials made: they are disqualifying prospects who were never actually contacted.
Rule: CONNECTED - NOT INTERESTED is only used when you have spoken directly to the identified decision-maker and that person, by name, has declined. Gatekeeper blocks always use GATEKEEPER - NOT REACHED.
Quick Decision Guide: The Nine-Second Check
Ask yourself two questions the moment the call ends:
1. Did I speak to the actual target person?
- Yes, go to question 2.
- No (voicemail, no answer, gatekeeper, wrong number, dead line): use the non-connected disposition codes above.
2. What did they agree to?
- Meeting booked: CONNECTED - MEETING BOOKED.
- Call back at a specific or vague future time: CONNECTED - CALL BACK REQUESTED.
- Clear refusal: CONNECTED - NOT INTERESTED.
- Asked to never call again: DNC - DO NOT CONTACT.
Disposition Code Customisation Note
These codes are written as plain-language labels. Most CRMs (Salesforce, HubSpot, Salesloft, Outreach) let you map custom disposition values. If your CRM uses numeric codes or abbreviated values, print this table, add a column for your internal code, and map them once. The logic and time windows stay the same regardless of what your system calls the field.
If your organisation uses a bespoke or heavily locked-down CRM where you cannot add disposition options, use the note template field to record the outcome in the exact wording above. The note becomes your audit trail.
Minimum Standards for Every Call Log
Regardless of outcome, every call record should contain:
- Disposition code logged before moving to next dial
- Timestamp accurate (do not back-fill at end of day)
- Note template completed with no blank bracketed fields
- Follow-up task created with a specific date, not "someday"
- Sequence step advanced or paused correctly per outcome
- DNC flag applied immediately if triggered (never deferred)
When NOT to Use This Cheat Sheet As Written
- Your team runs a single-touch outbound model with no sequences. The time windows still apply, but some sequence logic notes are irrelevant.
- You work in a regulated industry (financial services, healthcare) with specific FCA or sector guidance on contact frequency and DNC handling. This cheat sheet does not substitute for compliance requirements. Add your compliance rules as a column to the master table above.
- Your CRM auto-logs outcomes from call recording. Verify the auto-classification against these definitions. Auto-log tools frequently miscategorise short calls as "no answer" when a voicemail was in fact left.