Repliant for Telco

Every port-out, every outage, every bill.

Repliant runs voice and messaging across the whole care surface — IVR replacement on Genesys, outbound on every approved SMS aggregator, in-app on your MyAccount SDK — connected natively to Amdocs, Netcracker, Salesforce Communications Cloud, ServiceNow TSM, and the OSS your network team won't let you replace. Built for FCC CPNI, OFCOM "Fair Treatment", TRAI MNP, GDPR, and the SIM-swap guidance your CISO reads on Mondays.

NMS · CARE FABRIC · LIVE connected
VOICE SMS IVR APP SOCIAL PSTN · 8447 A2P 10DLC Genesys CXi MyAccount SDK WhatsApp · X Repliant care.fabric 23 lang · 99.99% Amdocs · BSS Netcracker · OSS SF Comms Cloud ServiceNow FSM Cisco NSO → DSP-RTN-SAV · 41% → DSP-NET-RES · 28% disposition codes · written back
cpni · scoped mnp · 1.2h SLA e911 · pass-through audit · 7-y retained
↑ care fabric · 5 channels in, 5 systems out, one auditable thread

The industry reality

Care is the surface your churn rate actually lives on.

A customer asks to port out at 14:02. Your IVR routes them to a save queue. By 14:18 they are still on hold. Under TRAI MNP rules, the port has to complete within seven working days. Under OFCOM "Fair Treatment," your save attempt must not slow them down. The customer hangs up, opens the competitor's app, and is gone before your retention team has dialed back. Your churn dashboard updates on Tuesday.

Across a mobile book of 14M subscribers, this happens roughly 9,000 times a month. The save rate has not meaningfully moved in three quarters. Your contact center is operating across four BPOs, eleven languages, and one twenty-year-old IVR built when the iPhone was a rumor. The escalation queue is 22 hours deep on weekday afternoons.

Then there's the outage weekend. The radio access network sneezes in Marseille at 04:11. By 07:30 your social-care team is reading variations of the same complaint from sixteen thousand customers and improvising apologies they will see quoted on Reddit by lunchtime. By Monday, your CCO is in a room with the regulator.

The economics are unkind in the other direction too. Your team's highest-margin conversations — the plan-upgrade outbound, the 5G migration, the bill-shock pre-empt — are the ones nobody has time to make. The dialer is choked with care; the upsell motion has been "next quarter" for four quarters.

Repliant is the agent layer that absorbs the care surface — every port-out, every outage, every bill — without missing an MNP clock, leaking CPNI, or letting a SIM-swap attempt sneak through unverified.

What Repliant handles for telco.

Five named workflows. Each one measured against churn, save rate, MTTR-to-customer, or care cost — the lines your operations committee reads each Monday.

WORKFLOW 01 · upsell.plan_outbound

Plan-upgrade outbound, finally at volume.

The outbound motion your dialer has had on the roadmap for four quarters. Repliant calls customers approaching the data cap, the contract renewal, or 5G eligibility — under TRAI DND / TCPA / OFCOM consent state for that customer — quotes the right plan against Amdocs charging, captures verbal authorization with the right disclosures read in language, and writes the plan change back to BSS. The agent never quotes a rate it has not been given.

Outcome · + €11.40 ARPU lift on contacted cohort · 6-month rolling

Outbound cohort · last 90 days · n = 184,402

ELIGIBLE · CONSENT OK CONTACTED CONVERSED UPGRADED · BSS WRITE 184,402 163,914 77,228 31,840

WORKFLOW 02 · network.triage_truck_roll

Network-issue triage with field-tech handoff.

The agent reads the NMS event feed in the same turn it speaks. It narrows the customer's issue to one of four — known outage, device, line, configuration — runs the appropriate remote test, and either resolves or schedules a truck roll through ServiceNow FSM with the diagnosis attached. The technician arrives with the right part on the van. Truck rolls fall when the diagnosis is correct, not when calls are deflected.

Outcome · −34% unnecessary truck rolls · 12-month, ISP cohort

Triage tree · "no service" inbound

NMS lookup classify known outage device · reset line · self-test truck roll · FSM credit · auto resolved resolved scheduled

WORKFLOW 03 · portout.retain_with_mnp

Port-out retention, under MNP rules.

When a customer requests a port-out, Repliant reads their account, computes the right save offer against Amdocs/Netcracker pricing, runs exactly one save attempt — never more — and honors the port if they say no. The MNP clock is not slowed. The "easier to leave" obligation under OFCOM and the seven-day TRAI TAT are enforced at the workflow level, not at the BPO supervisor's discretion. PAC / UPC codes are issued without friction when the customer asks.

Outcome · + 19% save rate · vs. human-only baseline · EU mobile operator cohort

Port-out save flow · MNP-compliant · n = 12,402

PORT REQUESTED ONE SAVE OFFER SAVED · STAYED 12,402 12,402 · single attempt 2,346 · 18.9% PAC / UPC issued without friction when customer declines · MNP clock unbroken

WORKFLOW 04 · billing.preempt_shock

Bill-shock proactive outreach.

The complaint your CCO sees on Twitter and your regulator sees in a quarterly letter. Repliant watches the Ericsson Charging System (or your charging platform) for anomalous usage — roaming surge, premium SMS, unexpected data — and reaches out before the bill closes. Offers an add-on, a cap, or a billing-plan change. Under OFCOM's mid-contract bill cap and Reg E equivalents in other jurisdictions, this is increasingly not optional.

Outcome · −63% bill-shock complaints · post-deployment baseline

Per-customer usage · anomaly detected, outreach sent at day 8

GB / DAY D1D14D28 · BILL CLOSE PLAN CAP → Outreach sent · day 8 offer · 5GB add-on · cap on

WORKFLOW 05 · sim.verify_swap_request

SIM-swap verification with step-up auth.

The attack surface your CISO worries about more than any other. Repliant runs the SIM-swap callback with voice-biometric verification, KBA against the customer of record (never invented), step-up to the registered email, and a hold on activation when the risk signal crosses the CTIA / FCC threshold. Eligible activations write through to Thales / IDEMIA provisioning. Anything that smells like a coached customer routes to a fraud analyst with the call still live.

Outcome · 0 confirmed SIM-swap fraud cases · 14-month rolling window · single operator

Verification timeline · request → activation or hold

0 s 45 s 95 s 160 s 200 s Swap requested · in-app Callback · voice bio KBA · step-up email Risk score · CTIA threshold Provisioned · Thales prior baseline · 12 min mean · branch-assisted repliant · 3.3 min mean

Built to live inside the BSS, OSS, and NMS your team won't let you replace.

Repliant reads from and writes to the platforms your network, your billing, and your care teams have run for fifteen years — under the same RBAC and audit posture they already trust.

BSS · billing & charging

read · write · rate

Amdocs CES

customer · billing · charging

Netcracker

BSS · revenue

Oracle BRM

billing & revenue

CSG

Singleview · Ascendon

Ericsson Charging

CCS · pre/post-paid

OSS · network & service

read · diagnose · order

Netcracker OSS

orchestration · service

Cisco NSO

network orchestrator

Ericsson OSS-RC

radio & core

Huawei IES / iManager

NMS · alarms

ServiceNow TSM

service mgmt · FSM

CRM & care

case · journey · agent desktop

SF Comms Cloud

Industries · Vlocity-derived

Genesys Cloud CXi

IVR · routing · WFM

NICE CXone

routing · QM

Pega Customer Service

decisioning · CDH

Microsoft Dynamics

communications template

Identity · channels · network

SIM · voice · SMS · data

Thales · IDEMIA

SIM · eSIM provisioning

Twilio · Vonage

PSTN · A2P SMS

Sinch · Infobip

global SMS · A2P

WhatsApp Cloud

Meta direct

RCS Business

Google · MNOs

For operators on legacy stacks — green-screen Amdocs implementations, custom mediation built before TM Forum templates were a thing, in-house CRMs written by a team that has all retired — Repliant integrates via a signed gateway with batched-write semantics and an OSS-event subscriber that does not require your network team to open a new firewall request. We have shipped against BSS instances older than the iPhone.

Compliance & guardrails

CPNI, MNP, and the SIM-swap perimeter — all wired in.

Telco compliance has more clocks running than any industry on Repliant's roster. We ship with the rules expressed as policy your agent cannot work around — and with audit trails your second line can sign in under fifteen minutes.

CERTIFIED

SOC 2 Type II

CERTIFIED

ISO 27001

ALIGNED

GDPR · DPDP · CCPA

AWARE

FCC CPNI · CALEA

AWARE

OFCOM · EECC

AWARE

TRAI · MNP TAT

Regulator awareness: FCC CPNI · OFCOM Fair Treatment + mid-contract bill cap · TRAI MNP & TCCCPR · EECC · CTIA / GSMA SIM-swap guidance · E911 routing pass-through.

Industry-specific guardrails

  • CPNI BOUNDARY Customer proprietary network information is scoped per tool. The agent cannot share call records, locations, or usage detail outside the authenticated customer's own session.
  • MNP CLOCK Port-out save attempts cannot slow the MNP clock. One offer, then the PAC / UPC code is issued. The clock is monitored at workflow level and reported in the audit log.
  • SIM-SWAP STEP-UP Voice biometric + KBA + registered-email step-up before any swap activation. Activation is held when the risk score crosses the CTIA / FCC threshold.
  • RATE INTEGRITY Plans, add-ons, and roaming bundles are quoted only from your live charging system. The agent does not invent a 50GB tier you don't sell.
  • OUTBOUND CONSENT TCPA, TCCCPR DND, OFCOM contact preferences — checked at the channel layer before send. Quiet hours, STOP keywords, and per-state restrictions are enforced.
  • BILL-SHOCK CAP OFCOM mid-contract cap + EU 280/2009 roaming cap + TRAI usage-alert rules are enforced before any spend trigger fires. Outreach happens before the cap is crossed, not after the bill closes.
  • CALL RECORDING Stored under your KMS, in your region. PII redacted pre-LLM. Right-to-erasure honored on the same flow your CRM already supports.
  • E911 / 999 / 112 Lawful-intercept and emergency routing pass through unmodified. The agent does not intermediate emergency calls under any circumstance.

What to expect

From signed MSA to live in market in 10–12 weeks.

Telco deployments sit between BFSI and travel on the timeline axis — slower than retail because the BSS and OSS reviews are serious, faster than banking because the regulator landscape is better-understood. We move at a pace your network operations team, your CISO, and your regulator can all live with.

W1 W3 W5 W7 W9 W11 W12 · GA DISCOVERY BSS · OSS · CHARGING SECURITY · NETOPS SANDBOX · LANG. PHASED ROLLOUT Scope · access · CISO + netops BSS + OSS connected · sandbox CISO + 2nd-line signoff SIM-swap drill · CPNI audit 23 lang · outage-day drill 5% live · then 50% · then full GA · regulator walkthrough

FAQ

Questions telco buyers actually ask.

If yours isn't here, your AE will get it answered before your second meeting.

Can the agent actually navigate Amdocs / Netcracker, or does it just read?

Both. Native read/write into Amdocs CES (customer, billing, charging), Netcracker (BSS + OSS), Oracle BRM, CSG Singleview, and FIS Profile-style charging where applicable. The agent operates within scoped tools — it can rate, quote, change a plan, add an add-on, and write the disposition — but cannot, for example, exceed a configured credit limit. Scope changes flow through your existing IT change-management process.

How do you handle port-out under FCC / OFCOM / TRAI MNP rules — we can't appear to slow down a port?

Exactly one save offer. If the customer declines, the PAC / UPC / port code is issued immediately and the MNP clock continues unbroken. This is enforced at the workflow level — there is no path for an agent or a BPO supervisor to extend the save attempt. Audit log records the timestamp of request, the timestamp of save offer, and the timestamp of code issuance. We have walked OFCOM and TRAI through this exact log without remediation findings.

What about CPNI — can the agent share customer proprietary network information?

CPNI is scoped per tool and per authenticated session. The agent cannot share call records, locations, usage detail, or service-feature configurations outside the authenticated customer's own session. Family-plan administrators and corporate-account principals are recognized and scoped accordingly. Third-party requests (subpoenas, law enforcement) are routed to your CALEA / lawful-intercept workflow without passing through the model.

SIM-swap fraud is the #1 thing my CISO worries about. How do you not become an attack surface?

Voice biometric verification on every callback, KBA against the customer of record (never invented), step-up to the registered email, and a hold on activation when the risk score crosses your configured threshold (mapped against CTIA / GSMA / FCC guidance). The agent cannot activate a SIM swap above the configured risk score without a fraud-analyst on the live call. We have shipped against operators carrying this concern as a top-three risk register item, and have not yet contributed a confirmed fraud case in the cohort.

What's the model doing during a network outage — does it have outage-state awareness?

Yes — first-class. The agent subscribes to your NMS event feed (Cisco NSO, Ericsson OSS-RC, Huawei iManager) and knows about declared outages before the customer does. During an outage, the agent stops attempting device-side troubleshooting (which annoys the customer), acknowledges the issue, applies the appropriate proactive credit per your policy, and offers the right next contact moment. When the outage clears, customers in the affected cells receive a proactive follow-up if your policy requires it.

We run a flagship brand and a sub-brand MVNO. Can we calibrate per brand?

Yes. Each brand in your portfolio gets its own tone preset, escalation matrix, plan catalog, and CPNI scope — with the same underlying systems integration. Customers crossing between brands are recognized by the agent and treated within the new brand's policy. Brand-voice changes ship through your existing review process; you sign off before any voice update touches a real customer.

TCPA and TRAI commercial communications — can it do outbound that's actually compliant?

Outbound only sends to numbers with a recorded opt-in tied to your subscriber base, with quiet hours, STOP / HELP keywords, and per-state and per-jurisdiction restrictions enforced at the channel layer. TRAI DLT registration is supported for India deployments. OFCOM contact-preference state is honored. The agent does not initiate outbound to a number without a documented consent record — and the consent record is exportable for regulator inspection.

What does the audit trail look like — and can our second line sign it off?

Every session emits a signed, immutable record: channel, tools called with arguments, policies evaluated, MNP timestamps, CPNI scope, the model trace, and the final disposition (with the BSS write confirmation). Records are exportable to your existing GRC platform — MetricStream, Archer, ServiceNow IRM — on whatever schedule your team configures. We have walked operators' second-line auditors through a full sample inside fifteen minutes.

Repliant for Telco

Your next outage weekend doesn't have to end at the regulator.