Preview dialer
Shows the record, history, and objective before the call. Recommended when preparation influences quality and conversion.
Dialing modes solve different problems. Comparing only speed hides what really matters: agent preparation, team capacity, abandonment risk, list volume, and the value of each contact.
The main types are preview, progressive, and predictive. In preview, the agent reviews the contact before calling. In progressive, the system dials when an agent is available. In predictive, algorithms calculate how many calls to start before agents become available. Operations can also keep assisted manual dialing for exceptions.
A portfolio of major accounts should not follow the same pace as a mass campaign. The right mode comes from the intersection of contact value, list size, number of agents, completion rate, and tolerance for waiting.
Shows the record, history, and objective before the call. Recommended when preparation influences quality and conversion.
Starts one call for each available agent. Favors predictability and reduces excess calls.
Calculates the pace using campaign and team statistics. Seeks scale but requires calibration and monitoring.
Keeps the decision with the agent, using click-to-call, CRM record, and automatic logging to reduce steps.
Different portfolios can use different modes based on value, urgency, consent, and availability.
Time, frequency, list, capacity, and abandonment handling must accompany any chosen mode.
| Mode | When the call starts | Priority | Best use |
|---|---|---|---|
| Preview | After the agent reviews the record | Contexto | Consultative sales and high-value accounts |
| Progressive | When an agent is available | Predictability | Collections, relationship, and medium-sized lists |
| Predictive | Before availability, based on calculation | Escala | Large campaigns and monitored teams |
| Assisted manual | When the agent decides | Control | Exceptions, callbacks, and sensitive contacts |
The mode should be born from the operation's requirements, not from the most popular name in the market.
The higher the value and complexity, the more context tends to be needed.
Consider the size and quality of the base, not just the number of rows in the spreadsheet.
Predictive scaling needs sufficient capacity and behavior for calculation.
Set limits for wait, abandonment, frequency, and experience before speeding up.
The right mode balances preparation, capacity, scale, and experience according to each portfolio.
The operation stops treating speed as the only success criterion.
The pace considers agents, duration, and post-call work.
Limits and exceptions are included in the configuration before increasing volume.
Tests and indicators replace preferences for a specific mode.
The main ones are preview, progressive, and predictive. There is also assisted manual dialing, with click-to-call and CRM logging, useful for exceptions and sensitive contacts.
Progressive starts the call when an agent is already available. Predictive anticipates calls using availability and completion calculations, seeking more scale and requiring abandonment control.
When the agent needs to review history, contract, opportunity, or context before speaking. It is common in consultative sales, key accounts, and sensitive negotiations.
No. It can increase the pace in suitable operations, but a poor base, small team, or inadequate calibration can cause wait time, abandonment, and a worse experience.
Yes. An operation can use preview for strategic accounts, progressive for regular portfolios, and predictive for high-volume campaigns.
Test equivalent segments and track useful contacts, talk time, conversion, abandonment, cost per result, and quality. Don't compare just the total number of attempts.
OmniSmart helps map base, team, context, and indicators to define a testable dialing strategy.
Tell us the basics about your scenario.