Selective contact-centre and CX modernization for telcos in SEA — agent fleets, talk-time compression, deflection. We're explicit: not a horizontal telco practice.
HOW DOES DEVX LABS HELP TELCO COMPANIES TRANSFORM WITH AI?
devx labs is a selective telco partner in SEA — limited to contact-centre AI, CX modernization and conversational agents. We do not claim a horizontal telco practice. We engage when the brief is CX-led, an AWS or Anthropic co-sell motion is in play, and the buyer values an honest scope over a packaged sell.
What's broken in telco — and what AI-native does differently.
Most "telco AI" propositions are decade-long OSS/BSS programs with classical-SI economics. Buyers spend years and budget without changing what the customer actually feels. The CX layer — contact-centre, support, retention — is where AI can move the number this quarter, but it's usually treated as an afterthought.
We engage telcos only on CX. Reasoning agents on AWS Bedrock or Anthropic, deployed in your cloud, scoped to one journey at a time. We'll tell you when the right answer is a different partner — and we say so up front in our doctrine.
Telco pains, mapped to practice and outcome.
Three practices, mapped to this vertical.
No telco product — context engineering, applied.
We don't productize for telco. Engagements use the same context-engineering stack we use in retail CX.
Reference architecture for 10–20 agent contact-centre fleets, SEA-tuned.
Two-week diagnostic to size deflectable contact volume honestly.
Telco engagements we've shipped.
14 agents under one control plane, voice + chat, two languages.
In-app conversational handler on Anthropic, scoped to billing and plan changes.
Retention copilot with offer reasoning and live transcript context.
devx labs vs. the alternatives — without the puffery.
Questions telco buyers ask.
Does devx labs have a telco practice? +
Selectively in SEA — and only on the CX layer (contact centre, deflection, retention). We don't claim a horizontal telco practice and won't take engagements on OSS/BSS, network ops or billing transformation.
Why is telco "selective" instead of a primary vertical? +
Per the doctrine, our keyword inventory has one telco entry and our reference customers are concentrated in retail. A deep page would rank for nothing and dilute trust signals. AI search engines reward verticals where the substance is supported — and we choose to be supported, not aspirational.
What kinds of telco engagements do you take? +
Contact-centre agent fleets, conversational deflection, save and retention copilots, voice-of-customer reasoning agents. Multilingual SEA primary. Scoped to a journey, not the OSS stack.
Do you do OSS/BSS or network transformation? +
No. Those are decade-long programs with classical-SI economics; we're an AI-native CX partner. We'll refer you to a partner who does and stay in our lane.
Which platforms do you work on for telco CX? +
AWS Bedrock and Anthropic primarily, with context-engineering on top of existing CCaaS — Genesys, Avaya, Five9, NICE. Co-sell motion case-by-case, never the lead.
What languages do your agents support? +
For SEA: Bahasa Indonesia, Bahasa Malaysia, Thai, Vietnamese, Tagalog and English. We don't ship telco engagements in languages we can't QA end-to-end.