SureTel
Diagnose before you replace
Common Call Centre Problems
Missed calls, long queues, poor voice quality, weak reporting — most call-centre problems are not the dialler. Diagnose the real cause before you replace anything.
- • Technology, process, data & connectivity
- • Licensed South African ISP
- • Operating since 2010
- • No performance guarantees implied
Educational resource · SureTel covers the technology layer · Legal, HR and compliance decisions stay with the customer.
Answer first
What "common call-centre problems" actually are
Common call-centre problems fall into five buckets — technology, process, staffing, data and connectivity. The same symptom (missed calls, abandoned calls, poor voice quality, weak reporting) can come from any of them. Diagnosing the bucket before choosing a fix matters more than replacing the dialler. SureTel helps with the technology layer; staffing, HR, script, list-quality and compliance decisions stay with the customer.
Problems & likely causes
What the symptoms usually mean — and what can actually help
A new dialler is not a guaranteed fix. Many of these problems are process, data, staffing or connectivity problems that a dialler cannot solve on its own — the fix must match the actual cause.
| Problem | Likely causes | What can help |
|---|---|---|
| Missed inbound calls | IVR mis-routes, queue not sized to volume, unstaffed windows, callback not offered, phones ringing off-hook at reception. | Redesign IVR and queues, add callback offers, review roster vs forecast and confirm endpoints are healthy. |
| Long hold times / high abandon | Under-staffed peaks, one giant queue, no skills-based routing, no callback path, weak wrap-up discipline. | Split queues by skill, add callbacks, tighten wrap-up codes and forecast peaks against the real intraday curve. |
| Poor voice quality | Under-sized line, no QoS, Wi-Fi voice, poor cabling, weak headsets, packet loss upstream. | Size the line for concurrent calls, apply QoS or a voice VLAN, cable desks, replace cheap endpoints, add backup connectivity. |
| Low outbound contact rate | Weak list quality, wrong CLI, wrong dial mode for the campaign, no suppression, no callback honouring. | Customer to review list source and lawful basis; SureTel scopes CLI, dial-mode fit and suppression on the platform. |
| No queue or campaign visibility | Reporting turned off, no wallboards, metrics reviewed weekly not daily, no separation of inbound and outbound. | Enable platform reporting, add wallboards where scoped, split reporting per queue/campaign, review daily. |
| No call recordings or QA | Recording disabled, retention unclear, no access controls, no QA rubric or sampling cadence. | Enable recording with a documented policy and access controls; establish QA sampling — QA discipline is customer-owned. |
| No CRM integration | No click-to-call, no screen-pops, agents key call notes into two systems, dispositions not synced. | Scope click-to-call and screen-pops with the CRM; deeper syncs may require custom development. |
| Weak escalation and callbacks | No supervisor routing, callbacks not honoured by the dialler, no rules for no-contact, no complaints log. | Configure supervisor barge/whisper, honour scheduled callbacks, document no-contact rules and complaint response. |
| Compliance and opt-out exposure | No opt-out honouring, suppression per-list not per-campaign, scripts without disclosures, no recording notice. | Customer to obtain qualified legal or compliance advice; SureTel enforces platform-level suppression where scoped. |
Missed inbound calls
Likely causes: IVR mis-routes, queue not sized to volume, unstaffed windows, callback not offered, phones ringing off-hook at reception.
What can help: Redesign IVR and queues, add callback offers, review roster vs forecast and confirm endpoints are healthy.
Long hold times / high abandon
Likely causes: Under-staffed peaks, one giant queue, no skills-based routing, no callback path, weak wrap-up discipline.
What can help: Split queues by skill, add callbacks, tighten wrap-up codes and forecast peaks against the real intraday curve.
Poor voice quality
Likely causes: Under-sized line, no QoS, Wi-Fi voice, poor cabling, weak headsets, packet loss upstream.
What can help: Size the line for concurrent calls, apply QoS or a voice VLAN, cable desks, replace cheap endpoints, add backup connectivity.
Low outbound contact rate
Likely causes: Weak list quality, wrong CLI, wrong dial mode for the campaign, no suppression, no callback honouring.
What can help: Customer to review list source and lawful basis; SureTel scopes CLI, dial-mode fit and suppression on the platform.
No queue or campaign visibility
Likely causes: Reporting turned off, no wallboards, metrics reviewed weekly not daily, no separation of inbound and outbound.
What can help: Enable platform reporting, add wallboards where scoped, split reporting per queue/campaign, review daily.
No call recordings or QA
Likely causes: Recording disabled, retention unclear, no access controls, no QA rubric or sampling cadence.
What can help: Enable recording with a documented policy and access controls; establish QA sampling — QA discipline is customer-owned.
No CRM integration
Likely causes: No click-to-call, no screen-pops, agents key call notes into two systems, dispositions not synced.
What can help: Scope click-to-call and screen-pops with the CRM; deeper syncs may require custom development.
Weak escalation and callbacks
Likely causes: No supervisor routing, callbacks not honoured by the dialler, no rules for no-contact, no complaints log.
What can help: Configure supervisor barge/whisper, honour scheduled callbacks, document no-contact rules and complaint response.
Compliance and opt-out exposure
Likely causes: No opt-out honouring, suppression per-list not per-campaign, scripts without disclosures, no recording notice.
What can help: Customer to obtain qualified legal or compliance advice; SureTel enforces platform-level suppression where scoped.
Problem categories
Five categories, one honest starting point
Sort every symptom into the right category before choosing a fix. The same complaint often lives in more than one — and rarely only in the dialler.
Technology
Symptoms: Missed calls, unstable dialler, IVR loops, dropped audio, no CRM integration.
What to check: Platform version, licence limits, integration scope, endpoint quality and PBX/dialler configuration.
Process
Symptoms: Weak escalation, no dispositions, chaotic callbacks, no QA feedback loop.
What to check: Documented call flows, disposition set, escalation matrix, QA rubric, wrap-up rules.
Staffing & QA
Symptoms: Long hold times, poor script adherence, coaching gaps, high attrition.
What to check: Roster vs forecast, agent skill matrix, coaching cadence, QA sampling — an HR/management layer, not a platform layer.
Data & lists
Symptoms: Low contact rate, wrong numbers, uneven outbound, opt-out complaints.
What to check: List source and lawful basis, suppression discipline, deduplication, disposition-driven cleanup — customer-owned.
Connectivity & voice
Symptoms: Choppy audio, one-way audio, calls that connect but do not ring, cross-site quality dips.
What to check: Line sizing for concurrent calls, jitter/latency/packet loss, QoS or voice VLAN, backup connectivity, UPS coverage.
Problem patterns by model
The same symptom means different things by model
Inbound, outbound and blended teams have different failure modes. Match the diagnosis to the model — see Inbound vs Outbound Call Centres for the operating detail.
Inbound-heavy desk
Support, orders and bookings. Symptoms cluster around queue design, IVR routing, agent load and abandon rate. Fixes live in Cloud PBX, queues, callbacks and staffing — see Call Queues Explained.
Outbound campaign floor
Sales, follow-up, collections. Symptoms cluster around list quality, dial mode, disposition discipline and compliance. Fixes live in Hosted VICIdial, list hygiene, campaign design and QA — a technology-and-process problem.
Blended team
Same agents handle inbound and outbound with priority rules. Symptoms cluster around inbound starvation, mixed reporting and blurred KPIs — separated wallboards and priority rules are the fix.
Technology fixes
The tools that actually apply to real symptoms
SureTel scopes the technology layer — platform, VoIP, connectivity, reporting and integrations — matched to the diagnosis, not sold as a package.
Hosted VICIdial
Campaigns, dial modes, dispositions and callbacks as first-class objects — chosen per campaign, never one giant setting.
Cloud PBX with queues & IVR
Queues, skills-based routing, callback offers and after-hours flows for inbound desks — depending on the platform and licence.
Business VoIP
Sized for concurrent calls with correct CLI, so audio stays clean and legitimate returns route back to the right team.
Reporting & wallboards
Live queue and campaign metrics on-floor and at supervisor desktops — where supported. Reporting supports decisions; it does not guarantee performance.
CRM integration
Standard click-to-call and screen-pops with common CRMs; deeper syncs and bespoke workflows may require custom development.
Connectivity & backup
Business fibre, wireless or licensed microwave as the primary line, LTE/5G backup with dual-WAN failover — feasibility per address.
Platform detail: Hosted VICIdial, Cloud PBX, VoIP and Business Connectivity.
Voice quality & network
Poor voice quality is almost always a network problem
Before blaming the platform, walk this checklist. Most voice-quality dips resolve inside the LAN, the endpoints or the primary line — not in the SIP path. See also VoIP Bandwidth & Internet Requirements and Why Is My Business Internet Slow?.
- Confirm the line is sized for concurrent voice calls, not for browsing.
- Measure jitter, latency and packet loss during peak hours, not only at night.
- Apply QoS or a dedicated voice VLAN so voice packets are prioritised inside the LAN.
- Cable the desks — Wi-Fi is not a voice medium for sustained call-centre use.
- Replace cheap headsets and confirm firmware on PoE switches and IP phones.
- Add LTE/5G backup with dual-WAN failover so a broken cable does not stop revenue.
- Protect router, firewall and PoE switches on a sized UPS.
- Confirm the SIP path — CLI, codecs and NAT — has not been changed since the last quality dip.
Network path — where quality lives
- Agent headset
- Softphone / IP desk phone
- PoE switch (voice VLAN)
- Router / firewall (QoS)
- Primary connectivity (fibre / wireless / microwave)
- LTE / 5G backup with dual-WAN failover
- SureTel VoIP / Cloud PBX / Hosted VICIdial
- Called party
Any step can be the fault. Diagnose end-to-end before changing the SIP config.
Reporting metrics
What each metric reveals — and what to watch out for
Reporting supports decisions but does not guarantee sales, answer rate or campaign outcomes. Features are available where supported by the platform; recording access is controlled and policy-aligned.
| Metric | What it reveals | Watch-outs |
|---|---|---|
| Abandoned calls | Calls where the caller hangs up before an agent answers — a signal that queues, callbacks or staffing are under-sized. | Definition varies by platform. Confirm the threshold (e.g. abandons after 5 seconds) so comparisons across days are honest. |
| Service level | The percentage of calls answered within a target time (e.g. 80% within 20 seconds). A leading indicator of caller experience. | Publishing service level as a customer promise is a business decision — no external service-level guarantees are implied here. |
| Average speed of answer | The mean time from queue entry to agent answer — a companion to service level, useful when queues run long. | Averages hide the tail. Look at 90th-percentile answer time alongside the mean before drawing conclusions. |
| Contact rate (outbound) | The percentage of dial attempts that reach a live person — a signal of list quality, CLI and dial-mode fit. | A low contact rate rarely means the dialler is broken; list hygiene and CLI usually explain more. |
| Dispositions | The outcome codes agents apply to each call (sale, no-answer, callback, opt-out). A picture of campaign health. | A short, disciplined disposition list beats a long, drifting one. Review disposition mix daily, not weekly. |
| Callback compliance | Whether promised callbacks are honoured on time by the dialler and the agent. | Missed callbacks corrode trust faster than any other metric on the floor. |
| Recording coverage | The share of qualifying calls recorded to a documented policy — access controlled to authorised users. | Recording without a documented retention and access policy is a compliance risk, not a compliance control. |
Abandoned calls
Reveals: Calls where the caller hangs up before an agent answers — a signal that queues, callbacks or staffing are under-sized.
Watch-outs: Definition varies by platform. Confirm the threshold (e.g. abandons after 5 seconds) so comparisons across days are honest.
Service level
Reveals: The percentage of calls answered within a target time (e.g. 80% within 20 seconds). A leading indicator of caller experience.
Watch-outs: Publishing service level as a customer promise is a business decision — no external service-level guarantees are implied here.
Average speed of answer
Reveals: The mean time from queue entry to agent answer — a companion to service level, useful when queues run long.
Watch-outs: Averages hide the tail. Look at 90th-percentile answer time alongside the mean before drawing conclusions.
Contact rate (outbound)
Reveals: The percentage of dial attempts that reach a live person — a signal of list quality, CLI and dial-mode fit.
Watch-outs: A low contact rate rarely means the dialler is broken; list hygiene and CLI usually explain more.
Dispositions
Reveals: The outcome codes agents apply to each call (sale, no-answer, callback, opt-out). A picture of campaign health.
Watch-outs: A short, disciplined disposition list beats a long, drifting one. Review disposition mix daily, not weekly.
Callback compliance
Reveals: Whether promised callbacks are honoured on time by the dialler and the agent.
Watch-outs: Missed callbacks corrode trust faster than any other metric on the floor.
Recording coverage
Reveals: The share of qualifying calls recorded to a documented policy — access controlled to authorised users.
Watch-outs: Recording without a documented retention and access policy is a compliance risk, not a compliance control.
Deeper reporting scope: Cloud PBX Analytics & Call Reporting.
Compliance & data-quality caution
Plan compliance and data quality before you blame the platform
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.
POPIA and direct-marketing rules cover lawful basis, consent, opt-outs, suppression, recording notices and retention. Recording access must be controlled and aligned to a documented policy. No bypass of consent, opt-out or suppression rules is implied or supported. SureTel does not make the customer POPIA-compliant, does not sign off compliance posture, and does not supply lead databases.
- Lawful basis for every outbound 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.
- Documented complaints and disputes process, with logged response times.
- Legal or compliance advice obtained on POPIA, direct marketing and scripts.
Use cases
Where these problems show up
Insurance sales & retentions
Outbound qualification and blended inbound for renewals — abandon rate and callback compliance under one wallboard.
Collections
Structured outbound with strict compliance, recording and suppression — process problems are usually list and script, not dialler.
Automotive service & sales
Inbound bookings and outbound follow-up — most quality dips come from Wi-Fi voice and cheap headsets, not the platform.
Medical scheme support
Inbound queues with skills-based routing and case notes — abandon rate is usually a staffing and IVR problem.
Pharmacy & healthcare bookings
Appointment reminders and inbound support — callback discipline matters more than dial mode.
Retail & e-commerce support
Order queries and returns — CRM screen-pops and clean dispositions cut agent hunting time.
Professional services desks
Small internal desks — the fix is IVR, callbacks and CRM click-to-call, not a full call-centre platform.
BPO for external brands
Multi-programme delivery with isolated reporting per client — mixed reporting hides real problems.
Startup call centre
10–25 seat launch — most early problems are connectivity, headsets and process, not the dialler.
Solution overview: Call Centre Communications.
What SureTel can help with
The technology layer — and where it stops
SureTel does not control third-party networks, customer staffing, scripts, HR or customer data. Standard CRM integrations are scoped as part of the solution; deeper syncs may require custom development. QueueMetrics is available where scoped; features apply where supported by the platform.
SureTel can assist with
- Cloud PBX, Hosted VICIdial or a mix, scoped to the operating model.
- Business VoIP with correct CLI and sized concurrent-call capacity.
- Business fibre, wireless or licensed microwave as primary connectivity; LTE/5G backup where feasible.
- Numbers, porting, endpoints, PoE switches and network readiness.
- Call flows, IVR, queues, callbacks, dispositions and campaign design at the platform layer.
- Standard CRM integrations (click-to-call, screen-pops) — deeper syncs may need custom development.
- Platform-level recording with access controls, aligned to the customer's documented policy.
- Reporting and wallboards where supported, plus QueueMetrics where scoped.
- Support inside the supplied solution scope, per the agreed SLA.
SureTel does not replace
- Staffing, HR decisions, coaching cadence and internal management.
- Legal or compliance advice — including POPIA, direct-marketing rules and lawful basis for outbound lists.
- Script writing, opening statements, disclosures and objection handling.
- List sourcing, data quality, deduplication and opt-out ownership.
- QA rubric ownership, sampling cadence and coaching outcomes.
- Control over third-party networks, customer premises equipment outside scope, or customer-owned CRMs.
- Sales results, collections outcomes, answer-rate or performance guarantees of any kind.
Common mistakes
The mistakes that keep call centres stuck
No performance guarantees are made or implied. These are the recurring patterns SureTel sees on scoping calls — not a checklist that replaces qualified advice.
Blaming the dialler by default
A new dialler is not a guaranteed fix. Most call-centre problems are process, data, staffing or connectivity problems in disguise.
Wi-Fi voice for agents
Wi-Fi is not a voice medium for sustained call-centre use. Cable the desks and stop chasing ghosts in the SIP path.
One giant queue for everything
One line for support, sales and retentions means the wrong agent picks up. Split by skill, not by hope.
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.
Reporting weekly, deciding weekly
A weekly report is a post-mortem. Contact rate, service level and disposition mix are daily decisions.
Two half-populated CRMs
One system of record, always. Two half-truths mean both are wrong by Friday.
Recording without a policy
Recording without retention, access and QA is storage, not a control. It also creates compliance exposure.
SureTel diagnostic path
From symptom to scope, in seven steps
Pricing depends on agent count, dialler requirements, VoIP usage, connectivity, integrations, reporting and support scope. SureTel puts a written scope on paper before any spend commitment — see Hosted VICIdial for platform commercial detail.
Discovery call
Describe the symptoms, seat count, model (inbound/outbound/blended) and current platform.
Diagnostic scoping
SureTel separates technology from process, data and connectivity — no assumptions about where the fault sits.
Platform review
Hosted VICIdial, Cloud PBX, VoIP and connectivity assessed against the actual problems, not a generic template.
Voice-network check
Line sizing, QoS, endpoints, backup connectivity and UPS reviewed as part of the same scope.
Compliance handover
Legal/compliance, script and list-quality decisions stay with the customer and their qualified advisers.
Written scope & quote
One written scope covering platform, VoIP, connectivity, endpoints and support — no scope hidden as a surprise.
Deploy, soft-launch, support
Provisioning, training and a small live pilot before ramp — then standard support inside the agreed scope.
Licensed South African ISP · ICASA licence 0009/CECS/AUG/09 · Operating since 2010 · Standard support Monday–Friday 08:00–17:00.
Related resources
Keep diagnosing 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.
- Inbound vs Outbound Call Centres
Purpose, tools, reporting and compliance for inbound, outbound and blended teams.
- Call Queues Explained
How queues, routing strategies, callbacks and overflow keep inbound service levels honest.
- Call Recording for Business
A practical guide to business call recording, retention, permissions and notices.
- Cloud PBX Analytics & Call Reporting
Call reporting, queue metrics, IVR analytics, wallboards and QueueMetrics scope.
- VoIP Bandwidth & Internet Requirements
How much bandwidth business VoIP really needs — concurrent calls, upload speed, latency, jitter, QoS and backup.
Call-centre problem FAQs
Frequently asked questions
What are the most common call centre problems?
The most common problems fall into five buckets — technology, process, staffing, data and connectivity. Symptoms include missed calls, long hold times, abandoned calls, poor voice quality, weak IVR, no queue visibility, poor reporting, no recordings, no QA, no CRM integration and weak escalation. The right fix depends on which bucket the symptom is actually in.
Will a new dialler fix our call-centre problems?
Not on its own. Many problems that look like the dialler are actually process, data, staffing or connectivity problems. A new dialler helps when the current platform is the real limitation — otherwise it is an expensive change that does not fix the root cause. Diagnose first, then decide.
Why is our call-centre voice quality poor?
Voice quality problems are almost always a network problem, not a platform problem. Common causes are under-sized lines, no QoS, Wi-Fi voice, poor cabling and cheap headsets. Measure jitter, latency and packet loss at peak, apply QoS or a voice VLAN, cable the desks, replace endpoints and add backup connectivity.
How do we reduce abandoned calls?
Abandoned calls are calls where the caller hangs up before an agent answers. Reduce them by splitting queues by skill, adding a callback path, forecasting peaks against the real intraday curve, tightening wrap-up codes and improving IVR routing. Definitions vary by platform, so confirm the abandon threshold before comparing days.
What reporting metrics matter most?
Inbound teams watch service level, average speed of answer, abandon rate and first-call resolution. Outbound teams watch contact rate, connect rate, disposition mix and callback compliance. Reporting supports decisions but does not guarantee sales, answer rate or campaign outcomes — features are available where supported by the platform.
Do we need Hosted VICIdial to fix outbound problems?
Sometimes. Hosted VICIdial suits sustained outbound campaigns with lists, dispositions and callbacks as first-class objects. For pure inbound desks Cloud PBX is often a simpler fit. SureTel will recommend the right platform for the operating model rather than default to VICIdial. See our Hosted VICIdial service page for the commercial detail.
How does POPIA affect our call-centre setup?
POPIA and related direct-marketing rules mainly affect outbound campaigns — lawful basis, consent, opt-outs, suppression, recordings and retention. Inbound recording, retention and data-handling also carry considerations. This resource flags planning considerations only; get qualified legal or compliance advice for your exact requirements. Consent, opt-out and suppression must never be bypassed.
How much does fixing call-centre problems cost?
Costs depend on agent count, dialler requirements, VoIP usage, connectivity, integrations, reporting and support scope. Some problems are configuration fixes; others need a platform, connectivity or endpoint change. SureTel scopes and quotes the technology layer in writing before any spend commitment.
What does SureTel actually help with, and what stays with us?
SureTel can help with the telephony, dialler, VoIP, connectivity, call-flow, reporting and support layer. The customer remains responsible for staffing, HR, legal compliance, data quality, scripts, sales process, QA discipline and internal management.
Next step
Diagnose the real problem with SureTel
Tell SureTel what the symptoms are — missed calls, poor voice quality, weak reporting, low contact rate — and SureTel will scope the technology layer: Hosted VICIdial, Cloud PBX, VoIP, connectivity and integrations. Legal, HR and compliance decisions stay with you and your qualified advisers.
Call-centre technology scoping only. Your details are handled according to SureTel’s Privacy Policy. Prefer to talk first? Contact SureTel.