Blog

A sales rep with a headset peels off a callback sticky note, smiling

"Call me back in September": following up with a prospect without being pushy

June. A prospect tells me: "Look, now's not a good time, call me back in September." I hang up happy. He didn't say no. September comes, then October. When I finally call, he says: "Oh right… January would be better, actually." I shared that scene on LinkedIn and hundreds of salespeople recognised themselves. Because we all have a graveyard of "call me back later" in our CRM. Here is the method I use today to follow up with a prospect without being pushy, and above all without losing them.

  • Title card: cold call or cold email

    Cold call or cold email: which channel books more meetings in 2026?

    Every year, someone declares cold calling dead. And every year, the teams with full calendars have a phone in their hand. Email is not dead either: it has become more demanding, and plenty of sequences end up in a folder nobody opens. Here is when each one wins, how to work out your real cost per meeting, and the three-week sequence that combines both. Full disclosure: Flunter builds a parallel dialer, so we have an opinion. We still tell you when email is the right call.

  • Atelier produit chez Flunter : une commerciale explique son besoin à l'équipe produit

    How we build a prospecting tool with the reps who use it

    I'm Florian, Head of Product at Flunter. My job is to decide what we build, and above all what we don't. In this article, I explain how sales reps' needs reach us, how we sort them and what we shipped in spring 2026 thanks to them. I also talk about what we refuse to build, because that is often where a cold calling tool shows what it is worth.

  • Un commercial détendu au casque pendant un appel, bureau rangé, collègue débordée en arrière-plan

    The small frictions that can cost sales reps close to an hour a day on the phone

    When people talk about sales productivity on the phone, they usually think about call volume first. What I see in the teams we work with is that time mostly slips away between calls: dialing, waiting, looking for a note, filling in the CRM. Taken one by one, these frictions last a few seconds. Added up over a day, they can get close to an hour. Here are the eight we see most often, a worked example to measure them and, for each one, the fix on the process side and on the tool side.

  • Une responsable sales ops et un commercial trient et vérifient un fichier de prospection

    Preparing a clean cold calling list: formats, duplicates and import

    A calling session is often won or lost before the first call, when the list is prepared. Numbers without a country code, duplicates, switchboards mixed with direct lines, people who asked not to be called again: every dirty row costs time on the phone. In this article, I share what I see with the teams we work with at Flunter: the columns that matter, the right number format, cleaning duplicates and opt-outs, CSV pitfalls and importing from the CRM. The goal is simple: a list you can call without stopping every five minutes.

  • Un manager et une commerciale réécoutent ensemble un appel après la session de prospection

    After a calling session: the 15-minute debrief

    A calling session almost always ends the same way: you close the tab, move on to email, and forget what was said. That's a shame, because right after the session is when you learn fastest. In this article, I suggest a 15-minute debrief routine: two calls to listen back to, one pattern to look at, three numbers to check, a grid to score yourself and one decision for the next session. I also show how we designed Flunter so this debrief takes a quarter of an hour, not an hour.

  • Une commerciale consulte la fiche d'un prospect sur sa tablette avant de le rappeler

    Calling a prospect back: get the context in 30 seconds before you dial

    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.

  • Un commercial relit le résumé de son appel avec une collègue avant de l'envoyer au CRM

    Sales call summary: what an AI call summary should contain to be useful in your CRM

    A sales call summary has one job: let anyone pick up the deal without listening to the call again. In most CRMs I see, that is far from the case: "interested, call back", and nothing else. AI summaries solve the typing problem, not always the content problem. Here is the structure we recommend at Flunter, a template to copy, a before/after example and what should actually go to your CRM.

  • Une responsable RevOps montre à un commercial comment piloter sa prospection depuis un assistant IA

    MCP for cold calling: prepare your calls from Claude

    MCP lets an AI assistant like Claude read from and write to your tools, instead of working only with what you paste into the chat. For a team that prospects by phone, that means pulling up a contact's history, preparing a call list or creating follow-ups in one sentence. Flunter publishes an MCP server built on its API. This article explains what MCP is in plain terms, what our server can do today, how to install it and where its limits are.

  • Coach logging a split on her stopwatch at the edge of the track as two runners go by

    Cold calling KPIs: the metrics to track (and the ones to ignore)

    A prospecting dashboard with fifteen metrics is one nobody reads. A single number, call volume, sends everyone running in the wrong direction. In between sits a handful of KPIs that really tell you where your cold calling stands and what to fix. This guide covers the ones to track and how to calculate them, the ones that mislead, then a simple routine to run an SDR team on these numbers.