Where does ISP support cost actually come from?
Support cost is mostly people time spent on contacts that repeat. Every operator has a short list of reasons subscribers call, text or email, and that list barely changes from month to month. The expensive part is not the rare, hard case. It is the same simple case handled hundreds of times by your most experienced staff.
Three things push the cost up further: contacts that arrive in spikes during an outage, contacts that need a second call because the first one didn’t fix anything, and contacts where the agent spends the first minutes looking up the account across several systems before any help starts.
Which contacts can AI resolve end to end?
Start with contacts that are frequent, well defined and resolved by a known action on the account or the network. These are the ones where an AI agent can finish the job, not just answer a question.
| Contact type | What resolution looks like | What the agent needs |
|---|---|---|
| Outage and slow-speed reports | Confirm a known outage in the area, or run a check and a remote CPE restart | Service location, outage status, device actions |
| Balance and invoice questions | Explain the charge line by line, send the operator’s payment link | Invoice detail, payment history |
| Password and portal resets | Verify identity, trigger the reset, confirm it worked | Authentication, portal account |
| Plan changes | Explain options, apply the change, confirm the new price | Plan catalog, authorization rules |
| Appointment changes | Reschedule an install or repair window | Technician calendar, visit status |
Leave out cases that need judgment or negotiation beyond clear rules at first: complaints about a previous interaction, credits above a set amount, legal or regulatory requests. Those go to a person, with the context already gathered.
How should an AI agent authenticate and escalate?
Authenticate before any account action. Reading public outage status needs no verification; changing a plan or discussing a balance does. Use the same verification rules your human team follows, and let the agent refuse politely when a subscriber can’t pass them.
Escalate with context, not with a transfer. When a case needs a person, the handoff should carry who the subscriber is, what they asked, what the agent already checked and what it tried. A handoff that makes the subscriber repeat themselves costs you the time you just saved, and the goodwill with it.
A good test for escalation: could the person who picks up the case act on it in the first thirty seconds, without asking the subscriber anything they already said?
Which metrics show real savings?
Measure outcomes for the subscriber, not activity for the bot. These definitions keep the numbers honest.
- Resolution rate
- Contacts closed by the AI agent with the issue actually fixed, divided by contacts it handled. The number that drives cost.
- Containment rate
- Contacts that never reached a human. Useful, but it rises when subscribers give up, so never read it alone.
- Average handling time (AHT)
- Time a human spends per contact, including wrap-up. Good AI handoffs lower it for the cases people still take.
- First-contact resolution (FCR)
- Issues fixed without a repeat contact within a set window, such as seven days. Catches fixes that didn’t hold.
- Customer satisfaction (CSAT)
- Post-contact rating. Compare AI-handled and human-handled contacts of the same type.
| ID | Event | Detail | Status | Value |
|---|---|---|---|---|
| #48201 | Auto-suspend | Past due · 4 days · policy DUNN-04 | Suspended | −1 service |
| #48202 | Auto-reconnect | ACH payment cleared · $74.00 | Reconnected | 2 min |
| #48203 | Cycle invoicing | Taxes, USF and E911 applied · emailed | Issued | 2,418 docs |
| #48204 | Payment reconciled | Paid via reminder link · matched to invoice | Cleared | +$74.00 |
What goes wrong with support automation?
- Deflection dressed up as resolution. Pointing subscribers to a help article and counting the conversation as handled. The call comes back, usually angrier.
- No access to the account. An agent that can only answer questions can’t fix anything. Resolution needs read and write access to the subscriber record, within limits.
- No clean exit. Subscribers who can’t reach a person when they need one stop trusting every channel you offer.
- Measuring the wrong thing. Containment without FCR hides repeat contacts; cost per contact without CSAT hides damage to the base.
Where does Inerxia fit?
Inerxia’s Tier 1 support agent takes inbound calls, chats, texts and emails, authenticates the subscriber before any account action, and resolves outages, balance questions, password resets and plan changes end to end, including remote equipment actions such as CPE restarts. When a person is needed, it escalates with full context, and every action is kept in an audit trail.
Inerxia publishes these figures for its support agent: 92% of Tier 1 tickets resolved by AI, −54% average handling time and +31 NPS points over six months. Agents start at $500 each; see pricing for how channels and capabilities are added.