Cold calling software: what to look for, and what to ignore
What matters when choosing cold calling software for an SDR team: numbers, inbound routing, recording and consent, call outcomes, and one forgotten question.
Cold calling software is a crowded category where most products look identical on a feature grid and differ enormously in use. Here is what separates them in practice, roughly in order of how much it will matter six months in.
1. Numbers assigned per rep, not shared
Anyone can place a call. The operational question is how numbers are managed.
Can numbers be held at account level and assigned to individual reps, one to one? Shared caller IDs destroy callback attribution — the prospect rings back and nobody knows whose conversation it was. Can you hold local area codes your prospects recognise, and release numbers without losing the call history attached to them?
2. Who answers when a prospect calls back
Almost every evaluation focuses on outbound. Then the prospect calls back, and the system has no opinion about who should answer. Ask specifically: when a prospect returns a call, who does it ring? A good answer is a precedence chain:
Inbound routing precedence
- 1
Rep with the lead reserved
Whoever is currently working the lead gets the call first.
- 2
Last outbound touch
Else the rep who last called, emailed or texted — across channels, so an SMS counts.
- 3
Wider fanout
If that rep does not pick up, ring the team. Voicemail is not acceptable for cold outbound.
- 4
Missed call logged per rep
An unanswered callback leaves a trace on the lead, so the conversation is not lost.
3. Recording, consent and retention are three things
Recording
One side or both. Dual-channel costs more and is worth it for coaching.
Consent
Rules differ by country; some require all parties to consent. The system should store the consent event and timestamp, even if the recording fails.
Retention
A retention window enforced automatically. Recordings are sensitive personal data — keeping everything forever is a GDPR liability.
Transcription is worth having, but check the language. English-only transcription is useless for a multilingual operation.
4. Call outcomes that keep their meaning
Most tools offer a disposition dropdown. Look for whether the outcomes are structured and whether anything downstream uses them. Two distinctions pay for themselves:
- Bad number vs wrong number. Bad number means not in service — ideally set automatically from the telephony error code. Wrong number means the line works but the wrong person answered. Collapsing them loses the signal that tells you which list supplier sold you junk.
- Answered vs connected vs voicemail. If these collapse into one “contacted” state, your connect rate is not measuring anything.
5. Scripts you can A/B test
A script library is table stakes. Check whether you can run variants, assign reps to a variant, and report per variant. Without that, “we improved the opener” is an anecdote.
6. Call cost per client
Telephony is usage-priced and arrives as one monthly bill. Ask whether call spend can be attributed per account or per client, so you can put call cost next to the meetings it produced — and see which client relationship is actually profitable.
What to ignore
- Dial-throughput claims in isolation. More dials into a list that books badly produces more bad meetings. Throughput fixes too few conversations, nothing else.
- AI feature lists without a stated accuracy or language scope.
- Integration counts. Fifty shallow integrations are worse than the one deep integration you need.
Most dialers cannot tell you what a call was worth
A dialer records the call and asks for a disposition. Separately, somebody works out which meetings held, what each rep earned and what each client gets invoiced. If your calling tool ends at the disposition, you still own that reconciliation — usually the more expensive problem.
Calling tool ends at the disposition
- Call logged with a disposition, then nothing
- Held meetings checked by hand against the calendar
- Commission worked out in a spreadsheet
- Client invoice built from a separate meeting list
Calling tool feeds the rest of the month
- Call produces a booking on the same lead
- Booking gets an outcome: held, no-show, cancelled
- Outcome creates exactly one commission row
- Same outcome decides whether the client is billed
Where Dialbrew fits
It has the calling stack described above: VoIP numbers assigned per rep, cross-channel inbound routing, consent-captured recording with transcription and enforced retention, eight structured call outcomes, scripts with A/B tests, and per-account cost sync.
It is not a business phone system — no IVR, no queues, no predictive or power dialing. If raw dial throughput or company telephony is your constraint, buy a dedicated product; we would rather say that than sell you the wrong thing.
Further reading
- Sales dialer — the calling module in detail
- Cloud phone system — where the line sits versus a real phone system
- Kixie alternative · Aircall alternative — if you are evaluating one
- EU outbound and GDPR — the compliance obligations in detail
- The SDR tool stack — where calling fits among the other layers