What do telecom and internet customers contact you about?
Most subscriber contacts mean something stopped working, the bill changed, or the account needs to change. Agent resolves the first two once it can read network and billing data; anything that moves a number to a new SIM or carrier stays behind your own identity checks.
| Conversation type | Can Agent resolve it? | Hand off when | Data Agent needs |
|---|---|---|---|
| Outage check: "Is the internet down in my area?" | Yes, when your incident feed shows a known fault at the service address | No incident is listed, or the subscriber is on a priority register or a business SLA | Incident feed by node, exchange or cell site; service address |
| No connection, slow speeds or no signal | Partly: runs your scripted checks and a remote line or modem test | A technician visit is needed, or it is the third report of the fault | Remote diagnostics on the router, ONT or line; device model |
| "Why is my bill higher this month?" | Yes: itemizes proration, an expired promotion, roaming or overage | The subscriber disputes a charge or says they never agreed to it | Billing system, plan history, promotion end dates |
| Outage credit or goodwill credit | Partly: applies credits your policy allows, up to a set limit | The request is above the limit, or a credit was already given this cycle | Credit policy, confirmed outage duration |
| Plan change, upgrade or add-on | Yes, for changes the plan rules allow | An early termination fee or device balance applies, or it is a business account | Plan catalog, eligibility, contract end date |
| New device activation or eSIM setup | Yes: activation status, APN settings, eSIM install steps | Activation fails twice, or the line shows a fraud or security hold | Activation status, IMEI or EID, provisioning status |
| SIM replacement or SIM change | No. Points to your authenticated SIM change flow | Always, once identity checks have run in your own system | Account security status only |
| Port-in status or port-out questions | Partly: explains the steps and reports port-in status | A port has stalled, or the subscriber did not request a port-out | Porting request status, account lock status |
| Installation or technician appointment | Yes: books, reschedules and shares the arrival window | An appointment was missed, or the install needs a site survey | Field service scheduling system, serviceability |
| Cancellation request | Collects and routes; never cancels a line | Always, to retention or account services with the reason attached | Contract end date, device balance, equipment to return |
What does an AI procedure for "my internet is down" look like?
Connectivity contacts arrive in waves after a single fault. A support lead could write the procedure for Agent like this.
Example procedure: service down
- Identify the account from the logged-in app session, or ask for the account number plus the postcode or ZIP code of the service address. After two failed attempts, hand off.
- Check the incident feed for the service address. If an incident is open, give the cause in plain words and the estimated restoration time exactly as the feed shows it. Never invent or round a time.
- Offer text or email updates for that incident, sent to the contact details already on the account.
- If no incident is open, run the remote test on the router, ONT or line. Guide the subscriber through at most three steps: check the power and status lights, restart the equipment, try a wired device.
- If the remote test still fails, offer the next three technician slots from the field service system and book the one they choose.
- If the incident record shows the service has been down for more than 24 hours, apply the outage credit your policy sets, up to $10 per conversation, and say how it will appear on the next bill.
- Hand off at once on: a priority or medical-needs flag, a business line with an SLA, a third report of the same fault within 30 days, the words cancel, complaint, ombudsman, Ofcom, FCC or lawyer, or two negative messages in a row.
- Never change the plan, the SIM or the number during an outage conversation.
Example conversation
Subscriber: My broadband has been off since this morning and I work from home.
Agent: Sorry about that. I can see you are signed in to the app. There is a fault on the cabinet that serves your street, caused by a damaged cable. Engineers are on site and the current estimate for restoration is 6pm today.
Subscriber: Fine. Text me when it's back. This is the second time this month.
Agent: Done, you will get a text when the fault clears. Because this is a repeat fault, I have passed your account to our network support team so someone reviews the line once service is back.
The network support queue receives the conversation, the incident ID, the remote test result and the update subscription Agent created.
What guardrails does a telecom AI agent need?
Three hard limits: never move a number to a new SIM or carrier, never disclose call records to someone who has not passed your authentication, and never promise a repair time your systems do not show.
What Agent must never do
- Perform a SIM change or authorize a port-out. The FCC's 2023 order on SIM swap and port-out fraud requires US wireless providers to use secure authentication before a SIM change or port, notify customers of those requests and offer free account locks. Keep those steps in your own authenticated flow; Agent links to it and hands off.
- Read out call detail records or other customer proprietary network information to an unverified contact. The FCC explains the rules in its guide to protecting your telephone calling records.
- Give legal or financial advice, such as whether to break a contract or how to pay off a device balance. It states the figures on the account and routes the question.
- Issue credits above the limit you set, or any refund outside your written policy.
What triggers a handoff
- Keywords such as fraud, hacked, SIM swap, someone took my number, complaint, ombudsman, regulator or lawyer.
- Customer tier (business and priority-register accounts), negative sentiment or a repeat fault.
- Every cancellation, and any request Agent cannot verify.
Complaints have a clock in the UK
Ofcom has cut the wait before customers can take a complaint to an ADR scheme from eight weeks to six, for complaints raised on or after 8 April 2026. When a subscriber says they are complaining, Agent should tag it, record the date and route it, so the clock starts in your records and not just in theirs.
Data handling
Agent verifies the subscriber before showing account data, never asks for a full card number, PIN or password in chat, and acts only through revocable connector permissions. Aftersales offers a GDPR data processing agreement and hosts all data in the US; Scale adds SSO and SCIM. Monitors give security teams a record of every conversation. Aftersales does not make you compliant.
Which channels matter most for telecom customer service?
Pick channels that still work when your service does not. A subscriber with dead home broadband will message you from their phone, and one with no mobile signal will use Wi-Fi.
- In-app chat. The subscriber is already signed in, so Agent can skip most identity questions and read the right account.
- WhatsApp. Runs over Wi-Fi when the mobile network is down, and is the default messaging app in many markets. Agent answers in 31 languages.
- Phone. Older subscribers and anyone without a working connection will call. Growth and Scale include warm and cold transfers, recording consent and per-brand numbers, useful when you run a main brand and a value brand.
- SMS. Good for outage and appointment updates, but outbound texts need consent; see the FCC's guide to unwanted calls and texts.
- Social DMs. Outages surface here first.
All of them land in one Inbox queue, so a subscriber who starts on social and moves to chat keeps one thread.
Which telecom systems should the AI agent connect to?
Connect the incident feed and billing first; together they cover outages, bill questions and credits. Each connector gets explicit, revocable permissions, so provisioning can stay read-only while the field service connector books appointments.
| System | What Agent reads or does | How it connects |
|---|---|---|
| Billing and CRM (BSS) | Balances, bill line items, plan, promotions, contract end date; applies capped credits | Aftersales API or webhooks |
| Network monitoring and incident feed | Open incidents by node, exchange or cell site; estimated restoration time | Aftersales API or webhooks |
| Device management and remote diagnostics | Line and router test results; remote restart | Aftersales API or webhooks |
| Field service scheduling | Available slots; books and reschedules installs and repairs | Aftersales API or webhooks |
| Provisioning, SIM and porting systems | Read-only: activation, eSIM and port-in status, account lock flag | Aftersales API or webhooks |
| Salesforce, Zendesk or Freshdesk | Existing customer and case records; Agent can run inside them | Named integrations |
| Slack and Jira | Post a new fault pattern to the network channel or open a Jira issue from a workflow | Named integrations |
| Stripe or Shopify | Only if you take top-ups through Stripe or sell devices and accessories in a Shopify store | Named integrations |
Stacks vary widely, so confirm specific connectors on a call. Keep plan terms, roaming rates and troubleshooting steps in Knowledge, and make sure Agent answers price and speed questions from the same figures as your broadband labels if you sell in the US.
What does AI customer service cost for a telecom provider?
A regional ISP or mobile virtual network operator handling 9,000 conversations a month would pay about $5,480 a month at list prices, roughly $0.61 per conversation, on these assumptions:
- 15 support agents on Growth, billed annually.
- Agent resolves 45% of conversations, below the 71% median Aftersales customers reach after 90 days, because SIM changes, ports, disputes and cancellations go to people.
- Copilot for every agent, and network operations engineers and field dispatchers added as free Lite seats so they can comment on threads.
| Line item | Calculation | Monthly cost |
|---|---|---|
| 15 agent seats on Growth | 15 × $69 | $1,035 |
| Agent resolutions | 4,050 × $0.99 | $4,009.50 |
| Copilot for 15 agents | 15 × $29 | $435 |
| Network and field staff as Lite seats | Up to 20 included on Growth | $0 |
| Total per month | $5,479.50 |
A resolution is counted once per conversation, however many questions it contained, and conversations Agent cannot help with are free. That matters in an outage: a subscriber who asks about the fault and then a bill in one chat costs one resolution. Providers that need SSO would choose Scale at $109 per seat. Teams staying in Salesforce Service Cloud, Zendesk or Freshdesk can run Agent on its own at $0.99 per resolution with a minimum monthly commitment and no seats. See pricing.
How do you roll out a telecom AI agent in 30 days?
Start with outages and bill questions on one brand or region, then widen.
- Week 1. Tag three months of conversations by intent; outages, bill increases and appointment changes usually lead. Connect the incident feed and billing read-only and agree the handoff list with your fraud team.
- Week 2. Write procedures or import macros, then replay past outage days and check every restoration time Agent quotes.
- Week 3. Go live in the app and on web chat for one region, overnight first. Run Monitors on every conversation and review each SIM or porting handoff.
- Week 4. Turn on capped outage credits, appointment booking and WhatsApp. Report resolution rate, handoff reasons and repeat contacts to the network and billing leads, using the definitions in our resolution rate guide.