A callback is a prospect who told you "not now" rather than "no". It is often the most promising call, and yet it is often the one we get wrong: the prospect remembers you, you no longer remember them. In this article, I share the method I see working in the teams we support: a 30-second checklist before you dial, opening lines that pick up the thread, and a follow-up routine that does not depend on your memory. I also explain how we built the Flunter contact record so that all this context fits on a single screen.
In short
To call a prospect back well, take 30 seconds before dialing to reread the last conversation, their objections and the next step you promised. Open the call by quoting what they told you last time, not by introducing yourself again. Call back at the time they chose, thanks to a dated task created right after the first call. A tool that shows the AI summary, the recording and the history on the contact record cuts that preparation down to a few seconds.
Why callbacks are the most valuable calls, and the most wasted
In cold calling, most of the effort goes into getting a first conversation. When a prospect says "call me back in two weeks" or "send me something and we'll talk again", the hardest part is done: they know you, they have a need, they agreed to a next step. The callback is no longer a cold call.
The problem is the asymmetry. The prospect had one conversation with you. You, in the meantime, had dozens. They remember what they told you. You vaguely remember a company name.
In the field, it is always the same set of mistakes:
Starting from scratch: "Hi, I'm Julien from such and such, we help companies...". The prospect immediately understands you no longer know who they are.
Asking a question you already asked: "How many people are on your sales team?" when they told you last time.
Calling back too late: "in two weeks" becomes six weeks, and the project moved on without you.
Forgetting what you promised: a document, a price, a demo for a colleague.
None of these mistakes come from a lack of talent. They come from a lack of context when you dial. It is an organization and tooling problem, which is why we spent so much time on it at Flunter.
The 30-second checklist before a callback
Before each callback, I recommend going through five points. If your tool is well organized, it takes less than a minute, often about ten seconds.
What to check | Where to find it | Why it matters |
The last conversation: date, length, who spoke | Contact record history | You know whether you are picking up a real conversation or a 40-second exchange |
The call summary | AI summary or your notes | You get back the need, the context and the prospect's own words |
The objections | AI summary, notes or recording | You prepare the answer instead of discovering it a second time |
The promised next step | AI summary, notes, task | You keep your word: document sent, date set, person to include |
The open task | Tasks and reminders | You know why you are calling today and not another day |
If one point is still unclear, replay only the relevant part of the recording, or search for the word in the transcript. Replaying a full twenty-minute call before every callback is not sustainable over a day.
How to open a callback: lines that pick up the thread
The rule is simple: your first sentence must prove you remember the conversation. Quote what the prospect told you, the date or the reason for the callback. Not your pitch.
When the prospect asked you to call back on a specific date
"Hi Ms. Leroy, it's Julien from Nova. We spoke last Thursday, you asked me to call you back after your committee meeting on Tuesday. Did it go ahead?"
When you promised to send something
"Hi Thomas, it's Julien. On Monday I sent you the pricing for a team of six reps, as agreed. Have you had a chance to look at it?"
When the prospect raised an objection
"Hi Mr. Garnier, it's Julien from Nova. Last time you told me the real blocker was the integration with your CRM. I checked with our team and I have a clear answer for you."
Lines to avoid
"Sorry to bother you again...": it sounds like an apology.
"Do you remember me?": you put the prospect on the spot.
"I just wanted to check in": there is no concrete reason to call.
For the structure of the rest of the call, you can start from our cold call script guide: discovery is shorter on a callback, since some of the answers are already in your summary.
When to call back: tasks, reminders and sorting by last call
The best time for a callback is the one the prospect chose. If they said "Tuesday after 2 pm", that slot matters more than any calling-time statistic. For other cases, our article on the best time to call B2B prospects gives benchmarks by day and hour.
Create the task the moment you hang up
A callback that is not written down right away is a lost callback. When you log the call outcome, create a dated task, with the time if the prospect gave one, and one line saying why you are calling back. "Call Ms. Leroy" is not enough. "Call back after the committee on the 14th, she approves the training budget" is.
When the prospect stays vague ("call me next week"), pick a specific day yourself and say it: "I'll call you Thursday morning, does that work?". The prospect will remember, and so will you.
Sort contacts by last call
For follow-ups without a set date, sort your contacts by last call date. You see at a glance who has not been called back for too long. We added this sort to Flunter in the spring, because teams asked for it.
A concrete example
Take a rep who ends her week with 18 callback tasks. On Monday morning, she opens them in date order: 7 have a specific time set by the prospect, 11 only have a day. She blocks the 7 time slots in her calendar, then groups the other 11 into a one-hour block late in the morning, before her cold calling session. For each callback, she spends 30 seconds on the contact record. Her callback block takes about 9 minutes of preparation in total, instead of hunting for her notes while the prospect is already on the line.
What the contact record should show you
For the checklist to fit in 30 seconds, everything has to be in one place. That is what we set out to do with the contact record in Flunter: from the record, you get the AI summary, the call recordings, the transcripts and the history of exchanges with the contact.
In practice, here is what each element brings to a callback:
The [AI summary](/en/product/ai-summaries/) is the first thing to read before calling back: it captures the key points of the conversation a few seconds after you hang up.
The [recording and transcript](/en/product/call-recording-transcription/) help when the summary is not enough: finding the exact wording of an objection, a figure, a name. Faster playback of recordings saves you from listening to everything at normal speed.
The history shows every attempt and conversation, not only the last one. Three unanswered calls since the last conversation changes how you open.
Notes and custom fields keep what AI cannot guess: your own read of the deal, the assistant's name, the end date of the current contract.
During a session, the power dialer shows the contact record (name, company, history, notes) before the prospect picks up. And if you are looking for a specific call weeks later, search in the call log takes you straight to it. Outside a session, the call companion lets you search for a contact in your base and open their record to find their notes quickly before calling back.
What we are after is that a rep never has to say "hold on, let me find my notes" while the prospect is on the line.
Syncing tasks and context with your CRM
The context of a callback should not live only in your calling tool. If a colleague takes over the account, or if the prospect calls someone else back, everything has to be visible in the CRM.
In Flunter, the call outcome, AI summary, notes and tasks are pushed to the CRM after each call, and the direction of task sync depends on the tool (details are on our integrations page):
CRM | Tasks |
HubSpot | Both ways (HubSpot to Flunter every 3 hours) |
Salesforce | Both ways |
Close | Both ways (Close to Flunter every 3 hours) |
Pipedrive | Flunter to Pipedrive only |
Boond Manager | Flunter to Boond Manager |
Odoo | Flunter to Odoo (scheduled activities) |
If your team creates its callbacks in the CRM, check this sync direction before deciding where you work day to day.
Frequently asked questions
How many times should you follow up with a prospect by phone?
There is no universal number. As long as the prospect gave you a reason to call back, call back on the agreed date. If they stop answering, space out your attempts and change the time slot. If they clearly say no, stop and log it, so nobody on the team calls them again.
How long should you wait between two follow-up calls?
First, whatever the prospect set. With no agreed date, a few business days between two unanswered attempts is a reasonable pace, varying the time of day. After a real conversation, call back within the timeframe you announced during the call.
What should you say when you call a prospect back?
Start with what they told you last time: the reason for the callback, their request or their objection. Then bring what you promised (an answer, a document, a date) and suggest a concrete next step.
How can you track prospects without a CRM?
A calling tool that keeps history, tasks and summaries per contact already covers most of the follow-up. A spreadsheet can do for a small list, but it keeps neither recordings nor summaries, and it quickly gets out of sync once several people use it.
What you can do this week
List your overdue callbacks: sort your contacts by last call and spot those who were waiting for a callback you never made.
Rewrite your tasks: every callback task should say why you are calling back, not just who.
Prepare three opening lines based on the examples above, adapted to your most frequent situations.
Block a callback slot every day, before your cold calling sessions, and set yourself a daily goal of callbacks handled.
Try the 30-second checklist on your next ten callbacks, and compare the number of meetings booked with your usual callbacks.
If you want to see how the contact record, tasks and AI summaries fit together in Flunter, these features are included in every plan, starting at €89 excl. VAT per license per month. Details are on the pricing page, and to measure the effect of your callbacks on your results, our article on cold calling KPIs gives you the right metrics.