Power Dialer works a queue of prospects who have a phone number on file, one call after another, with a rep on the line. Before any number is dialled, the system checks the do-not-call list, the prospect’s local calling window, and the market’s recording rules. Reps still make the calls that matter. The dialer manages the queue, checks call eligibility, and automatically selects an outgoing caller number.
This sales power dialer supports human-led calls; it is not autonomous AI voice calling for sales, and the browser dialer does not record calls or produce transcripts.
Trusted by 10,000+ users across all sizes and industries
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
Power Dialer lives on its own Dialer page: a dial pad, a queue list, a queue detail table showing every prospect waiting and why, session settings for hours and pace, and a numbers panel tracking the lines available to call from.
A workspace has to have Power Dialer enabled for any of this to appear. Where it is not, no dial pad, queue or numbers panel shows up.
A call list starts in the list builder, opened from the dialer lobby. Filters include a minimum engagement score, market, and a recent buying signal. A live preview shows the match count and why others were left out: no phone, on the do-not-call list, below score, wrong market, or no signal.
Call queues use workspace contacts with a phone number on file, but each call must pass the relevant suppression and calling-window checks before it is placed. Lists can also be built by ticking rows in a people table, generated by a playbook, or fed by a campaign’s manual call step. Each entry includes a pre-call brief with the latest positive signal, up to the last five interactions across channels, and a suggested opening line. Undialable contacts may remain visible in the lobby with a status chip; final server preflight runs at dial time.
Every dial in the queue runs through the same compliance preflight, checked again by the server at the exact moment of dialing.
| Check | What it looks at | What happens if it fails |
|---|---|---|
| Do-not-call | Workspace do-not-call and suppression lists | Contact is refused or removed from the queue |
| Calling window | The prospect's local time against a fixed 9am to 6pm weekday window | Call is held, with the reason shown in the queue |
| Recording rule | The market's rule on whether the call may be recorded | Applied automatically before the call connects |
The system also decides which number rings, on its own: the rep's own number first, then one local to the prospect's area, then the healthiest number in the shared pool. A number whose answer rate collapses is quarantined and pulled from rotation automatically, reason recorded, so a call goes out from a number likely to be answered.
A contact that fails a check does not vanish quietly. The queue detail table shows exactly why a call did not go out, so a rep working the list sees a reason rather than a gap.
A one-off call can be placed from almost anywhere: press d, open the dial pad from the dialer page, or use the row-level dial action inside a call list. It opens a slide-over panel with a search box or a keypad, shows local time, calling-window status, do-not-call status and the recording rule up front, and connects through the browser once dialled.
A full session works a whole list instead of one person. The rep starts the session and a card deck advances through the list, each card showing the contact's context and a suggested opening line before the call goes out. Power mode starts the next dial a few seconds after each disposition is logged, so a rep can keep working without reaching for a mouse.
Both paths run on the same engine: the same preflight, suppression checks, number rotation and browser audio. The system never lets two calls reach the same person at once.
Placed from the dial pad, for a single contact, from anywhere in the app.
Works a whole list at once, with power mode auto-starting the next dial after each disposition.
Both paths run the same compliance preflight and the same automatic number rotation.
After a call, the representative can use a keyboard shortcut to select an outcome. Confirming the outcome saves it to the Salesflow call record and updates the session counters. Call history remains available on the prospect timeline; these updates do not write back to an external CRM.
The prospect-timeline statement is also documented.
| Disposition | What it signals |
|---|---|
| Meeting booked | A next step is on the calendar |
| Callback requested | The contact wants a call at a later time |
| Interested | Positive signal, no meeting booked yet |
| Not interested | The contact has declined |
| Send info | The contact wants material by email before a further conversation |
| Do not call | The contact has asked not to be called again; the rep must also add the number to suppression |
Selecting “Do not call” during session wrap-up records the call outcome; it does not automatically add the number to suppression. The representative must also use the contact panel’s do-not-contact action to update the suppression registry. Before each call, the dialer checks the relevant suppression and do-not-call records and blocks the call when those checks fail.
A next step goes on the calendar.
The contact wants a call at a later time.
Positive signal, no meeting booked yet.
The contact has declined.
Material by email before a further conversation.
Do-not-call and suppression lists are checked before every dial, so a number already on them cannot re-enter any queue, even a brand new one.
A rep working a full queue does not want to reach for a mouse between calls. Enter starts a dial or confirms an action such as a disposition. Keys 1 to 6 pick a disposition. Space pauses or resumes power mode's auto-dial. M mutes the call. Escape ends the session.
Power mode is what turns a queue from tidy into fast. Once switched on, the next dial starts a few seconds after a disposition is logged, and the countdown can be cancelled with one keypress. The result is a session a rep can run largely without leaving the keyboard, which matters when a queue runs to dozens of contacts in one sitting.
A call is one channel among three, and it earns a place in the sequence rather than opening it. A campaign's call step is a manual task: it feeds the contact into a call list inside Power Dialer, ready for a rep to work by hand, not a call placed on its own. Email starts the relationship because it carries the most context per touch. LinkedIn adds a face a few days later. By the time a call step fires, the contact has already seen the name twice.
Placing a call step too early wastes the channel. A prospect who has not seen your name is more likely to treat an unknown number as a nuisance.
An example sequence is two email touches, one LinkedIn touch, and a manual call task, with Wait steps between them. A reply can stop subsequent campaign steps according to the configured reply policy. A reply can stop subsequent campaign steps according to the configured reply policy.
Unlike AI voice calling for sales, this workflow leaves the conversation to a representative while keeping the call task and prior outreach context in the same sales process.
It is not a way around do-not-call obligations. The checks enforce rules your workspace has set, not a permission the law does not grant. Legal responsibility for who gets called stays with the sender, not the software.
It does not guarantee a call gets answered, and it will not dial around a flagged number just because a queue needs clearing. Volume without care produces unanswered rings and very little pipeline.
It is not a replacement for a rep's judgment on the call. A queue, a preflight check and a suggested opening line get the right person on the line. What gets said once they answer is still on the rep.
run before every single dial, none of them skippable
logged after a call, written back to the contact as activity
the pace power mode is built to reach for a rep working a queue
No implementation project. Turn it on, build the first queue, work the dial pad.
The Dialer page, dial pad, queue and numbers panel appear for the workspace.
Engagement score, market and recent signal decide who qualifies, phone holders only.
Enter to dial or confirm, space for power mode, escape to end the session.
Power Dialer is a shipped feature with its own Dialer page, dial pad, queue and session settings. It is not a placeholder name.
Only prospects with a phone number who are not on the do-not-call list are eligible. Lists can be built from filters such as engagement score and recent buying signal, by ticking rows in a people table, or fed by a campaign's manual call step.
Three things: do-not-call and suppression status, the prospect's local calling window, and the market's recording rule. Any failed check holds or refuses the call, with the reason shown in the queue.
A one-off call is placed from the dial pad, for a single contact, from anywhere in the app. A full session works an entire list, and power mode auto-starts the next dial once a disposition is logged. Both run the same compliance checks and number rotation.
The rep logs a disposition from six options: Meeting booked, Callback requested, Interested, Not interested, Send info, or Do not call. The disposition writes back to the contact as activity.
It records the outcome on that call. Suppression itself comes from the workspace's do-not-call and suppression lists, checked before every dial, and logging Do not call in wrap-up does not yet add the number there by itself.
Later, not first. A typical sequence runs two email touches and one LinkedIn touch before a call, so the contact has already seen the name before the phone rings.
Book a 30 minute demo and watch Ariel find buyers, write the outreach and line up meetings, with you approving every move.
Book a Demo See Ariel