Lead management system and software for SDR agencies
A lead management system built for agencies: lists per client, expiring lead reservation, phone normalisation, per-client DNC and depletion alerts.
E.164
phones normalised
per client
DNC filtered
1 SDR
per reserved lead
What this gets you
Prospect lists scoped to the client project they belong to
Expiring lead reservation — two reps can never work the same company
Phone numbers normalised to E.164 at import, so deduplication actually works
Per-client DNC filtered at import, before any rep sees the row
Phone quality tracked as data, so bad numbers are measurable per supplier
Depletion alerts before a rep spends a week working an empty list
Agencies work several clients’ lists at once
Most lead management software assumes one company and one pool of leads. An agency works several clients’ lists with a shared roster, different suppression rules per client, and no room for work landing on the wrong client.
So prospect lists belong to a client project, as do products, pricing, the DNC list, reporting and the SDR roster. Per-client scoping is part of the data model, not a filter to remember.
Two SDRs calling the same company
On a shared list this is a certainty unless something prevents it. Opening a lead reserves it to that SDR with an expiry. Working it extends the hold, a final outcome releases it, and a background job clears stale holds. An expiring hold keeps the list moving, where a permanent assignment would leave leads parked against someone who never comes back.
Lists that run dry without anyone noticing
Nothing errors when a list is used up: activity just drifts down. Dialbrew tracks the share of each project’s leads already called and opens a task for the account manager when it crosses the account’s threshold.
Clean data at import
What happens to a CSV on import
- 1
Normalise phones
040 123 4567, +358 40 123 4567 and 358401234567 all become +358401234567. Default country comes from the account.
- 2
Remove duplicates
Match on phone, email, LinkedIn URL or name plus company, alone or combined. Phone matching works because numbers are normalised first.
- 3
Filter client DNC
Suppressed before any SDR sees the lead, and it survives re-importing the source.
- 4
Report per row
Every failed row is listed, so one systematic formatting issue is fixable in seconds.
Phone quality as data
Each lead gets a phone-quality status, recomputed daily as call outcomes accumulate. Reporting shows the share of bad numbers per list, so you can stop SDRs burning hours on dead lists and see which data supplier is worth paying for.
| Status | Set when |
|---|---|
| Disconnected | A call returns BAD_NUMBER, set automatically from the telephony response |
| Wrong number | The SDR logs WRONG_NUMBER: the line works, the wrong person answered |
| Never answers | Five or more unanswered calls in 60 days and no answered call ever |
| OK | None of the above |
What a lead carries
Status, a two-part fit rating (right company, right person), a structured lost reason, enrichment signals, a timeline across call, SMS, email and note, and a history of every status change with who made it.
What Dialbrew does not do
It does not source leads or hold a contact database. Bring your own data and Dialbrew cleans, scopes, protects and tracks it. It is not a nurture tool either: no drip campaigns or lead scoring over months.