SureTel

Call Centre Startup Guide

How to Start a Call Centre in South Africa

A practical, operator-friendly walk-through of the decisions, technology and launch steps behind a South African call centre.

  • • Licensed South African ISP
  • • Operating since 2010
  • • Cloud PBX & Hosted VICIdial
  • • Connectivity, endpoints & support scoped together

Educational resource · SureTel covers the technology layer · Legal, HR, compliance and data-source decisions stay with the customer.

Answer first

Starting a call centre, in one paragraph

A South African call centre is a business set up to handle voice conversations at scale — inbound support, outbound sales, blended workflows or a small internal desk. The technology layer is a voice platform (Cloud PBX or Hosted VICIdial), business connectivity with backup, quality endpoints, a CRM and clear reporting. Legal, HR, compliance and data-source decisions sit with the customer. SureTel supplies and supports the technology; qualified advisers own the rest.

Startup readiness checklist

Ten decisions to make before signing anything

Walk this list first. Every technology, connectivity and compliance discussion downstream gets faster when these are answered.

  1. Define the operating model

    Decide: Inbound, outbound, blended or a small internal desk.

    Why it matters: Every downstream decision — headcount, dialler, connectivity, compliance — depends on this.

  2. Set the campaigns and workflows

    Decide: What each team actually does — sales, support, appointments, collections, retentions.

    Why it matters: Campaigns drive routing, scripts, dispositions and CRM design.

  3. Size the seat count and shifts

    Decide: Starting agents, growth ceiling, shift pattern and peak concurrency.

    Why it matters: Sizing sets bandwidth, licences, hardware and floor space.

  4. Choose the phone platform

    Decide: Cloud PBX for voice + basic queues, or Hosted VICIdial for volume dialling.

    Why it matters: The two solve different problems — mixing them without a plan wastes money.

  5. Plan connectivity and backup

    Decide: Business fibre or wireless as primary, plus LTE/5G backup.

    Why it matters: Call quality and campaign uptime depend on the line, not just the platform.

  6. Plan data sources and consent

    Decide: Where lead or contact data comes from and what lawful basis applies.

    Why it matters: POPIA, opt-outs and suppression must be sorted before the first outbound call — get qualified legal or compliance advice.

  7. Design the CRM and disposition flow

    Decide: One system of record, agreed dispositions, screen pops and callback rules.

    Why it matters: Reporting, QA and follow-up all depend on clean dispositions and one truth of record.

  8. Set the scripting and QA framework

    Decide: Opening, mandatory disclosures, objection paths, opt-out and QA rubric.

    Why it matters: Scripts protect brand and compliance; QA keeps them enforced without micromanaging.

  9. Budget for hardware and endpoints

    Decide: Softphones, headsets, desk phones where needed, PoE switches, network hardware.

    Why it matters: Quality endpoints and network kit are the difference between a working desk and a frustrated agent.

  10. Plan launch, training and support

    Decide: Cut-over date, training week, go-live support and escalation path.

    Why it matters: A quiet soft-launch beats a noisy hard-launch — plan the first two weeks in detail.

Choose your model

Five common call-centre shapes

Inbound, outbound, blended, small internal desk, BPO — every downstream decision (platform, dialler, connectivity, reporting) traces back to which of these you are actually running. See also: Inbound vs outbound call centres.

  • Inbound support

    Customers phoning in for help, orders or bookings.

    • Queues, skills-based routing, IVR and callbacks.
    • Service-level targets on answer time and abandonment.
    • Cloud PBX or VICIdial inbound suits most teams.
    • Success measured by resolution, CSAT and adherence.
  • Outbound sales

    Agents dialling a defined list for sales or lead qualification.

    • List management, dialling mode fit and disposition strategy.
    • Recorded scripts, objection paths and manager coaching.
    • Hosted VICIdial where sustained volume is required.
    • Compliance and consent posture reviewed with qualified advice.
  • Blended

    Teams that switch between inbound calls and outbound campaigns.

    • Priority routing so inbound never starves.
    • Presence rules and campaign pause on inbound spike.
    • One CRM, one wallboard, one QA rubric.
    • Suits mid-sized teams with variable demand.
  • Small internal desk

    A handful of internal agents handling calls alongside another job.

    • Cloud PBX with ring groups, IVR and voicemail is usually enough.
    • Softphones on existing laptops keep hardware light.
    • Reporting and QA scaled to team size — no wallboard needed.
    • Grows into a full desk without ripping out the platform.
  • BPO / outsourced contact centre

    A dedicated business selling contact-centre capacity to other brands.

    • Multi-tenant campaign design, isolated data per client.
    • Formal SLAs, reporting packs and QA per programme.
    • Higher-SLA connectivity, redundancy and continuity planning.
    • Client-specific compliance posture agreed contractually.

Minimum tech stack

The nine layers a working call centre relies on

None of these are optional. The question is which vendor supplies each layer and how they line up — SureTel covers the technology layers marked below.

  • Voice platform

    Required: Cloud PBX for queues and IVR, or Hosted VICIdial for dialler volumes.

    SureTel: SureTel supplies both and helps match platform to model.

  • Connectivity

    Required: Business fibre or wireless primary, with LTE/5G backup where feasible.

    SureTel: SureTel scopes coverage, feasibility and continuity per site.

  • Numbers

    Required: DIDs (geographic and non-geographic), plus porting for existing numbers.

    SureTel: Number provisioning and porting are handled by SureTel.

  • Endpoints

    Required: Softphones, headsets, desk phones where required, PoE switches, cabling.

    SureTel: SureTel recommends and supplies quality endpoints; existing kit reviewed on request.

  • Recording

    Required: Call recording aligned to a documented policy and retention window.

    SureTel: Recording is available on the platform; policy and legal review sit with the customer.

  • Reporting

    Required: Real-time wallboards, agent stats, campaign and queue reporting.

    SureTel: Reporting is scoped as part of platform setup; extended dashboards may be custom work.

  • CRM / integrations

    Required: One CRM of record, click-to-call, screen pops, disposition sync.

    SureTel: Standard integrations scoped up front; bespoke APIs or webhooks may require custom development.

  • Security & fraud

    Required: Toll-fraud controls, permission scopes, agent access reviews.

    SureTel: Platform-level controls; broader information-security and compliance sit with the customer.

  • Support & escalation

    Required: Named support path, documented escalation, hours of coverage.

    SureTel: Standard support Monday–Friday 08:00–17:00; 24/7 only where a qualifying SLA is in place.

Bespoke integrations, extended reporting and 24/7 support are scoped and priced separately. Standard support is Monday–Friday 08:00–17:00.

For platform detail see Cloud PBX, Hosted VICIdial, VoIP and SIP Trunking.

Hosted VICIdial dial modes

Match the dialling mode to the campaign and compliance posture

Dial modes are tools, not rankings. Predictive dialling is one option — it is not always the best choice and it requires responsible configuration and a data and consent posture that fits.

  • Manual

    Agents choose which number to call. Best for low-volume, high-value work and any list requiring judgement before dialling.

  • Preview

    The next record is shown to the agent before the call is placed. Suits qualified follow-ups where the agent needs context first.

  • Progressive

    One call is placed per available agent. Predictable, safer for compliance profiles that need agent presence at connect.

  • Predictive

    The dialler places multiple calls per agent based on pacing models. Requires responsible configuration and a compliance/data posture that fits — it is one option, not a default best.

  • Inbound

    Queues, skills-based routing, IVR and callback. Runs alongside outbound in blended workflows without starving inbound.

  • Blended

    Agents flip between inbound and outbound with priority rules. Presence and pacing decide how aggressive outbound gets during quiet inbound moments.

For commercial detail on the dialler platform see Hosted VICIdial and the call-centre solution overview at Call Centre Communications.

Connectivity & network readiness

Call quality is a network problem, not just a platform one

Even the best platform sounds bad on a badly-designed line. Quality and campaign uptime depend on the primary connection, backup path, endpoints, power and how the network is configured — perfect quality is not promised without these in place.

  • Symmetrical primary line sized for peak concurrent calls plus overhead.
  • QoS or a dedicated voice VLAN so calls aren't hurt by general office traffic.
  • Cabled agent desks where possible; Wi-Fi only where the network is properly designed.
  • PoE switches and reputable headsets on every desk — cheap endpoints kill call quality.
  • UPS on the router, firewall, PoE switches and any onsite call-centre kit.
  • Router / firewall configured for the platform (SIP, ports, ALG behaviour).
  • Backup connectivity path — LTE/5G or an alternative fixed line where feasible.
  • Documented escalation for line, platform and endpoint faults.
  • Single-office desk

    Backup: LTE/5G router with dual-WAN failover.

    Caveat: Coverage, signal quality and package need to be checked per address.

  • Larger call floor

    Backup: LTE/5G backup plus a second fixed line where feasible.

    Caveat: Feasibility, cost and lead times vary; higher-SLA options exist where scoped.

  • Multi-branch operation

    Backup: Backup per site, plus platform-level failover to alternative sites.

    Caveat: Requires design work — routing, presence and reporting need to line up across branches.

  • Home / hybrid agents

    Backup: Home business line with LTE/5G backup where available.

    Caveat: Home connectivity is not enterprise-grade; QA and support responsibilities sit differently.

Coverage and feasibility per site: Business Connectivity, Business Fibre, Wireless Internet, Licensed Microwave and LTE/5G Backup.

Compliance & governance

Plan compliance before campaigns, not after

Important — technology layer, not legal advice

SureTel can help with the telephony and call-centre technology layer. The customer remains responsible for legal, compliance, HR, data-source, script and business-process decisions.

SureTel does not make the customer POPIA-compliant, does not write business plans, does not register companies, does not provide legal or compliance sign-off, and does not supply lead databases. This resource flags planning considerations only — get qualified legal or compliance advice for the specifics.

  • Lawful basis and consent

    Understand the lawful basis for calling each list and how consent was captured. POPIA, direct-marketing rules and opt-out expectations must be planned up front — get qualified legal or compliance advice.

  • Opt-outs and suppression

    Every campaign needs a working opt-out mechanism and a suppression list that agents cannot bypass. Suppression should apply across campaigns, not per list.

  • Data sources and quality

    Lists must come from documented, lawful sources. SureTel does not supply lead databases. Data quality controls sit with the customer and their compliance advisers.

  • Call recording policy

    Recording is useful for QA, training and disputes. The customer decides notification, retention and access rules, and should have those reviewed by legal or compliance.

  • Agent conduct and scripting

    Opening disclosures, objection paths and the mandatory close protect brand and compliance. QA enforces the script without micromanaging tone.

  • Access and permission control

    Agent, supervisor and admin roles limit what each user can see, change or export. Reviews of access should happen when roles change.

  • Governance and evidence

    Keep documented policies for consent, recording, retention and complaints. If a regulator asks, evidence beats memory.

  • Complaints and disputes

    A documented complaints process — logging, response times, resolution and escalation — reduces regulatory and reputational risk.

This is not legal advice and no bypass of consent, opt-out or suppression rules is implied or supported.

CRM, scripts & agent workflow

One system of record, one workflow, one QA loop

The CRM is not just a database — it is where the agent lives and where every disposition, callback and QA note lands. Bespoke API or webhook work may require custom development; standard connectors are scoped up front. See also: CRM integration for call centres.

  1. One CRM of record

    Pick one system agents live in — never two half-populated CRMs. Every call, disposition and note lands in the same record.

  2. Contact and campaign linkage

    Each contact record is linked to its campaign, source and consent state so QA and reporting can join the dots.

  3. Screen-pop on connect

    The agent sees the contact record the moment the call connects — no manual searching between rings.

  4. Standardised dispositions

    Agreed disposition codes per campaign, with clear rules for callbacks, follow-ups and no-contact.

  5. Callback rules

    Callbacks are scheduled in the CRM and honoured by the dialler — no missed appointments hidden in agent notebooks.

  6. Notes and script prompts

    Scripts prompt the agent through the required disclosures; free-form notes capture what the record doesn't.

  7. Compliance touchpoints

    Opt-outs, consent captures and complaints flow into the CRM with the same weight as sales activity.

  8. QA and coaching loop

    Recorded calls are sampled against the QA rubric; feedback closes the loop with agents and supervisors.

Budget & cost factors

What actually drives call-centre cost

No price list survives contact with a real operation. The table below lays out the cost factors — what each area depends on. Hosted VICIdial pricing is referenced once as an indicative starting point; commercial detail sits on the platform page.

  • Agents / seats

    Drivers: Number of concurrent agents, growth ceiling, shift pattern.

    Notes: Per-seat licensing dominates most call-centre budgets.

  • Dialler mode and minimums

    Drivers: Manual, preview, progressive, predictive, inbound, blended; platform minimums.

    Notes: Hosted VICIdial from R120 per agent per month, minimum 10 agents, excl. VAT, where suitable.

  • Voice minutes / call charges

    Drivers: Call volume, destinations, geographic vs mobile mix.

    Notes: Rated separately from platform licences; reviewed monthly.

  • Connectivity

    Drivers: Primary line type, capacity, SLA tier, backup path.

    Notes: Feasibility per address; higher SLA and dedicated products cost more.

  • Endpoints and hardware

    Drivers: Softphones vs desk phones, headsets, PoE switches, cabling, UPS.

    Notes: Quality endpoints materially affect call quality — not the place to cut.

  • CRM integration scope

    Drivers: Standard connectors, screen-pops, bespoke APIs or webhooks.

    Notes: Standard integrations are scoped up front; bespoke work is scoped and priced separately.

  • Recording and retention

    Drivers: Storage window, access model, export needs.

    Notes: Longer retention and more granular access controls add cost.

  • Support and SLA

    Drivers: Standard hours or qualifying 24/7 SLA, escalation depth.

    Notes: 24/7 support only where a qualifying SLA is in place; standard hours are Mon–Fri 08:00–17:00.

Indicative pricing only — no sales, collections, productivity or campaign-result guarantees are made. For commercial detail on the dialler platform see Hosted VICIdial.

Common mistakes

The mistakes that trip new call centres up

These come up on nearly every scoping call. See also: Common call-centre problems.

  • Picking the platform before the model

    Choosing Cloud PBX or VICIdial before deciding the operating model wastes licences and forces workarounds.

  • Under-sizing the line

    A line sized for browsing is not a line sized for concurrent voice — call quality collapses on day one.

  • Cheap endpoints

    The wrong headset is the loudest customer complaint on any call floor. Quality endpoints are cheaper than churn.

  • No backup path

    One line and no failover means one cable break stops revenue. Backup is a cost of doing business, not a nice-to-have.

  • Assuming predictive is always best

    Predictive dialling suits some campaigns and not others. Match the mode to the campaign and compliance posture.

  • Two CRMs of half-truth

    When agents live in one system and reporting comes from another, both are wrong by the end of the week.

  • No opt-out discipline

    Weak suppression is a regulatory and brand risk. Opt-out must be honoured across every campaign, every time.

  • No QA or coaching loop

    Recording without QA is storage. Sample calls, feed back and coach — otherwise scripts drift within a month.

Use cases

Where call-centre technology shows up in real businesses

  • Insurance sales and retentions

    Outbound qualification with blended inbound for renewals and cancellations.

  • Collections

    Structured outbound campaigns with strict compliance, recording and suppression.

  • Automotive service and sales

    Inbound bookings, outbound follow-up on quotes and service reminders.

  • Medical scheme support

    Inbound queues with skills-based routing, callback and case notes.

  • Pharmacy and healthcare bookings

    Appointment setting, reminders and inbound support.

  • Retail and e-commerce support

    Order queries, returns and outbound recovery on abandoned baskets.

  • Professional services

    Small internal desks handling client calls with CRM notes and callbacks.

  • BPO for external brands

    Multi-programme delivery with isolated data, SLAs and QA per client.

  • Startup call centre

    10–25 seat launch with tight budget control, phased hardware and clear growth path.

What SureTel can help with

The technology layer, delivered as one scope

  • Voice platform setup

    Cloud PBX or Hosted VICIdial provisioned to match the operating model — inbound, outbound, blended or BPO.

  • Connectivity scoping

    Business fibre, wireless or licensed microwave as primary, with LTE/5G backup where feasible.

  • Numbers and porting

    New DIDs, geographic and non-geographic numbers, and porting for existing numbers.

  • Endpoints and network kit

    Softphones, desk phones, headsets, PoE switches and cabling recommendations.

  • Standard integrations

    Click-to-call, screen pops and disposition sync with common CRMs; bespoke integrations scoped separately.

  • Recording and reporting

    Platform-level call recording and reporting, aligned to a customer-owned policy and retention window.

  • Launch and training support

    Cut-over planning, agent training on the platform and go-live support inside standard hours.

  • Ongoing support

    Support within the supplied solution scope; documented escalation; 24/7 only where a qualifying SLA is in place.

What SureTel does not do

  • Register companies, write business plans or provide legal, tax or HR advice.
  • Sign off customer POPIA, compliance or data-governance posture — that stays with the customer and their qualified advisers.
  • Supply lead databases or contact lists.
  • Guarantee sales, collections, productivity, answer rates or campaign results.
  • Bypass consent, opt-out or suppression rules.
  • Blame upstream providers or competitors for outcomes inside the supplied solution scope.

Licensed South African ISP · ICASA licence 0009/CECS/AUG/09 · Operating since 2010 · Standard support Monday–Friday 08:00–17:00.

Launch process

An eight-step path from first call to live campaigns

  1. Discovery call

    Understand the operating model, campaign types, seat count and site addresses.

  2. Feasibility and coverage check

    Confirm connectivity options and backup paths per site.

  3. Platform recommendation

    Cloud PBX, Hosted VICIdial or a mix — matched to the operating model and campaign mix.

  4. Written quote and scope

    Platform, connectivity, endpoints, integrations, recording, reporting, support and any custom work — all priced separately.

  5. Provisioning and configuration

    Numbers, platform tenants, queues, campaigns, users, roles and standard integrations set up.

  6. Endpoint delivery and network prep

    Endpoints supplied and configured; network readiness (QoS, cabling, UPS) confirmed on site.

  7. Agent training and soft-launch

    Small live pilot with real calls, QA sampling from day one, adjustments before ramp.

  8. Ramp and support handover

    Scale up campaigns, hand over to standard support, agree escalation and review cadence.

Related resources

Keep planning the call-centre stack

Call-centre startup FAQs

Frequently asked questions

What does it take to start a call centre in South Africa?

At a minimum: a defined operating model (inbound, outbound, blended or a small internal desk), a voice platform (Cloud PBX or Hosted VICIdial), business connectivity with backup, quality endpoints and network kit, a CRM, a documented recording and QA process, and a compliance posture reviewed by qualified legal or compliance advisers. SureTel supplies the technology layer; the business, legal and HR decisions stay with the customer.

What does SureTel actually help with?

SureTel helps with the telephony and call-centre technology layer: Cloud PBX or Hosted VICIdial, business connectivity and backup, numbers and porting, endpoints, standard CRM integrations, platform-level recording and reporting, launch planning and ongoing support inside the supplied solution scope.

What is the difference between inbound, outbound and blended?

Inbound handles calls coming into the business — support, orders, bookings. Outbound is agents dialling a list for sales, appointments, collections or qualification. Blended lets the same agents switch between the two with priority rules so inbound never gets starved when outbound is busy.

Do I need Hosted VICIdial or is Cloud PBX enough?

Cloud PBX is enough for most inbound-heavy teams and small internal desks that need queues, IVR, ring groups and voicemail. Hosted VICIdial is designed for outbound and blended teams that need dialling modes, campaign management and dialler-style reporting. A short scoping call is usually the fastest way to decide.

How does POPIA affect starting a call centre?

POPIA and related direct-marketing rules affect how contact data can be collected, held, used and opted out of. This resource flags POPIA as a planning consideration only — it is not legal advice. Get qualified legal or compliance advice on lawful basis, consent capture, opt-outs, suppression, retention and complaint handling before running outbound campaigns.

Is predictive dialling always the best mode?

No. Predictive dialling suits some outbound campaigns and not others. It requires responsible pacing configuration and a compliance and data posture that fits. Progressive, preview and manual modes exist for a reason and are the right choice for many campaigns. Match the mode to the campaign, not the other way around.

What should the call-recording policy cover?

A recording policy should cover notification to callers where required, retention window, access controls, permitted use (QA, training, disputes) and secure disposal. Recording is available on the platform; the specific policy, notifications and retention rules should be agreed with qualified legal or compliance advisers.

Can SureTel integrate the phone system with our CRM?

Standard integrations — click-to-call, screen pops and disposition sync — are scoped up front for common CRMs. Bespoke APIs, webhooks or deeper workflow integrations may require custom development and are scoped and priced separately before any commitment.

How much does it cost to start a call centre?

Cost depends on seat count, dialling mode, connectivity, endpoints, CRM scope, recording and retention, and support level. As an indicative starting point, Hosted VICIdial is from R120 per agent per month, minimum 10 agents, excl. VAT, where suitable — see /services/hosted-vicidial for commercial detail. Connectivity, endpoints, integrations and support are quoted separately.

Next step

Scope the technology layer for your call centre

Tell SureTel about the operating model, seat count and sites. SureTel will recommend the right platform mix (Cloud PBX, Hosted VICIdial, VoIP), scope connectivity and backup, and put a written scope on paper.

Call-centre technology scoping only. Your details are handled according to SureTel’s Privacy Policy.

Required for business connectivity, onsite PBX, onsite Managed IT and CCTV. Optional but useful for other services.

Consent
No errors
Privacy Policy

Protected by reCAPTCHA — Google's Privacy and Terms apply.