Calling for SDR teams — a cloud phone built into the operation

What this gets you

• VoIP numbers held at account level and assigned to individual reps
• Inbound routing to whoever actually owns the conversation, across channels
• Recording and transcription attached to the lead, not a separate archive
• Call scripts per client project, with A/B tests and per-variant reporting
• Call outcomes that drive commission, not just a disposition dropdown
• Per-account telephony cost sync, so call spend sits beside the output it produced

Let us be clear about the category first

Dialbrew is not a business phone system, and if that is what you need you should buy one.

There is no IVR, no call queues, no org-wide telephony, no predictive or power dialing engine, and no contact-centre routing. Aircall, RingCentral, Dialpad and Ringover are all good at those things and Dialbrew does not try to compete with them.

What it has is calling built into the record that matters:

A phone system gives you the call. It does not give you the commission on the meeting the call produced.

That is the entire argument for having calling here rather than beside.

What the calling stack actually is

VoIP numbers are held at account level and assigned to individual reps, one number to one rep. Outbound calls use the rep’s assigned number as caller ID.

Inbound routing resolves who owns the conversation before it rings. The precedence is: whoever has the lead reserved; otherwise whoever made the most recent outbound touch to that prospect across both calling and SMS; otherwise the project roster. That cross-channel step matters — a prior outbound SMS makes that rep the owner of an inbound call, and vice versa. If the owner does not pick up, the call falls through to a wider set rather than being dropped.

Recording and transcription attach to the lead’s timeline, not to a separate audio archive you have to go searching in. Recording runs in two modes: the rep’s own side automatically, and a dual-channel recording when the rep presses consent. Transcription is Finnish-capable.

Both are gated by an account-level master switch that is a hard gate — off at the account means off everywhere, regardless of per-client settings. Per-customer and per-project settings can only narrow it further, never enable past an off account. Recordings carry their own retention clock, shorter than ordinary activity data, with automated archival and deletion.

Call scripts live per client project, with A/B tests that report per variant and flag the leader. The calls workspace shows a rep only their assigned variant.

SMS sends from reusable presets, with a shared threaded inbox that remembers the channel last used — so an SMS conversation stays an SMS conversation.

Cost sync pulls per-account telephony spend on a schedule, so call cost sits next to the meetings it produced rather than arriving as one unattributable monthly bill.

The part that only works because it is in one system

Every call writes to a unified activity log on the lead, discriminated by channel, alongside SMS, email and notes. The feed streams live, so a manager watching a client’s list sees work land rather than reading about it tomorrow.

Then the chain continues. A call that produces a booking creates a booking record. That booking gets an outcome — held, no-show, or no-show-with-reschedule. That outcome generates exactly one commission row and determines whether the meeting is billable to the client.

A standalone dialer cannot do that, because it does not know what a client product costs or what a rep earns. That is not a criticism of dialers; it is a different scope.

Missed calls, handled properly

An unanswered inbound call is recorded as missed, attributed to the rep who should have taken it, and surfaced as a per-rep indicator on the lead. It clears when that rep dismisses it — not merely when someone opens the lead. Small detail, but the alternative is a notification system nobody trusts.

Compliance

Call recording obligations differ by country — some jurisdictions require all parties to consent rather than one — so a multi-country operation cannot assume a single policy covers it. Dialbrew supports recording with consent capture and retention controls; the lawful basis and notification practice for your markets is yours to set, and worth taking advice on.

Recordings and transcripts are treated as high-sensitivity personal data: tighter access, a shorter retention clock than ordinary activity data, and automated cleanup.

If you need a real phone system too

Keep it. Most teams will. Dialbrew handles the outbound sales calling that has to be tied to outcomes and money; a business phone system handles company telephony. They are not mutually exclusive, and we would rather tell you that than pretend otherwise.