Clearing customer problems within NCC benchmark times

How fast the NCC expects a Nigerian operator to clear customer problems, when quarterly QoS reports are due, and how support tickets can track it.

By Achekam · 11 October 2026 · 5 min read · For Telecoms businesses in Nigeria

Launching soon. The Industry CRM add-on described in this article is launching soon. This article describes it as it will work at launch.

For a Nigerian operator, a customer's problem has a clock on it from the moment it is reported. The Nigerian Communications Commission does not only ask whether problems get fixed; it sets benchmarks for how many must be cleared on the same day, how many within two days, and by when every last one must be closed. It also expects the customer care line itself to work: every call answered, nobody left listening to an engaged tone.

Meeting those benchmarks is partly a network job and partly an organisational one. This article sets out the NCC's clearance and customer care benchmarks, the quarterly reporting timetable, how the NCC defines a dropped call, and how the Telecom pack in Achekam's Industry CRM add-on helps a support team keep each problem on its clock. The figures are those the NCC publishes at the time of writing.

The NCC's clearance benchmarks

The NCC says it is empowered to set minimum quality of service standards for telecoms operators, covering technical measures such as call completion rates and commercial measures such as customer care access and billing integrity. The NCC's Quality of Service page lists the benchmarks in full and is the page to check for changes.

Among the commercial benchmarks for mobile operators is the speed at which customer problems are cleared:

Read the table from the top. Most problems must be cleared the day they are reported, so the support process has to be designed for same-day resolution, not for a queue that is worked through over the week. The second and third rows deal with the harder cases, and the last row leaves no room for problems that simply stay open.

Customer care centres: every call answered

The NCC's customer care benchmarks are just as specific. It requires operators' customer care centres to achieve a call completion rate of 100%: every call must be answered by a person or a machine, and the line must never be busy. While a customer waits in the queue, a repeated announcement must play at every two-minute interval, and the NCC's benchmark for time in the queue at a customer interface point is 10 minutes.

In practice that means sizing the care centre and its phone system for peaks, not averages, and making sure the queue announcements are configured on every line, including any overflow or after-hours service.

Quarterly reports and when they are due

The NCC requires every mobile operator to report quality of service quarterly. Each quarter's report must reach the NCC's Abuja office by the 15th of the first month of the next quarter, in hard copy and in editable electronic form. It is made up of a national report, regional reports, and urban reports for Lagos, Aba, Abuja, Kano, Benin City, Maiduguri and Port-Harcourt.

Working backwards from that date gives a practical timetable:

1. Quarter end: freeze the quarter's support records and network statistics.
2. First week of the new quarter: compile clearance figures nationally, by region and for each of the named cities.
3. Second week: review, sign off and prepare both the hard copy and the editable file.
4. Before the 15th: deliver to the Abuja office, and keep proof of delivery.

The city-level split is the step that catches teams out. If your support records do not capture where each customer is, you cannot produce the urban reports from them, so decide where each customer's location will be recorded before the quarter starts.

How the NCC defines a dropped call

The quarterly reports also carry technical measures. The NCC defines the dropped call rate as the number of dropped calls divided by the total number of call attempts, a dropped call being one terminated prematurely before either party releases it normally. That figure comes from network data, not from support records, but a customer who complains about calls cutting off is describing the same event. Linking those complaints to network findings helps engineering see where subscribers feel the problem most.

Keeping each problem on its clock with support tickets

The Telecommunications pack in Achekam's Industry CRM is built for internet, voice and mobile providers and resellers. It keeps Service subscriptions, support Tickets and Installation jobs, so a customer's problem is logged against the service it concerns.

Each ticket follows a set path: the pack acknowledges it, runs first-line checks, and escalates by tier against an SLA due date set on the ticket. To mirror the NCC's benchmarks, set the due date for ordinary problems to the same day they are reported, and arrange the escalation tiers so that anything still open moves up before the two-day and three-day marks.

Follow-up work often involves several people: a field technician, a network engineer, a billing clerk. In the Industry CRM, tasks can have subtasks up to three levels deep, and a workflow creates its tasks stage by stage, so each step of a stubborn problem has an owner and a date.

Seeing what is slipping

The home-page counts come from records, tasks or the ledger, never typed in by hand, and they include overdue tasks and tasks due today. A support manager who opens the home page each morning sees at once how many problems are past their due date, which is the number that threatens the same-day benchmark.

One limit to keep in mind: the pack provisions nothing on a network, is connected to no network, and statuses are recorded by staff. Network measures such as the dropped call rate stay in your network systems; the tickets record what customers reported and what the business did about it. Agree before the quarter starts how ticket records will be counted for the clearance figures, so the report draws on the same rules every time.

Support tickets with SLA due dates explains the ticket workflow in more detail, and the NCC's billing integrity benchmarks covers the complaints that start with a wrong bill.

This quarter

Decide where each problem's location and reporting time will be recorded, set same-day due dates as the default, and put the 15th of next quarter's first month in the diary now.

General guidance only, not advice on your own circumstances. Tax and payroll rules change: check the current position with the authority or your adviser.