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.
In short
To improve sales productivity and save time in phone prospecting, go after the small tasks around each call: dialing the number, waiting on rings and voicemails, looking up the history before a callback, logging the outcome, writing the summary and scheduling the follow-up. Each one takes a few seconds, but repeated over dozens of calls, they can cost an hour a day. The fixes are simple: prepare your lists, standardize how calls are logged, and let a dialer and an automatic summary handle the repetitive work.
The eight frictions that eat into the day
At Flunter, our goal is to help teams have more useful conversations. Calling several numbers in parallel is the most visible lever. But when we watch sales reps at work, we always find the same small brakes around the call itself.
Friction | What happens | The fix |
Dialing by hand | Copying the number from the CRM or a spreadsheet, typing it, checking it | A dialer that dials for you |
Waiting on rings and voicemails | Listening to a phone ring out, hitting a greeting, hanging up | Parallel calls and voicemail detection |
Looking for notes before a callback | Opening the CRM, finding the contact, rereading the history | Contact record shown before the pickup |
Switching between CRM, dialer and spreadsheet | Three windows, three searches for one prospect | A calling tool connected to the CRM |
Logging the call outcome | Picking a status, typing it, sometimes in two places | One-click outcomes, synced automatically |
Writing the call summary | Rewriting the conversation from memory | AI summary generated after hang-up |
Scheduling the follow-up | Creating a task or reminder by hand, or forgetting it | Tasks and reminders tied to the contact |
Finding a past call | Working out who said what, listening to the whole thing again | Search in the call log |
None of these frictions is dramatic. That is exactly why teams let them settle in.
A worked example: where an hour a day goes
What follows is an illustration, not a statistic. The assumptions are mine, chosen to be plausible for a typical prospecting session. Replace them with your own numbers.
Assumptions: a rep makes 60 calls a day with a 20% pickup rate, which gives 12 conversations (for context on that rate, see our article on the pickup rate). Of those conversations, 6 need a callback.
Friction | Calculation | Time per day |
Dialing by hand | 60 calls × 10 seconds | 10 min |
Waiting on unanswered calls | 48 calls × 20 seconds | 16 min |
Looking for notes before a callback | 6 callbacks × 1 minute | 6 min |
Logging the call outcome | 60 calls × 10 seconds | 10 min |
Writing the call summary | 12 conversations × 1.5 minutes | 18 min |
Scheduling the follow-up | 6 tasks × 30 seconds | 3 min |
Finding a past call | 1 search × 4 minutes | 4 min |
Total | 67 min |
Switching between tools has no line of its own: it is spread across all the others. It is what turns a 3-second entry into a 10-second one.
On these assumptions, the rep spends just over an hour a day on something other than talking to prospects. That time is not wasted: summaries and follow-ups matter. The question is who does them, and how fast.
Before the call: dialing, waiting, getting context
Dialing by hand
Process: prepare your lists before the session, with clean, correctly formatted numbers, so you never copy anything while calling.
Tool: a power dialer dials numbers one by one in list order and moves on automatically. For calls outside a list, the Flunter call companion also lets you dial a number directly, search for a contact in the database, then call them, send them a text or open their record.
Waiting on rings and voicemails
Process: call when your prospects are most likely to answer, and group your calls into sessions instead of spreading them out.
Tool: this is the heaviest item, and the one we built Flunter for. A parallel dialer dials up to five numbers at once (three on the Starter plan) and passes you the first person who answers: the time spent waiting on rings runs in parallel instead of adding up. Voicemails, automated switchboards and call screeners are filtered out by our voicemail detection, an in-house detection engine, tuned continuously on real calls, that decides at pickup. If a voicemail still gets through, Cmd + K on Mac (Ctrl + K on Windows) hangs up, logs the call as "Voicemail" and restarts the session.
Looking for notes before a callback
Process: write your notes for whoever will call back, even if that is you. One sentence on the need, one on the next step.
Tool: with the power dialer, the contact record (name, company, history, notes) appears before the pickup. Getting back into context takes seconds.
During and after the call: logging, summarizing, scheduling
Logging the call outcome
Process: keep a short list of call outcomes, the same for the whole team. If a rep hesitates between two statuses, the list is too long.
Tool: in Flunter, you log the outcome in one click (callback, meeting, not interested, wrong number) and it syncs to the CRM automatically. Outcomes can be customized to fit your sales process.
Writing the call summary
Process: define what a good summary must contain for your team: need, objections, next step. Everything else is optional.
Tool: the AI summary is generated a few seconds after hang-up, covering topics discussed, the prospect's requests, decisions, objections and next steps. It syncs automatically to the CRM, and the call is also recorded and transcribed. The rep rereads and corrects if needed, but no longer writes from scratch.
Scheduling the follow-up
Process: no conversation ends without a dated next step. No date, no follow-up.
Tool: create the task or reminder right away, tied to the contact. With a connected CRM, Flunter tasks are sent to the CRM, so nobody keeps two calendars.
Between calls: switching tools and finding a past call
Switching between CRM, dialer and spreadsheet
Process: decide which tool is the source of truth for what. Lists and history live in the CRM, calls in the dialer, and the spreadsheet stays closed during the session.
Tool: Flunter connects natively to HubSpot, Salesforce, Pipedrive, Close, Boond Manager and Odoo. Lists are imported from the CRM or a CSV file, CRM activities show up during the call, and every call is logged back with its outcome, AI summary and recording. Details are on the integrations page. For teams with an in-house CRM or custom dashboards, the API lets you pull calls and statistics.
Finding a past call
Process: name your campaigns clearly and log an outcome on every call. A well-logged call is easy to find; a call marked "other" gets lost.
Tool: search in the call log takes you straight to the conversation, and accelerated playback saves you from replaying it in full. Sorting contacts by last call brings the people you just called to the top.
Measure before you change tools
Before buying anything, measure. Half a day is enough.
Time a normal session without changing any of your habits.
For each call, note the time spent dialing, waiting and logging.
At the end, count real conversations, not calls.
Repeat the exercise once your fixes are in place, over the same length of time.
The right metric is not calls per day, it is useful conversations per hour of prospecting. To pick your other metrics, see our cold calling KPIs.
Frequently asked questions
How do I save time in cold calling?
By cutting everything around the call: prepare your lists before the session, let a dialer do the dialing, filter out voicemails, log outcomes in one click and automate the summary. Talk time itself should not go down.
How much time do sales reps lose on admin tasks?
It depends on call volume and tools. In our illustrative example at 60 calls a day, frictions add up to just over an hour. The most reliable answer is to time one of your own sessions.
Is a power dialer enough to be more productive?
It removes dialing and chains calls, but it calls one number at a time: you still wait on every ring. A parallel dialer also cuts that wait. Both are included in every Flunter plan.
Does the AI summary replace the rep's notes?
It replaces the writing, not the review. The rep checks the summary and adds what only they know, like a gut feeling about the prospect.
Do I really need to log every call, even unanswered ones?
Yes, but the tool should do it for you whenever it can: in Flunter, a detected voicemail is automatically logged as "Voicemail". Otherwise follow-ups and statistics are skewed. That is why logging should take one click, not one minute.
What you can do this week
Monday: time a prospecting session and fill in the example table with your own numbers.
Tuesday: cut your list of call outcomes down to six or seven statuses at most.
Wednesday: write down in three lines what a call summary should contain.
Thursday: block two fixed prospecting slots and prepare the lists the day before.
Friday: compare conversations per hour with Monday's number.
If dialing and waiting weigh the most in your table, try a parallel dialer on one of your lists. If it is logging and summaries, look at one-click outcomes and AI summaries.