SureTel
Call-centre models compared
Inbound vs Outbound Call Centres
Purpose, tools, reporting and compliance for inbound, outbound and blended call centres — before scoping VoIP, dialler or connectivity.
- • Cloud PBX & Hosted VICIdial
- • Licensed South African ISP
- • Operating since 2010
- • Technology layer scoped end-to-end
Educational resource · SureTel covers the technology layer · Legal, HR and compliance decisions stay with the customer.
Answer first
Inbound, outbound and blended, in one paragraph
An inbound call centre answers calls from customers — support, orders, bookings — using queues, IVR and skills-based routing. An outbound call centre dials a lawful list for sales, appointments or collections, using campaigns, dial modes and dispositions. A blended team runs both with priority rules so inbound is never starved. The right model shapes every downstream decision — platform, dialler, connectivity, reporting and compliance planning.
Quick comparison
Inbound, outbound and blended side by side
One table, six columns. Read across each row before choosing a platform or dial mode.
| Model | Purpose | Callers | Core tools | Reporting focus | Common risk |
|---|---|---|---|---|---|
| Inbound | Answer calls the business receives — support, orders, bookings. | Customers, prospects and existing accounts phoning in. | IVR, queues, skills-based routing, callbacks, recording. | Service level, answer time, abandon rate, first-call resolution. | Long queues, missed calls, uneven agent load. |
| Outbound | Reach a defined list — sales, follow-up, appointments, collections. | Contacts on a lawful list; opt-outs suppressed. | Campaigns, dial modes, dispositions, scripts, CLI, recording. | Contact rate, connect rate, conversion, disposition mix. | Compliance exposure, list quality, wrong dial mode for the campaign. |
| Blended | Same agents handle inbound and outbound with priority rules. | Mix of inbound callers and outbound contacts. | All of the above plus priority routing and campaign pause/resume. | Separated inbound and outbound metrics on one wallboard. | Inbound starvation and reporting muddle without clear rules. |
Inbound
Purpose: Answer calls the business receives — support, orders, bookings.
Callers: Customers, prospects and existing accounts phoning in.
Core tools: IVR, queues, skills-based routing, callbacks, recording.
Reporting: Service level, answer time, abandon rate, first-call resolution.
Risk: Long queues, missed calls, uneven agent load.
Outbound
Purpose: Reach a defined list — sales, follow-up, appointments, collections.
Callers: Contacts on a lawful list; opt-outs suppressed.
Core tools: Campaigns, dial modes, dispositions, scripts, CLI, recording.
Reporting: Contact rate, connect rate, conversion, disposition mix.
Risk: Compliance exposure, list quality, wrong dial mode for the campaign.
Blended
Purpose: Same agents handle inbound and outbound with priority rules.
Callers: Mix of inbound callers and outbound contacts.
Core tools: All of the above plus priority routing and campaign pause/resume.
Reporting: Separated inbound and outbound metrics on one wallboard.
Risk: Inbound starvation and reporting muddle without clear rules.
Choose the model by purpose
Which shape fits your operation?
Customer support desk
Callers phone in for help, orders or bookings. Volume comes to you.
Usually fits: Inbound. Cloud PBX with queues and IVR is usually enough.
Outbound sales team
Agents dial a lawful list to sell, qualify or renew.
Usually fits: Outbound. Hosted VICIdial suits sustained volume with campaigns.
Collections team
Structured outbound with strict compliance, recordings and suppression.
Usually fits: Outbound (usually preview or progressive) with tight governance.
Bookings and appointment setting
Outbound reminders and inbound confirmations, often in the same day.
Usually fits: Blended — inbound priority, outbound during quieter windows.
Multi-department operation
Support, sales and retentions running side by side, each with its own campaign or queue.
Usually fits: Blended with skills-based routing and separate reporting per team.
Inbound requirements
What an inbound call centre relies on
Inbound lives or dies on queue design, routing and callback discipline. Recording access is limited to authorised users; features vary depending on the platform and licence.
IVR / auto-attendant
Route callers to the right queue by menu — after-hours, language or department options where scoped.
Queues and skills-based routing
Match callers to agents by skill, priority or opening hours; overflow rules keep queues moving.
Callbacks
Offer a callback in place of waiting — reduces abandon rate without adding seats.
Service-level reporting
Answer time, abandon rate, service-level targets and first-call resolution, viewed live and historically.
Recordings for QA
Inbound calls recorded per a documented policy; access limited to authorised users.
Wallboards
Live queue status and service-level tiles on-floor or on desktops — depending on the platform and licence.
After-hours handling
Voicemail, on-call routing, holiday schedules and clear closed-hours messaging.
Cloud PBX or VICIdial inbound
Cloud PBX suits most inbound desks; VICIdial inbound is used where inbound sits inside a larger blended platform.
Inbound platform detail: Cloud PBX, Call Queues Explained and Auto-Attendants (IVR) Explained.
Outbound requirements
What an outbound call centre relies on
Outbound is a campaign discipline before it is a platform. Lists, dial modes, dispositions and reporting must be aligned to the campaign and the compliance posture — predictive dialling is one option, not a default best. Get qualified legal or compliance advice before running outbound campaigns.
Campaigns
Each campaign has its own list, script, dispositions, CLI and reporting — never one giant undifferentiated queue.
Lists and suppression
Documented, lawful lists; opt-outs and suppression applied across campaigns, not per list.
Dial modes
Manual, preview, progressive and predictive — chosen per campaign and compliance posture, not by default.
Dispositions and callbacks
Agreed disposition codes, scheduled callbacks honoured by the dialler, and clear rules for no-contact.
Scripts and disclosures
Opening, mandatory disclosures, objection paths and opt-out prompt — enforced through QA without micromanaging.
Caller ID (CLI)
Consistent, correct CLI per campaign so contacts recognise the number and legitimate returns route back.
Recording and QA
Recordings sampled against a QA rubric; access limited to authorised users; retention aligned to policy.
Campaign reporting
Contact rate, connect rate, agent talk-time, disposition mix and conversion — reviewed daily, not weekly.
Outbound platform detail: Hosted VICIdial, Predictive Dialer vs Progressive Dialer and Call Recording for Business.
Blended requirements
Blended only works with priority rules
Blended is not "outbound whenever the phone stops ringing". Inbound gets priority; outbound pacing eases when inbound spikes. Reporting stays separated so inbound and outbound never share a tile.
Priority rules
Inbound gets priority so waiting callers are never starved by outbound pacing.
Skills-based blending
Agents blend only across campaigns and queues they are skilled for — no unqualified transfers.
Load balancing
Outbound pacing eases when inbound spikes; campaigns pause or slow automatically where supported.
Pause and wrap-up
Wrap-up codes and pause reasons captured cleanly so schedule adherence stays measurable.
Live monitoring
Supervisors listen, whisper or barge on any call within their scope — depending on the platform and licence.
Separated reporting
One wallboard, but inbound and outbound metrics never mixed in the same tile.
Blended warning
Blended without priority rules starves inbound. Blended without separated reporting hides the problem. Both must be set up before the first campaign runs — no guarantees on answer rate or campaign outcomes are made or implied.
Where Hosted VICIdial fits
The needs Hosted VICIdial is built for
SureTel helps with the telephony and call-centre technology layer; legal, HR, compliance and data-source decisions stay with the customer. Hosted VICIdial suits some models and not others — SureTel will recommend Cloud PBX where it fits better, depending on the platform and licence.
The need
Sustained outbound campaigns with multiple dispositions and callbacks.
How Hosted VICIdial fits
Hosted VICIdial handles campaigns, lists, dispositions and callbacks as first-class objects.
The need
A campaign that needs predictive or progressive dialling for volume.
How Hosted VICIdial fits
Dial modes are per-campaign; predictive is one option, chosen only where the campaign and compliance posture support it.
The need
Blended team switching between inbound and outbound with priority rules.
How Hosted VICIdial fits
Blended workflows keep inbound priority while outbound pacing adjusts around it.
The need
Recordings sampled against a QA rubric across campaigns.
How Hosted VICIdial fits
Recording and QA sampling supported on the platform; access limited to authorised users.
The need
Daily reporting on contact rate, disposition mix and agent talk-time.
How Hosted VICIdial fits
Reporting and wallboards ship with the platform; extended dashboards may be scoped as custom work.
The need
Small inbound-only desk with queues and IVR.
How Hosted VICIdial fits
Cloud PBX usually fits better than VICIdial for pure inbound — SureTel will recommend the right platform.
No guarantees on sales, collections, productivity, answer rate or campaign outcomes are made or implied.
Reporting metrics by model
What each model measures
Reporting supports decisions — it does not guarantee performance, sales, answer rate or campaign outcomes.
| Model | Useful metrics |
|---|---|
| Inbound | Answer time, service level (e.g. 80/20), abandon rate, average handle time, first-call resolution, callback take-up. |
| Outbound | Contact rate, connect rate, agent talk-time, disposition mix, conversion, callback compliance, opt-out rate. |
| Blended | Inbound service level plus outbound contact/connect rate — separated per campaign; presence and pause reasons per agent. |
Inbound
Answer time, service level (e.g. 80/20), abandon rate, average handle time, first-call resolution, callback take-up.
Outbound
Contact rate, connect rate, agent talk-time, disposition mix, conversion, callback compliance, opt-out rate.
Blended
Inbound service level plus outbound contact/connect rate — separated per campaign; presence and pause reasons per agent.
Deeper reporting: Cloud PBX Analytics & Call Reporting.
VoIP, connectivity & hardware
Call quality is a network problem, not just a platform one
The same physical layer supports inbound queues and outbound campaigns — sized for concurrent voice, protected by backup connectivity, and delivered on quality endpoints.
VoIP and call routing
Business VoIP sized for concurrent calls, with the dialler or PBX routing per campaign, queue and skill.
Primary connectivity
Business fibre, wireless internet or licensed microwave as the primary line — feasibility per address.
Backup connectivity
LTE/5G backup with dual-WAN failover keeps campaigns and inbound queues moving when the primary drops.
Endpoints
Reputable headsets, PoE switches and softphones or desk phones per role — the loudest customer complaint is a bad headset.
Internal network
QoS or a dedicated voice VLAN, cabled desks where possible, UPS on router, firewall and PoE switches.
Cost note
Call-centre platform, VoIP, connectivity and hardware costs depend on agent count, features, usage, connectivity and support.
Feasibility per site: VoIP and Business Connectivity.
Compliance & governance
Plan compliance before campaigns, not after
Important — technology layer, not legal advice
Call-centre compliance depends on your operating model, data source, scripts, recording practices and internal policies. This guide is general information only; get legal or compliance advice for your exact requirements.
SureTel does not make the customer POPIA-compliant, does not sign off compliance posture, and does not supply lead databases. No bypass of consent, opt-out or suppression rules is implied or supported.
- Lawful basis for every contact list documented before dialling.
- Working opt-out and suppression applied across every campaign, not per list.
- Recording policy covering notification, retention, access and permitted use.
- Access controls on recordings limited to authorised supervisors and QA staff.
- Agent, supervisor and admin roles reviewed when responsibilities change.
- Documented complaints and disputes process, with logged response times.
- Legal or compliance advice obtained on POPIA, direct marketing and scripts.
Use cases
Where inbound, outbound and blended show up
Customer support
Inbound queues with IVR, skills-based routing and callbacks; recordings for QA.
Bookings and appointments
Blended team confirming inbound bookings and reminding outbound the same day.
Pharmacy and healthcare
Inbound support, appointment reminders and prescription-refill callbacks.
Insurance sales and retentions
Outbound qualification and blended inbound for renewals and cancellations.
Automotive service and sales
Inbound bookings, outbound follow-up on quotes and service reminders.
Collections
Structured outbound with strict compliance, recording and suppression.
Sales development
Outbound qualification with preview or progressive dialling and CRM sync.
BPO / outsourced contact centre
Multi-programme delivery with isolated data, SLAs and QA per client.
Solution overview: Call Centre Communications.
Common mistakes
The mistakes that make inbound and outbound miserable
Running outbound as inbound
Answering calls all day is not a campaign — outbound needs lists, dispositions and pacing to work.
Running inbound as outbound
Queues and IVR do not solve for lists, dial modes and dispositions — the wrong tool starves the desk.
One giant queue for everything
Multi-department calls need skills-based routing, not one long line hoping the right agent picks up.
Predictive dialling by default
Predictive suits some campaigns and not others. Match the mode to campaign, data quality and compliance posture.
Weak opt-out discipline
Weak suppression is a regulatory and brand risk. Opt-out must be honoured across every campaign, every time.
Blending without priority rules
Blended without inbound priority means callers wait while outbound dials; inbound must never be starved.
One CRM you love, another you fill in
Two half-populated systems are both wrong by Friday. Pick one system of record and enforce it.
Reporting after the campaign ends
Contact rate and disposition mix reviewed weekly is a post-mortem; review daily to steer while it still helps.
How each flow actually runs
Inbound and outbound, step by step
Inbound is shaped by who calls in. A caller reaches the business, an auto-attendant identifies intent, a queue routes to the right skill, an agent handles the call with the customer record on screen, a disposition is captured and the recording lands under a documented policy. Reporting looks backward at service level and abandon rate, and forward at capacity planning.
Outbound is shaped by who the business is trying to reach. A lawful, opt-out-suppressed list is loaded, the dial mode is chosen per campaign, the agent connects, disclosures and scripts run, a disposition is captured, and callbacks or suppression close the loop. Reporting steers pacing, list quality and disposition mix daily.
Blended runs both flows on the same agents with priority rules. Inbound always wins the next available agent when a queue is waiting; outbound pacing eases automatically. Both flows depend on the same underlying VoIP, connectivity, endpoints and QA discipline.
Inbound flow
- Caller
- IVR / auto-attendant
- Queue with skills-based routing
- Agent (with screen-pop)
- Disposition & recording
- Service-level reporting
Outbound flow
- Lawful list
- Dial mode (manual / preview / progressive / predictive)
- Agent connected
- Script, disclosures & disposition
- Callback or suppression
- Campaign reporting
SureTel implementation path
From first call to live campaigns, in seven steps
SureTel scopes the telephony, dialler, VoIP, recordings, reporting and connectivity layer. Legal, HR and campaign-compliance decisions stay with the customer and their qualified advisers. Call-centre platform, VoIP, connectivity and hardware costs depend on agent count, features, usage, connectivity and support.
Discovery call
Understand the operating model, campaign types, seat count, sites and current pain points.
Model recommendation
Inbound, outbound or blended — recommended per team, not forced onto every desk.
Platform scope
Cloud PBX, Hosted VICIdial or a mix, matched to the recommended model.
Connectivity and backup
Feasibility per site, primary line, LTE/5G backup and network readiness confirmed.
Compliance and CRM design
SureTel scopes the technology; the customer's qualified advisers own POPIA, scripts and lawful-basis decisions.
Provisioning and training
Numbers, queues, campaigns, dispositions and agent training delivered as one scope.
Soft-launch and ramp
Small live pilot, QA sampling from day one, then ramp under standard support.
Licensed South African ISP · ICASA licence 0009/CECS/AUG/09 · Operating since 2010 · Standard support Monday–Friday 08:00–17:00.
Related resources
Keep planning the call-centre stack
- How to Start a Call Centre in South Africa
Operating model, platform, connectivity, compliance planning and launch steps for a South African call centre.
- What is VICIdial?
A plain-English explainer of the open-source contact-centre platform and how hosted delivery works.
- Predictive Dialer vs Progressive Dialer
Compare predictive and progressive dialling and prepare for a responsible hosted-dialler discussion.
- Call Queues Explained
How queues, routing strategies, callbacks and overflow keep inbound service levels honest.
- Auto-Attendants (IVR) Explained
How auto-attendants and IVR menus route inbound calls, including after-hours rules.
- Call Recording for Business
A practical guide to business call recording, retention, permissions and notices.
Inbound vs outbound FAQs
Frequently asked questions
What is the difference between an inbound and outbound call centre?
An inbound call centre answers calls the business receives — support, orders or bookings — using queues, IVR and skills-based routing. An outbound call centre dials a lawful list for sales, follow-up, appointments or collections, using campaigns, dial modes and dispositions. Blended teams do both with priority rules so inbound is never starved.
What is a blended call centre?
A blended call centre is a single team of agents who handle inbound calls and outbound campaigns with priority rules. Inbound gets first call on their time; outbound pacing eases when inbound spikes. Reporting stays separated so inbound service level and outbound contact rate never share a tile.
Which model does my business need?
Support and order desks are inbound. Sales, follow-up, appointments and collections are outbound. Teams handling both — a booking desk that also confirms, or sales and retentions — are usually blended. The right answer depends on who calls whom, campaign volume and compliance posture. SureTel scopes this before recommending a platform.
Is predictive dialling always the best outbound mode?
No. Predictive suits some outbound campaigns and not others. It requires responsible pacing configuration and a compliance and data posture that fits. Manual, preview and progressive modes are the right choice for many campaigns. Match the mode to the campaign, data quality and compliance risk, not the other way around.
Can Hosted VICIdial run inbound as well as outbound?
Yes — Hosted VICIdial supports inbound queues, IVR, blended workflows and outbound campaigns depending on the platform, licence and configuration. For pure inbound desks Cloud PBX is often the simpler fit. SureTel will recommend the right platform for the model rather than default to VICIdial.
How is call-centre performance measured?
Inbound uses answer time, service level, abandon rate, average handle time and first-call resolution. Outbound uses contact rate, connect rate, disposition mix, conversion and callback compliance. Reporting supports decisions but does not guarantee sales, answer-rate or campaign outcomes.
How does POPIA affect inbound vs outbound?
POPIA and related direct-marketing rules mainly affect outbound campaigns — lawful basis, consent, opt-outs, suppression, recordings and retention. Inbound has its own recording, retention and data-handling considerations. This resource flags planning considerations only; get qualified legal or compliance advice for the specifics.
Do inbound and outbound need different connectivity?
The requirements are similar — sized voice bandwidth, QoS or voice VLAN, UPS and backup connectivity. Outbound at volume adds concurrent-call load, so line sizing and pacing need to line up. LTE/5G backup with dual-WAN failover keeps both inbound queues and outbound campaigns moving when the primary line drops.
What does SureTel actually help with?
SureTel helps with the telephony and call-centre technology layer: Cloud PBX or Hosted VICIdial, VoIP, business connectivity and backup, numbers and porting, endpoints, platform-level recording and reporting, standard CRM integrations, and support inside the supplied solution scope. Legal, HR, compliance and data-source decisions stay with the customer.
Next step
Scope the right call-centre model with SureTel
Tell SureTel about the operating model, seat count and sites. SureTel will recommend inbound, outbound or blended, match the platform (Hosted VICIdial or Cloud PBX), 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.