@vicistack/predictive-vs-progressive-dialing
v1.0.0
Published
Which Dial Mode Is Bleeding Your Campaign Dry? — ViciStack call center engineering guide
Maintainers
Readme
Which Dial Mode Is Bleeding Your Campaign Dry?
The dialing mode you choose for a campaign is the single most impactful configuration decision in outbound calling. It determines how many contacts your agents make per hour, how much idle time they endure between calls, how many leads you burn through per shift, and whether your operation stays on the right side of FCC and TCPA regulations. Get it wrong and you either leave money on the table (too conservative) or catch a compliance violation that costs more than a month of revenue (too aggressive). Despite this, most call center operators either stick with whatever their dialer defaulted to, or switch to "predictive" because someone told them it was faster — without understanding the trade-offs, the agent count thresholds, or the compliance implications. This guide covers the three primary dialing modes in depth: predictive, progressive, and preview. For each mode, we explain how it works technically, how VICIdial implements it, when to use it, and what performance to expect. We also cover hybrid approaches, VICIdial-specific configurations, compliance considerations, and a decision framework you can apply to any campaign. --- ## How Each Dialing Mode Works ### Predictive Dialing: The Algorithm Predictive dialing is exactly what the name implies — the dialer predicts when agents will become available and places calls in advance so a live call is waiting when the agent finishes their current one. The algorithm continuously calculates the optimal number of lines to dial per available agent (the "dial ratio") based on several real-time inputs: - Agent availability: How many agents are currently available or about to become available - Average talk time: How long agents typically spend on connected calls - Average wrap time: How long agents spend in after-call work - Answer rate: What percentage of dialed calls actually get answered - Current abandon rate: What percentage of answered calls are dropped because no agent was available Here's the simplified logic: If the algorithm knows 5 agents will be available in 30 seconds (based on their average talk time), and the historical answer rate is 25%, and dial-to-connect takes an average of 15 seconds, it needs to place approximately 20 calls right now so that 5 of them answer just as the agents become free. In VICIdial, this algorithm runs as a Perl script called AST_VDadapt.pl. It recalculates every 15 seconds — examining the current state of all agents, all active calls, recent abandon rates, and campaign performance metrics — and adjusts the dial level up or down accordingly. The fundamental trade-off: Predictive dialing maximizes agent talk time but creates a non-zero probability that a call will be answered with no agent available. This "abandoned" call is a compliance risk under FCC regulations, which mandate a maximum 3% abandon rate measured across a rolling 30-day period. ### Progressive Dialing: One Call, One Agent Progressive dialing places exactly one call per available agent. When an agent becomes available, the dialer places one call for that agent. If the call is answered, the agent handles it. If it's not answered (busy, no answer, voicemail), the dialer immediately places another call for that agent. There's no prediction involved. No algorithm calculating future agent availability. No risk of answered calls with nobody to handle them. The mechanical simplicity is the point. Progressive dialing guarantees: - Zero abandoned calls (every answered call has an agent waiting) - Every agent gets connected to every answered call (no algorithmic drops) - Compliance with all outbound calling regulations by design The trade-off is lower throughput. Agents spend more time waiting between calls because the dialer isn't proactively filling the pipeline. Instead of hearing a connected call within 1-2 seconds of finishing the previous one (predictive), agents wait 10-20 seconds while the dialer places a call, waits for it to ring, determines it won't be answered, and tries the next number. ### Preview Dialing: Agent-Initiated Calls Preview dialing shows the agent a lead's information before the call is placed. The agent reviews the data — name, company, notes from previous calls, account status — and then manually initiates the call when ready. Some implementations include a countdown timer that auto-dials if the agent doesn't act within a set period. This isn't dialing at all in the traditional sense. The agent is in control. They decide when to call, can skip leads they're not prepared for, and can research the contact before initiating conversation. The productivity hit is significant: agents spend 30-120 seconds reviewing each lead before calling, plus the ring/answer time, plus the actual conversation. But for complex sales cycles, high-value accounts, or situations requiring pre-call research, that preparation time pays for itself in conversion rate. --- ## VICIdial's Implementation of Each Mode VICIdial doesn't use the terms "predictive," "progressive," and "preview" in quite the way the industry does. Understanding the mapping between industry terminology and VICIdial's actual settings is crucial for configuring the right behavior. ### Dial Method Settings in VICIdial The primary control is Campaign Detail → Dial Method. Here's how VICIdial's options map to industry-standard dialing modes: | VICIdial Dial Method | Industry Equivalent | How It Works | |---------------------|---------------------|-------------| | RATIO | Fixed-ratio dialing | Dials at a fixed ratio you set (e.g., 3 lines per agent). Not truly predictive — doesn't adapt to conditions. | | ADAPT_AVERAGE | Progressive / Adaptive | Adjusts dial ratio based on campaign stats, targets average performance. Conservative. | | ADAPT_TAPERED | Adaptive progressive | Similar to ADAPT_AVERAGE but tapers off more aggressively when approaching drop limits. Most conservative adaptive mode. | | ADAPT_HARD_LIMIT | Predictive with safety net | Adapts aggressively but enforces a hard drop rate ceiling. | | INBOUND_MAN | Preview / Manual | Agents see lead data and initiate calls manually. | | MANUAL | Manual dialing | No auto-dialing at all. Agent manually enters numbers. | ### True Predictive Dialing in VICIdial: RATIO + Tuning Here's the industry secret that vendor marketing departments don't tell you: VICIdial's RATIO mode with a skilled administrator is functionally predictive dialing. Set the auto dial level to 3.0-5.0, enable available only ratio tally = Y, and configure the dial timeout appropriately — and you have a predictive dialer that's manually tuned rather than algorithmically adaptive. The difference between RATIO at 4.0 and a commercial "predictive dialer" like Convoso's is that RATIO holds steady at 4:1 regardless of conditions, while a predictive algorithm adjusts that ratio second by second. In practice, an experienced administrator monitoring the campaign can adjust RATIO periodically and achieve similar results — it's just not hands-free. ### Adaptive (Progressive-Like) Dialing: ADAPT Modes The three ADAPT modes are where VICIdial implements genuine algorithmic dialing — and they're closer to progressive than predictive in most configurations. ADAPT_AVERAGE: - Calculates dial ratio based on average campaign metrics - Adjusts every 15 seconds via AST_VDadapt.pl - Default behavior keeps the dial ratio relatively conservative - Won't exceed the Adaptive Maximum Dial Level you set ADAPT_TAPERED: - Same as ADAPT_AVERAGE but reduces dial ratio more aggressively as the campaign's drop rate approaches the ceiling - This is the safest auto-dial mode for compliance-sensitive campaigns - Typically produces 30-40 minutes of talk time per agent per hour ADAPT_HARD_LIMIT: - Adapts aggressively toward the maximum dial level - Enforces a hard ceiling on drop rate — if drops exceed the target, the algorithm immediately reduces the dial level - Most aggressive adaptive mode — closest to true predictive behavior ### Critical VICIdial Settings for Each Mode For Predictive (RATIO) Campaigns: | Setting | Value | Purpose | |---------|-------|---------| | Auto Dial Level | 3.0-5.0 | Lines per available agent | | Available Only Ratio Tally | Y | Only count truly available agents in ratio calculation | | Dial Timeout | 18-22 seconds | How long to ring before giving up | | Drop Rate Group | CAMPAIGN_ONLY | Monitor drops per-campaign | | Hopper Level | 200-500 | Leads pre-loaded for immediate dialing | | AMD Type | CPD or AMD | Answering machine detection mode | For Progressive (ADAPT) Campaigns: | Setting | Value | Purpose | |---------|-------|---------| | Dial Method | ADAPT_TAPERED | Progressive-like behavior | | Adaptive DL Level | 1.5-2.5 | Maximum ratio the algorithm can reach | | Abandon Rate Target | 1-2% | Conservative drop target | | Drop Lockout Time | 1 day | How long a dropped lead is locked from redialing | | Auto Dial Level | 1.0 | Starting dial ratio (algorithm adapts up) | For Preview (MANUAL/INBOUND_MAN) Campaigns: | Setting | Value | Purpose | |---------|-------|---------| | Dial Method | INBOUND_MAN | Shows lead data, agent initiates call | | Manual Dial | Y | Agent has dial button | | Lead Order | UP_LAST_NAME_ASC or MANUAL | How leads are presented to agents | > Not Sure Which Mode Your Campaign Needs? > ViciStack configures every campaign for the optimal dial method based on your agent count, vertical, and compliance requirements. Get Your Free Campaign Assessment → --- ## When to Use Each Mode: The Decision Framework ### Predictive Dialing: Maximum Throughput Use predictive when: - You have 15+ agents on a single campaign. Below 15, the algorithm doesn't have enough statistical data to predict accurately, and the dial ratio becomes erratic. - Your campaign is high-volume, low-complexity — consumer outbound, appointment setting, surveys, debt collection reminders. - Your operation can tolerate a 1-3% abandon rate (within FCC limits). - Lead lists are large enough that burning through contacts quickly is acceptable. - Revenue per contact is moderate — you make money on volume, not individual deal size. - Your compliance team and TCPA exposure are managed. Don't use predictive when: - You have fewer than 10 agents per campaign - You're calling cell phones in a TCPA-sensitive context (prior express consent not clearly documented) - Your leads are high-value and limited — predictive's speed burns through lists fast - You're in a heavily regulated vertical where any abandoned call creates liability Performance benchmarks (predictive): - Agent talk time: 45-55 minutes per hour at 25+ agents - Agent talk time: 38-45 minutes per hour at 15-25 agents - Contacts per hour: 8-15 (depending on answer rate and talk time) - List burn rate: 200-400 dials per agent per 8-hour shift ### Progressive Dialing: The Compliance Default Use progressive when: - You have fewer than 15 agents per campaign. Progressive works well at any scale — even 3 agents. - B2B campaigns where contact rates are lower and each contact is more valuable. - Compliance is a primary concern — TCPA-sensitive campaigns, cell phone lists without clear consent documentation, financial services under CFPB oversight. - High-value leads where you want agents to handle every answered call — no algorithmic drops. - You need to preserve lead quality by not over-dialing your list. - The campaign is in a state with strict calling regulations (California, Florida, etc.) Performance benchmarks (progressive): - Agent talk time: 30-40 minutes per hour - Contacts per hour: 5-10 - List burn rate: 100-200 dials per agent per 8-hour shift - Abandon rate: 0% (inherently compliant) ### Preview Dialing: Quality Over Quantity Use preview when: - Each call requires pre-call research — reviewing account history, looking up previous notes, checking external data sources. - Complex B2B sales where the agent needs to understand the prospect's business before calling. - High-value accounts where a poorly prepared call damages the relationship (enterprise sales, wealth management, executive-level outreach). - Callback campaigns where the agent needs context from the previous interaction. - Collections where the agent needs to review the account balance, payment history, and applicable regulations before initiating contact. - Your agents are highly skilled and expensive — paying them to research is worth it because their conversion rate on prepared calls justifies the lower throughput. Performance benchmarks (preview): - Agent talk time: 15-25 minutes per hour - Contacts per hour: 3-6 - List burn rate: 30-80 dials per agent per 8-hour shift - Conversion rate: 1.5-3x higher than predictive on the same leads
About
Built by ViciStack — enterprise VoIP and call center infrastructure.
- VICIdial Hosting & Optimization
- Call Center Performance Guides
- Full Article: Which Dial Mode Is Bleeding Your Campaign Dry?
License
MIT
