AI agents in telecom

Telecom customer service is dense with requests agents could settle: port my number, change my plan, cancel, explain this bill, stop this charge. Carriers already exchange a lot of this among themselves in standard formats, and both countries’ regulators set specific rules for identity checks and switching. Those rules make telecom a good test of whether an agent exchange can prove who the customer is without falling back to a phone call.

Where agents meet today

Carrier to carrier

Number porting is already an automated exchange between carriers. In the US, carriers must complete a simple wireline or intermodal port within one business day unless the new provider or customer asks for longer (47 CFR 52.35). In Canada, the CRTC set the interval for a simple wireless-to-wireless port at 2.5 business hours in Telecom Decision 2005-72.

For order and service systems, TM Forum publishes a set of REST-based Open APIs developed by its members, such as Product Ordering, Trouble Ticket and Customer Management.

Customer to carrier

Customers reach carriers through apps, websites, stores and phone lines. Assistants that place phone calls for people already exist, as When two voice agents meet on a phone call describes. A customer’s agent that could reach the carrier’s own agent directly would skip the voice layer and send the account number, plan code and request as data. The same holds for chat: an agent typing into a carrier’s chat widget is software imitating a person in order to reach other software, and every field it needs has to be parsed back out of prose.

Why porting is the hard case

A port-out moves a phone number, and with it the one-time codes many services send to that number. That is why regulators treat port-outs and SIM changes as fraud targets. Illustrative: a customer’s agent asks the losing carrier’s agent for a port-out PIN. The carrier’s agent refuses to return it to the agent directly and instead sends a prompt to the account holder in the carrier’s own app, where the customer approves. The PIN goes to the winning carrier through the normal porting process. The agent exchange speeds up the request without becoming a way around the carrier’s authentication. The same pattern fits SIM changes and any request that would move control of the account.

Top use cases

Use case	Who talks to whom	Notes
Number porting	Losing and winning carrier agents, and the customer’s agent	Port-out authorization and fraud checks
Bill negotiation	Customer agent and carrier agent	Plan changes and retention offers
Subscription cancellation	Customer agent and carrier agent	Cancelling plans and add-ons
Billing disputes	Customer agent and carrier agent	Roaming charges, promotions that ended
Device warranty	Device or customer agent and carrier or manufacturer agent	Repairs and replacements

Regulatory considerations

Checked on 26 September 2026 against the FCC, eCFR and CRTC sites. This is not legal advice.

United States (FCC)

• Customer authentication (CPNI). Carriers must properly authenticate a customer before disclosing customer proprietary network information on a customer-initiated call, online, or in a store. Call detail information may be disclosed on a customer-initiated call only if the customer gives a password that wasn’t prompted by asking for readily available biographical or account information; otherwise the carrier may only send it to the address of record or call the number of record. A customer’s agent asking for call records runs into this rule directly.
• SIM swap and port-out fraud. The FCC adopted rules in November 2023 requiring wireless carriers to use secure authentication before SIM changes and port-outs. In Order DA 24-649 of 5 July 2024 it waived compliance until the Federal Register announces that OMB has approved the related information collections. We found no such notice as of 26 September 2026.
• AI voices on calls. In February 2024 the FCC ruled that calls made with AI-generated voices are “artificial” under the Telephone Consumer Protection Act.
• Caller ID authentication. STIR/SHAKEN authenticates calling numbers on IP networks; the FCC describes it as a defence against spoofed robocalls.

Canada (CRTC)

• Self-service cancellation and changes. Following Telecommunications Act amendments in force since 30 October 2025, CRTC 2026-78 (24 April 2026) requires providers to let customers modify and cancel Internet and mobile plans through a self-service mechanism, such as an app, a website or email, without a live representative, and to send written confirmation of every self-service action. It takes effect on 26 April 2027.
• Notice before promotions end. CRTC 2026-67 (13 April 2026) amends the Wireless Code and Internet Code so that providers must notify the account holder 90 calendar days before a time-limited discount of more than three months expires during the commitment period. It takes effect on 13 April 2027.
• Automated calls under review. CRTC 2026-132 (11 June 2026) opened a review of the Unsolicited Telecommunications Rules. It asks whether the current definition of an automatic dialing-announcing device captures technologies that use synthesized or AI-generated voices. Interventions were due 27 July 2026 and replies 11 August 2026.
• STIR/SHAKEN. CRTC Decision 2021-123 required providers to implement STIR/SHAKEN for IP-based voice calls from 30 November 2021.
• Complaints. The Commission for Complaints for Telecom-television Services (CCTS) resolves consumer complaints about telecom and TV providers.
• Privacy. Telecom carriers are federally regulated, and the OPC notes PIPEDA applies to federal works, undertakings or businesses in every province. Bill C-36, introduced on 15 June 2026 to replace Part 1 of PIPEDA, is at second reading.

Where to start

1. Start with account questions that don’t expose CPNI. Plan details, device payment balance and order status are simpler first tasks than call records.
2. Design the authentication step first. Decide how a customer’s agent proves the customer approved this request, and make it at least as strong as what CPNI rules and your SIM-swap controls require for a phone call.
3. Treat port-outs and SIM changes as high risk. Require the account holder’s approval through a channel the carrier controls, and log it.
4. Confirm every change in writing. CRTC 2026-78 will require written confirmation for self-service actions in Canada from April 2027, and an agent-initiated change needs the same record.
5. Publish an Agent Card. A customer’s agent that can find your endpoint has less reason to phone. The Agent Card validator checks yours against the A2A specification.