Post-Call Follow-Up After a No-Close
The short answer
40-60% of calls end with no decision. What you send in the next 15 minutes decides if internal conversations include you. 98% open, replies at 2-3x cold email. Highest-value unworked surface: money to create meeting already spent; every hour you wait costs accuracy.
6 use cases in this category
Trigger
Event in your CRM
Under 9 seconds
Send iMessage
Result
Reply in the thread
Key takeaways
- Sales calls end no-decision 40-60% of the time.
- Voice memos arm the champion to re-explain.
- Minute 15: recap and one ask. Hour 3: asset sent.
- A voice memo carries 90 seconds of the rep's tone, playable and quotable.
- Minute 15: 'hey marcus, two things: 14-day window, SOC 2 report.
- Create stage 'Post-Call No Close' and trigger on change.
Where iMessage runs in the funnel
Most deals stall, not lose
Sales calls end no-decision 40-60% of the time. 6-10 decision makers per deal; you get 5-6% of their time. Everything else is internal: a champion explaining to a CFO who never saw your demo.
Multithread the account and surface the stall
Voice memos arm the champion to re-explain. A 90-second walkthrough survives a room you're not in; 700 words doesn't. Short replies feel normal in text; 'let me talk to the team' stays buried in email.
Nine sends over 60 days
Minute 15: recap and one ask. Hour 3: asset sent. Day 1: voice memo plus 'who's in room?' Day 3: add stakeholder. Day 5: one number or screenshot. Day 8: ask if deal slipped. Day 14/30: light touches.
Within 15 minutes
- Message
- Two-line recap plus the one thing they asked for
- What it's doing
- Lands while the call is still in short-term memory
Same day, +3 hours
- Message
- The asset, sent in-thread as a file or link
- What it's doing
- Kills the waiting-on-you stall before it forms
Day 1
- Message
- Voice memo on the hard part, plus "who else is in the room?"
- What it's doing
- Arms the champion and opens the multithread
Day 3
- Message
- Group thread with the second stakeholder
- What it's doing
- Puts you in the room instead of being described in it
Day 5
- Message
- One number, one customer, or one screenshot
- What it's doing
- Reduces the fear of choosing wrong
Day 8
- Message
- The direct question about the real stall
- What it's doing
- Converts silence into information
Day 14
- Message
- Timeline check with a specific date attached
- What it's doing
- Creates a next event on somebody's calendar
Day 30
- Message
- Relevance ping tied to something that changed
- What it's doing
- Holds the thread without restarting it
Day 60
- Message
- Budget-cycle check-in
- What it's doing
- Catches the deal when the money frees up
Voice memos beat PDFs in a room you're not in
A voice memo carries 90 seconds of the rep's tone, playable and quotable. Read receipts show attention vs authority gap. Add second stakeholder early; easier than cold email to the boss.
Copy: short, one idea, new info each time
Copy: short, one idea, new info each time
Minute 15: 'hey marcus, two things: 14-day window, SOC 2 report. when's review?' Day 8: 'slip to Q4? Either's fine, I'd know.' Every message carries new info or question.
Setup: stage trigger, nine steps, pause on reply
Setup: stage trigger, nine steps, pause on reply
Create stage 'Post-Call No Close' and trigger on change. Nine steps, 15-min to 90-day delays. Pause on inbound reply; automation kills the channel. Exit on booked meeting.
Setup happens during white-glove activation rather than on your side. Bring the CRM you already run and we will map the triggers on the call.
See it wired to your CRMMeasure reply rate per step and multithread success
Measure reply rate per step and multithread success
Track no-decision rate QoQ. Reply rate per step, not per sequence. Multithread succeeds when second contact replies. Read the stall reasons monthly.
Reply rate on step 1
- Read it as
- Whether the call actually landed
- What to do
- Compare directly against your old recap-email reply rate
Read, no reply at 48 hours
- Read it as
- Attention is fine, authority or budget isn't
- What to do
- Pull the multithread step forward to day 2
Second stakeholder in thread by day 7
- Read it as
- The multithread worked
- What to do
- Track per opportunity, never per contact
Stall named out loud by day 10
- Read it as
- You have information instead of a forecast guess
- What to do
- Log the reason as a CRM field and report on it monthly
Days from call to close
- Read it as
- Whether the thread compressed the cycle
- What to do
- Segment closed-won with the sequence against without
Frequently asked questions
Is texting 15 minutes after the call too aggressive?
No. It's inside an existing conversation, not cold. They spent half an hour with you. A two-line recap reads as competence. Aggressive is volume without content.
Do I need consent to text after a call?
Yes. TCPA governs all business texting. Apply your SMS consent standard. STOP auto-enforced account-wide per April 2025 FCC rules.
Do I need A2P 10DLC registration?
No. A2P governs SMS, not iMessage. That's a registration distinction, not consent exemption. TCPA still applies; sequence isn't behind carrier approval.
Should the sequence be automated or hand-written?
Automated steps, human replies. When prospect replies, pause automation and rep owns thread. Automating replies to live humans kills the play.
Stop losing no-decision deals
No-decision rate is your cheapest number to move because the meeting cost is already spent. $249 per line per month or $1,949 per year, unlimited iMessages (50 opted-in / 30 cold new contacts a day), no per-message fees, no A2P registration. White-glove setup waived on annual. Book a walkthrough and we'll map the nine-step sequence.