Features

The whole surface, end to end

Grouped by the part of the operation it serves. If you are looking for a sequencer, a contact database or a CRM, they are deliberately absent — Dialbrew integrates those rather than replacing them.

Leads & prospect lists

Supply the team without collisions, dead numbers or silent depletion.

Prospect lists per client project

Named lists scoped to the client they belong to, so reporting and suppression are per-client by construction.

Lead reservation

An expiring soft lock pins a lead to the SDR working it; a background job releases stale holds so the list keeps circulating.

Import hygiene

Phone numbers normalise to E.164, duplicates collapse on a stable key, and rows missing required fields are reported per row.

Per-client DNC

Suppression enforced at import, before a record reaches a rep — and it survives re-importing the original source.

Phone quality as data

A status recomputed as call outcomes accumulate, plus the origin of each number, so supplier quality is measurable.

Depletion alerting

A warning when a list runs dry, because nothing errors when a rep works an empty list.

Lead rating & lost reasons

Star ratings and structured lost-reason capture, rolled up for analysis.

Companies & contacts

Account-scoped prospect organisations and the people at them.

Activity & calling

One timeline per lead, whatever channel the work happened on.

Unified activity log

Call, SMS, email and note all write to one per-lead timeline, discriminated by channel.

VoIP calling

Twilio numbers held at account level and assigned to users, with cost sync per account.

Recording & transcription

Calls optionally recorded and transcribed, with archival and cleanup on a retention schedule.

Call scripts & A/B tests

Scripts per project, plus script tests that show a per-variant breakdown.

SMS with presets

Reusable message templates so the version written when someone was sharp is the one that gets sent at 3pm.

Shared inbox

Threaded replies that remember the channel last used, so an SMS conversation stays an SMS conversation.

Live activity stream

The timeline streams over SSE, so a manager watching a list sees work as it lands.

Bookings & outcomes

A booking is a unit of output with a recorded fate, not a promise.

Three honest outcomes

Held, no-show, and no-show-with-reschedule as distinct recorded states.

Calendar sync

Two-way with Google Calendar and Outlook, so the invite exists before the rep hangs up.

CRM push

Booked meetings pushed into the client’s own HubSpot or Pipedrive — each client connects their own.

Reschedule in place

A rescheduled meeting stays the same unit of work with a new date and its original attribution.

Cancellation flow

Request and approval, resolved by a stored compensation matrix rather than a monthly negotiation.

Appointment reminders

Automated, so reminder compliance does not depend on how busy the team is.

Slack notifications

Per-channel booking and no-show notifications, event-driven.

Commission & billing

One source of truth for what gets paid and what gets charged.

Products per client

Each product carries a customer price and an SDR commission, so one booking prices twice from one row.

One commission row per booking

Enforced by a unique database constraint, so a retried job or redelivered message cannot double-pay.

Approve → pay lifecycle

With reversion, so "has this been paid" is a stored state rather than a recollection.

Compensation matrix

Cancellations and no-shows resolved identically every month, for both rep and client.

Billing records

A lifecycle from creating → ready → invoiced → sent/paid, with the price frozen so sent invoices stay reproducible.

Procountor invoicing

Records pushed out and polled for status, so invoice state sits beside the work that produced it.

Work owed & EUR efficiency

Compensation tracking and money-per-hour reporting per rep and per project.

Workforce & capacity

Forecasts built on real rates and real available hours.

Allocation rates

Bayesian bookings-per-hour per SDR per project, so small samples stay appropriately conservative.

Manager overrides

A separate visible layer on top of the computed rate, never a silent edit to it.

Holiday-correct working days

Any count of working, billable or expected days subtracts public holidays for the account’s country.

Absences

Vacation, sick leave and personal time as recorded objects that reduce available hours.

Work hours & overrides

Per-account hours with per-user overrides, so part-time is modelled as part-time.

Work-time variance

Expected hours against logged hours, so drift surfaces while you can still act on it.

Teams & rosters

Teams per account, plus a named SDR roster per project held separately from the account manager.

Reporting & the client view

The client reads the same rows you do.

Pre-aggregated rollups

Performance rollups per SDR and per SDR-per-project, so a live portal is viable instead of slow.

Customer portal

Clients log in to their own meetings, reports, billing and DNC — with their own admin and member roles.

Scheduled client reports

Delivered automatically on a configured cadence by a background sweep.

Internal dashboards

Reporting views, an order book, and a manager task queue.

Global search

Across entities, scoped by tenancy and permission.

API keys

Programmatic access for whatever we have not thought of.

Access, security & platform

Scope by permission, hosted in the EU, built to survive a restart.

Six roles

Admin, SDR manager, SDR, account manager, and client admin/member.

Permission templates

Named bundles that set data scope independently of job title.

Permission-driven scope

All-vs-rostered visibility keys off explicit permissions, not role, so a contractor is a configuration.

Employment type

Recorded as the HR fact it is, used to pick a sensible default at invite time.

EU hosting

AWS eu-central-1, analytics on EU cloud with anonymous profiling disabled.

Durable events

A transactional outbox means a crash between commit and publish cannot lose an event.

Idempotent consumers

Processed-message tracking, so a redelivery cannot double-handle.

Impersonation

Admin support access, for when a client says "it does not work on my screen".

Book a walkthrough

Put every client on one floor

A walkthrough on your own roster, clients and commission model — from an imported list to a sent invoice. Judged on your operation, not a demo dataset.

Book a demo See how it works

EU-hosted · eu-central-1 · integrates the CRM, calendar and telephony you already run