Sales dialer with outcomes wired to commission
Click-to-call over VoIP with recording, transcription and scripts — where the call outcome drives the booking, the commission and the client invoice instead of ending in a disposition dropdown.
What this gets you
- Click-to-call from the lead card, using the rep’s own assigned number
- Recording and transcription attached to the lead timeline
- Scripts per client project, with A/B tests and per-variant reporting
- Eight call outcomes, including bad-number vs wrong-number as distinct facts
- Call outcome feeds the booking, the commission and the invoice
What a dialer usually ends at
A dialer places the call, records it, and asks the rep to pick a disposition from a dropdown. The disposition lands in a report. Then, separately, somebody works out what the meetings were worth.
The gap between those two things is where most SDR operations lose a day a month.
What happens here instead
Calling is click-to-call from the lead card, using the rep’s own assigned VoIP number as caller ID. There is no separate dialer app, because the call is an event on the lead rather than a session in another tool.
Call outcomes are eight states, not a free-text note: answered, no answer, busy, failed,
voicemail, callback, bad number, wrong number. Two of those deserve the distinction they get —
BAD_NUMBER (not in service, set automatically from the SIP response or telephony error code) and
WRONG_NUMBER (the number works but the wrong person answered, set by the rep). Collapsing them
loses a real data-quality signal about your list supplier.
Recording runs in two modes: the rep’s own side automatically, and a dual-channel recording when the rep presses consent — with the consent timestamp stored even if the recording itself fails, as a pure audit trail. Transcription is Finnish-capable.
Scripts live per client project with A/B tests. The calls workspace shows a rep only their assigned variant, and reporting breaks results down per variant with the leader flagged. That is a genuine experiment rather than a shared doc nobody opens.
Reservation happens automatically: placing a call reserves the lead to that rep with an expiry, so a colleague cannot dial the same company minutes later. Logging an outcome extends it. A terminal outcome releases it.
Then the chain continues
This is the part a standalone dialer structurally cannot do.
A call that produces a meeting creates a booking. The booking syncs to Google or Outlook, pushes into the client’s own HubSpot or Pipedrive, and posts to Slack. Later it gets an outcome — held, no-show, or no-show-with-reschedule.
That outcome generates exactly one commission row for the rep, enforced by a unique database constraint, and decides whether the meeting is billable to the client. Both figures derive from the same booking.
A dialer cannot do this because it does not know what a client’s product costs or what a rep earns. That is not a failing of dialers — it is a different scope. But it does mean that if you buy a dialer, you still own the reconciliation problem.
What this is not
No predictive dialing. No power dialing. No parallel dialing across multiple lines. No IVR or queues.
If raw dial throughput is your constraint, a dedicated predictive dialer will beat this and you should buy one — the honest comparison is that Dialbrew optimises what happens to the call, not how many calls per hour.
Alongside what you already run
Keep your phone system if you have one. Dialbrew handles the outbound sales calling that needs to be tied to outcomes and money; business telephony is a separate purchase. See the cloud phone system page for where that line sits, or the Kixie and Aircall comparisons if you are evaluating one of those.