Telecom,
built for the volume a network receives.
Telecom support is high volume, highly repetitive, and occasionally all at once — an outage turns a normal Tuesday into ten thousand simultaneous calls about the same thing.
The calls that cost you something.
Not a list of features you do not have — the four situations that already happen every week.
Volume is the problem before anything else is
Ordinary days are large; the day something breaks is a different order of magnitude, and it is the day the queue matters most.
Tariffs, bundles and roaming rates are a matrix nobody recites correctly
The right answer depends on the plan, the country, the day and whatever promotion is running, and staff get it wrong because it is genuinely hard.
During an outage everybody rings about the same thing
Thousands of identical calls, each one taking an agent away from the ones that are not about the outage.
Billing disputes need a record, and phone calls do not leave one
A disputed charge six weeks later comes down to who said what, and nobody has it.
One answer per problem, in the same order.
Everything below is something the product does today, on the call, without anybody being asked to change how they work.
Volume is the problem before anything else is
Concurrency is a capacity setting, not a rota
The platform is built for thousands of simultaneous calls and is measured against that. When a spike arrives, it is answered rather than queued.
Tariffs, bundles and roaming rates are a matrix nobody recites correctly
It reads the matrix rather than remembering it
Rates are real rows looked up on the exact combination that was asked about. There is no nearly-right answer, and updating a promotion is updating a row.
During an outage everybody rings about the same thing
It tells them what is known, and logs the ones that are different
Put the current status in the knowledge and every caller hears it consistently. The calls that are *not* about the outage still reach a person, because the agent can tell the difference.
Billing disputes need a record, and phone calls do not leave one
Every call leaves a transcript and a ticket
The dispute arrives at the billing queue with the conversation attached, the caller identified and the summary already written.
What one of these actually sounds like.
A roaming rate read off the exact tariff row, and a billing dispute that becomes a ticket in the right queue.
- Caller
راح أسافر لتركيا. شكد يكلف الإنترنت هناك؟
I am travelling to Turkey. How much is data there?
- Kasper
على باقتك الحالية، التجوال بتركيا ألفين دينار للميغابايت المية. أو تگدر تشتري باقة أسبوع بخمسة وعشرين ألف تشمل خمس گيگا.
On your current plan, roaming in Turkey is two thousand dinars per hundred megabytes. Or you can buy a weekly bundle at twenty-five thousand that includes five gigabytes.
- Caller
زين. بس عندي مشكلة — انحسب علي مبلغ الشهر الماضي ما أعرف شنو.
Good. But I have a problem — I was charged something last month I do not recognise.
- Kasper
راح أفتح لك طلب لقسم الفوترة بالتفاصيل، ويتواصلون وياك خلال يوم عمل. رقم الطلب راح يوصلك برسالة.
I am opening a case with the billing team with the details, and they will contact you within one business day. The reference will come to you by message.
The four numbers this comes down to.
Computed from the conversations themselves, on every agent, queue, channel and hour of the day.
- Containment rate
- At telecom volumes, a few points here is an entire shift.
- Service level
- What happens to the answer rate on the day something breaks.
- Cost per conversation
- The only way to compare the cost of an outage against the cost of a normal Tuesday.
- Transfer rate
- Which categories genuinely need a person, so staffing follows the work.
Hear it answer a telecom call.
Bring the question your team dreads. Fifteen minutes is enough to know whether this belongs on your phone.