How AI support changes an ISP's cost per ticket

Read a week of support messages at a home fibre ISP and you will see the same few questions again and again:

• "My internet is not working."
• "I have paid but I'm still disconnected."
• "What is my Wi-Fi password?"
• "When does my package expire?"

None of these need judgement to answer. They need someone to look things up.

Where the cost actually is

To answer "my internet is not working", a support agent has to:

1. find the customer's account;
2. check whether the subscription has expired;
3. check whether the PPPoE session is up;
4. check the ONU's optical level;
5. check whether there is a known outage on that OLT port;
6. then reply.

It takes minutes, and while the agent is looking, three more messages arrive.

The cost per ticket is mostly the time spent gathering facts the system already holds.

What changes when the system does the looking

SaidaAI sits inside SaidaLink, so it reads the same records an agent would. When a subscriber writes "no internet" on WhatsApp, it:

• finds the account;
• checks the balance and the due date;
• runs a connection diagnostic.

Then it replies with the actual cause. If the subscription has lapsed, it sends the mobile-money payment prompt in the same chat. If the line is at fault, it opens a ticket with the results attached. It does the same over SMS, web chat and voice, in more than 15 languages, including Swahili. {/* source: saidalink.tech/platform/saida-ai , /solutions/mobile-money-isp-billing */}

The person in support starts from the evidence, not from a blank screen.

What it does not do

It does not pretend to be a person. When a conversation needs judgement, it hands over to someone on the team with the full thread. It does not answer one operator's customer using another operator's data.

And it does not replace the support team. It removes the repetitive part of the job, so the team has time for the problems that do need judgement: the business customer whose link is flapping, or the estate where a whole splitter went down.

Measuring it

The honest measure is not "messages handled by AI". It is cost per resolved ticket, and time to resolution. Every SaidaAI request is logged against the tenant with the tokens it used, so an operator can put the two side by side.

On fibre networks the same idea works in the NOC. SaidaAI correlates alarms so that one fault does not turn into fifty tickets, and drafts the outage notice for a person to approve. {/* source: litspan.com/news/litspan-partners-saidalink-ai */}

The bigger point

Support is one of the largest costs for a small ISP after bandwidth and field work. If the cost per ticket falls, the operator can afford to serve customers who pay less, and that is how connectivity gets cheaper.