AI Customer Service Chatbot for an Internet Provider: London 2026

The verdict in three sentences

A London broadband provider with 60,000 subscribers and 25,000 contacts a month spends between 100,000 and 175,000 GBP a month on human-handled support. An AI chatbot connected to the CRM, network monitoring and billing can resolve 55 to 65 % of repetitive requests, roughly 7,500 to 9,000 contacts a month, for 1,500 to 6,000 GBP of model API costs. It works when it gives real, personalised answers (outage status on the customer's street, balance, next bill date) and fails when it is just a FAQ in disguise.

Where the 25,000 monthly contacts come from

For an alternative network or regional ISP in London, contacts cluster around a handful of predictable reasons. A fibre cut in Hackney or a cabinet fault in Croydon can trigger hundreds of calls within an hour. Billing, direct debit failures and plan changes form the other big block. Only a minority need genuine technical diagnosis or an engineer visit.

The first three rows make up the 55 % of repetitive demand. They are what justifies the investment.

Architecture and costs in 2026

A useful ISP chatbot rests on three building blocks. Channels first: web chat and the customer app, plus WhatsApp and SMS for customers who prefer messaging. The engine next: a language model that handles informal English, typos and transcribed voice notes. Integrations last, and without them nothing works: identifying the subscriber from their account or mobile number, reading the balance, checking outages by postcode and creating a ticket in the CRM.

An ISP connecting CRM, billing, network monitoring and payment logs usually lands in the complex band. A scope limited to bills and area outages can stay at medium complexity. See our approach to AI projects.

Rules that prevent failure

Rule one: handover to a human agent must be immediate when the customer asks or after two failed attempts, with the full conversation passed on. Rule two: the bot never promises a fix time it does not know; it reads the status from network monitoring or says an engineer has been dispatched. Rule three: compliance. Ofcom's General Conditions require clear complaint handling and access to alternative dispute resolution after eight weeks, so the bot must recognise a complaint and log it as such. UK GDPR applies to every transcript: mask account data in logs and set a retention period.

Finally, track the right metric: resolution without repeat contact within 72 hours, not the raw number of conversations handled by the bot.

Mini case study

Daniel, head of customer service at a 60,000-subscriber ISP in London, handles 25,000 contacts a month at an average 5 GBP per contact, or 125,000 GBP a month. The chatbot, live on web chat, the app and WhatsApp, resolves 60 % of the 13,750 repetitive requests: 8,250 contacts that never reach an agent.

Gross saving: 8,250 contacts at 5 GBP, or 41,250 GBP a month. Running costs: 4,000 GBP of API and 2,000 GBP of messaging, or 6,000 GBP, plus Premium maintenance at 183 EUR. Net gain: about 35,000 GBP a month. A complex build in the 10,670 to 22,870+ EUR band pays back within the first month. Daniel moves part of his team to complaints and retention, where churn costs far more than a call.

FAQ

Can the chatbot handle voice notes?

Yes, with automatic transcription upstream. Voice notes are a smaller share in London than in some markets, typically 5 to 10 % of messaging traffic, but handling them avoids dead ends.

What happens during a major outage?

The bot reads the declared incident from monitoring and answers hundreds of affected subscribers in seconds. This is where it saves the most, sometimes 2,000 calls in a single day.

Does Ofcom allow automated complaint handling?

Yes, as long as complaints are recognised, recorded and can escalate to a human, and the customer is told about ADR after eight weeks. Around 12 % of contacts are complaints and should be routed accordingly.

How long does deployment take?

Allow 8 to 12 weeks for a first scope covering bills and outages, then 4 to 6 weeks per additional batch of contact reasons.

Must data stay in the UK?

UK GDPR does not strictly require UK hosting, but transfers need adequate safeguards. The safest design keeps subscriber data in your systems and sends the model only what each answer needs.

Let's scope your project. We define with you which contact reasons to automate, which systems to connect and a first release delivered in weeks. Detailed quote within 48 h. WhatsApp +221 77 596 93 33.