Hosted Call Centre Guide
Choose a dialling approach that fits campaign workflow, agent readiness and responsible oversight.
Answer first
Predictive dialling uses campaign pacing to place call attempts ahead of expected agent availability, while progressive dialling places the next attempt in a more controlled sequence around agent readiness. Progressive is often the first discussion when controlled pacing matters; predictive needs active monitoring at suitable campaign scale. SureTel assesses the campaign, team, connectivity and operating requirements before recommending a suitable hosted-dialler path.
Compared
The meaningful difference is how closely call timing is tied to agent readiness. Neither model is automatically right for every campaign. The operating context, team capacity, contact practices, management ownership and monitoring discipline all matter. Use this table to frame a requirements discussion rather than treat it as a configuration instruction.
Decision point
Call timing
Predictive dialling
Campaign pacing can place attempts ahead of expected agent availability.
Progressive dialling
The next attempt is placed in a more controlled sequence around agent readiness.
Decision point
Primary operating conversation
Predictive dialling
How a suitably managed, higher-volume campaign will be monitored and adjusted.
Progressive dialling
How the team will keep hand-offs deliberate and visible while working through an outbound workflow.
Decision point
Where it may fit
Predictive dialling
A campaign with established management capacity, active oversight and confirmed operational controls.
Progressive dialling
A team that values controlled pacing and a practical first conversation around agent readiness.
Decision point
Monitoring requirement
Predictive dialling
Active campaign monitoring and authorised adjustment remain important.
Progressive dialling
Campaign oversight, contact-data hygiene and responsible operating controls still remain important.
Decision point
Risk if poorly operated
Predictive dialling
A contact may be reached before an agent is ready, creating a poor experience.
Progressive dialling
The operation may move through attempts more conservatively than a highly automated campaign.
Decision point
What the mode does not decide
Predictive dialling
Lawful basis, consent where required, opt-outs, data quality, agent practice, campaign policy or customer treatment.
Progressive dialling
Lawful basis, consent where required, opt-outs, data quality, agent practice, campaign policy or customer treatment.
Decision point
Best next action
Predictive dialling
Discuss campaign scale, monitoring ownership and support boundaries with SureTel.
Progressive dialling
Discuss team workflow, hand-off requirements and the right hosted-dialler scope with SureTel.
Related, not identical
Manual and preview patterns can both give an agent more control before a call, but they describe different moments in the workflow. Manual dialling focuses on the agent initiating the call. Preview dialling focuses on showing the relevant record before the agent decides whether to initiate it. A system may support both; the terms should not be treated as interchangeable.
Manual path: agent selects or enters a permitted contact → agent initiates call → outcome follows agreed workflow
Preview path: record is presented → agent reviews available context → agent decides whether to initiate call → outcome follows agreed workflow
Manual and preview dialling are supporting workflow concepts on this page. They do not replace the predictive-versus-progressive comparison, and neither approach is lawful, suitable or fully featured by default.
Before you choose
The decision is not about selecting the most automated label. It is about agreeing how agents should receive work, what a customer experience should feel like, who monitors the campaign and where accountability sits when technology, voice, connectivity and business-owned data meet. A good discovery conversation turns those questions into a defined scope.
Is the team carrying out structured follow-up, service outreach, collections, sales activity or another approved business workflow?
How should the operation handle availability, pauses, preparation time, wrap-up and supervision before the next attempt is made?
What information may an agent see, who owns it, and what must be confirmed before any record is presented or contacted?
Which dispositions, next actions, callbacks or escalation paths need to be represented in the agreed operational process?
Which business role watches campaign behaviour, customer treatment, agent practice and exceptions?
Which dialler, voice and connectivity elements are in SureTel's agreed scope, and which customer, carrier or third-party elements remain separately owned?
Practical guidance
Progressive dialling is often the more practical first conversation where controlled pacing and agent readiness need to stay visible. It is guidance rather than a universal recommendation. Campaign purpose, team size, contact data, call policy, management capacity, connectivity and the agreed service scope must still be confirmed before anyone treats it as the right mode.
Start by discussing progressive dialling.
Why this remains a discovery question: The business may prefer a more deliberate hand-off while the workflow and controls are being established.
Discuss whether predictive dialling may be suitable.
Why this remains a discovery question: Suitability depends on active monitoring, authorisation, customer-experience controls and confirmed operating context.
Discuss preview dialling and whether an agent-led manual initiation is appropriate.
Why this remains a discovery question: The required record context, access rights and workflow remain specific to the business.
Discuss the broader Hosted VICIdial operating model.
Why this remains a discovery question: The commercial service page owns the full supplied-solution conversation.
Price orientation
A simple public starting point can help a buyer decide whether to continue the conversation. The actual scope still depends on confirmed agent numbers, workflow, calling requirements, recording needs, numbers, connectivity context and the agreed implementation boundary.
Price orientation — not a rate card
Hosted VICIdial from R120 per agent/month excl. VAT. Minimum 10 agents. Use the Hosted VICIdial Pricing page for the canonical pricing view and request a quote for a scoped service discussion.
Active monitoring
Predictive dialling is not a set-and-forget switch. A business needs an identified campaign owner who reviews how the operation behaves and responds when experience or operating conditions need attention. SureTel can support the supplied hosted-dialler scope and communicate within that scope, while the business retains responsibility for campaign decisions and customer treatment.
This checklist does not include dial-ratio values, pacing settings, configuration steps, list-upload instructions, caller-ID practices, silent-call thresholds or guidance intended to bypass direct-marketing obligations.
Responsibility boundary
Technology can support a configured workflow, but it cannot decide the business's legal basis, policies or customer-treatment standards. This guide is practical technology guidance only. Before publication, any broader legal or compliance wording must receive appropriate review against current South African requirements and the business's own sector obligations.
Business campaign objective
Business-owned: data, lawful basis where required, contact policy, opt-outs, recording policy
Mode discussion: predictive / progressive / manual / preview
Caveat inside this node: "Selecting a mode does not itself make a campaign lawful."
SureTel-supplied hosted-dialler scope + agreed support communication path
Business-owned: agent practice, campaign monitoring, customer treatment and legal review
This is a high-level responsibility map for a hosted-dialler conversation. It does not exhaustively describe legal obligations and does not transfer the business's campaign responsibilities to SureTel.
A useful first conversation
A useful first conversation begins with the business workflow, not a mode label. It should identify what the campaign needs to achieve, who owns operating decisions, what SureTel is being asked to supply and which dependencies sit elsewhere. The final solution and commercial scope should be based on those confirmed requirements.
Establish whether the need is outbound, inbound, blended or a broader call-centre operating-model discussion.
Confirm team shape, readiness, record review needs, expected outcomes, campaign oversight and any required business approvals.
Separate customer-owned data, policies and agent practice from SureTel-supplied dialler, voice and agreed connectivity components.
Consider progressive, predictive, manual and preview contexts only after the operating model has been understood.
Move to a Hosted VICIdial service discussion, canonical pricing page, broader call-centre solution page or a quote request according to the confirmed need.
SureTel can provide a clear contact point, communicate during issues and coordinate investigation within the agreed supplied-solution scope. This does not transfer responsibility for customer-managed data, campaign decisions, unrelated systems, site power, customer networks or external carrier faults outside that scope.
Next step
Explore SureTel's canonical hosted call-centre dialler service and start a scoped conversation.
View the canonical pricing page for approved commercial orientation.
Read the broader plain-English guide to hosted diallers and contact-centre workflow.
FAQs
Predictive dialling uses campaign pacing to place call attempts ahead of expected agent availability. Progressive dialling places the next attempt in a more controlled sequence around agent readiness. The right choice depends on the campaign, team, operating controls and monitoring ownership, not on a universal “best” setting.
Progressive dialling is often the more practical starting discussion where a business values controlled pacing and agent readiness. That is not a universal rule. Campaign purpose, team size, contact data, calling policies, connectivity context and management capacity still need to be confirmed before deciding on a route.
Predictive dialling may be worth discussing for a suitably managed, higher-volume outbound campaign with active monitoring and clear operating controls. It should not be selected simply because it appears more automated. The business remains responsible for campaign policy, customer treatment, agent practice and appropriate oversight.
No. Manual dialling describes the agent actively initiating the call. Preview dialling describes a workflow in which a record is presented for review before the agent decides whether to make the call. They can appear together in one operating flow, but they are not interchangeable terms and the exact implementation must be confirmed.
Manual dialling may be useful when an agent needs direct control over the timing of a call. It can be discussed where a business needs a considered workflow rather than automated pacing. The required information, permissions, recording, outcomes and support scope should be confirmed before relying on any particular manual-dial process.
Preview dialling may be useful when a business wants an agent to review available record context before deciding whether to initiate a call. It is not a promise of a specific screen, CRM integration, record source, script, data-quality outcome or compliance result. The workflow must be scoped according to the approved business requirements.
No. A dialling mode does not guarantee contact rates, sales, productivity, customer experience or campaign outcomes. Results can depend on many factors, including data quality, campaign purpose, staffing, scripts, management, policies, connectivity and the broader customer journey.
No. Selecting progressive dialling does not make a campaign lawful or compliant. Each business remains responsible for its data, consent or other lawful basis where required, opt-outs, contact policies, recording practices, campaign monitoring and obtaining its own legal advice.
SureTel Hosted VICIdial starts from R120 per agent per month excluding VAT, with a minimum of 10 agents. The final commercial scope depends on confirmed requirements. Use the Hosted VICIdial Pricing page or request a quote for the current commercial detail; this resource article does not replace the pricing page.
SureTel can communicate, support and coordinate investigation within the confirmed scope of the hosted solution it supplies. Customer-owned data, campaign decisions, site power, customer-managed networks, unrelated providers and third-party systems remain outside SureTel's control unless they are explicitly included in the agreed scope.
Next step
Share your team, campaign and agent-readiness needs so the hosted-dialler conversation starts with the operating reality.
Educational guide · Not legal advice · Your details are handled per SureTel's Privacy Policy.
Share enough context for a useful first conversation — we'll confirm fit before quoting.
SureTel