All Case Studies
CS / 01Telecommunications · AI PlatformRegional Telco Group (multi-country)

Designing an AI Communication Multi-tenant Platform for Telcos (2026)

Carrier-grade multi-tenant CPaaS+CCaaS platform with native Vietnamese voicebot, omnichannel (Voice, Zalo, WhatsApp, Messenger, LINE, FB) and built-in LLM/RAG — designed for telcos to resell as a turnkey AI Communication service.

Telecommunications · AI Platform · Regional Telco Group (multi-country)
01
Multi-tenant
Tenant isolation by design
02
6 channels
Voice + 5 messaging apps
03
<300ms
Voicebot turn latency (p50)
04
99.99%
Platform SLA target
Project timeline

Challenge → Solution → Outcome

Step-by-step view of how we moved from the brief to the outcome.

Step 01Challenge

Regional telcos want to monetise AI Communication beyond connectivity but lack a multi-tenant platform where each downstream enterprise customer gets isolated data, branding, numbering and AI knowledge bases — while sharing the same SoftSwitch, SBC and LLM gateway. Existing CPaaS vendors are foreign-hosted, expensive per minute, and weak on Vietnamese ASR/TTS.

Step 1 / 11
01 / 11
Story arc

Problem. Solution. Result.

01
Problem

Regional telcos want to monetise AI Communication beyond connectivity but lack a multi-tenant platform where each downstream enterprise customer gets isolated data, branding, numbering and AI knowledge bases — while sharing the same SoftSwitch, SBC and LLM gateway. Existing CPaaS vendors are foreign-hosted, expensive per minute, and weak on Vietnamese ASR/TTS.

02
Approach
  • 01Designed a 3-plane architecture: Control (tenant/IAM/billing), Data (CDR, transcripts, RAG), Media (SoftSwitch, SBC, voicebot, channel gateways).
  • 02Multi-tenancy via schema-per-tenant + row-level security; per-tenant encryption keys and audit log.
  • 03Omnichannel inbox unifying Voice, Zalo, WhatsApp, Messenger, LINE and Facebook in one agent UI.
03
Result
  • Reference architecture & detailed HLD/LLD delivered (attached HTML design pack used as source of truth).
  • Per-minute economics ~55% lower than reselling a foreign CPaaS at equivalent SLA.
  • Time-to-onboard a new enterprise tenant: under 1 business day end-to-end.
02 · Solution

Solution

  • 01Designed a 3-plane architecture: Control (tenant/IAM/billing), Data (CDR, transcripts, RAG), Media (SoftSwitch, SBC, voicebot, channel gateways).
  • 02Multi-tenancy via schema-per-tenant + row-level security; per-tenant encryption keys and audit log.
  • 03Omnichannel inbox unifying Voice, Zalo, WhatsApp, Messenger, LINE and Facebook in one agent UI.
  • 04Native Vietnamese voicebot pipeline (ASR → NLU → RAG/LLM → TTS) with barge-in, sentiment routing and human handoff.
  • 05Self-serve tenant portal: number provisioning, bot designer, knowledge upload, usage & billing dashboard.
  • 06Carrier-grade reliability: dual SBC, geo-redundant Media plane, blue/green release for the AI plane.
03 · Outcome

Outcome

  • Reference architecture & detailed HLD/LLD delivered (attached HTML design pack used as source of truth).
  • Per-minute economics ~55% lower than reselling a foreign CPaaS at equivalent SLA.
  • Time-to-onboard a new enterprise tenant: under 1 business day end-to-end.
  • Roadmap covers GenAI agent assist, real-time translation and proactive outbound campaigns.
04 · Before / After

Measurable shift

01
Tenancy model
BeforeSingle-tenant per deployment
After
Multi-tenant with isolation by design
02
Channels in one inbox
BeforeVoice + email only
After
Voice + 5 messaging apps
03
Vietnamese voicebot
BeforeOutsourced / foreign vendor
After
Native pipeline, tunable per tenant
04
Tenant onboarding time
Before2–4 weeks
After
< 1 business day
05
Per-minute cost vs foreign CPaaS
BeforeBaseline 100%
After
~45% of baseline
In their words
The design pack covered everything from SBC dimensioning to per-tenant RAG isolation. We could hand it to procurement and to our engineers in the same week.
VP Digital Services·Regional Telco Group (under NDA)
Tech Stack
SoftSwitchAarenet SBCWebRTCVietnamese ASR/TTSLLM Gateway + RAGPostgreSQL (RLS)KafkaKubernetesZalo/WhatsApp/Messenger/LINE/FB APIs

Have a similar challenge?
Let's talk.

ZaloContact