Issue № 01Agentic AI

Voice Agent Platform

A white-label, multi-tenant AI agent platform for enterprise voice and chat — retrieval-backed knowledge, tool use, and compliance-ready flows. Agents that act, not chatbots that reply.

At a glance: Ethereal built an AI phone-and-chat assistant that answers customer calls and messages around the clock, understands what people actually need, and gets things done instead of just reading canned replies. It replies in under a second, works for both phone and web chat, and follows US privacy and calling rules automatically.

Voice Agent Platform — cover artwork01
Client
Confidential enterprise platformUS-regulated
Industry
Enterprise AIVoice automation · Customer support
Year
2025
Services
Agentic AIVoice AIRAG SystemMulti-tenant PlatformCompliance Layer
~750msend-to-end voice latency budget
2-in-1one engine for voice + chat
0 codetenant onboarding via config
5 gatescompliance controls on by default
01

The Problem

Businesses — including US-regulated ones — need 24/7 voice and chat support, but face high telephony costs, strict compliance exposure (TCPA, PCI, PII), and slow per-client onboarding. Most "AI support" products are chatbots that only reply; enterprises need agents that act.

Cost

Round-the-clock human phone coverage is the single most expensive support line item.

Risk

TCPA, PCI, and PII rules make every automated call a legal exposure if handled naively.

Speed

Onboarding each new client meant weeks of custom engineering — it had to become config.

02

The Solution

We designed a white-label, multi-tenant platform on a 4-layer architecture — tenant config → stack profile → industry pack → engine — so new tenants onboard with zero code. Each tenant gets its own FAISS-backed retrieval knowledge base. Compliance gates are on by default: consent matrix, automatic PII redaction, PCI-pause during card numbers, DNC registry checks, and explicit AI disclosure. A single engine serves both telephony (voice) and WebSocket (chat) channels.

System architecture
L1Layer

Tenant Config

Brand, prompts, escalation rules, and knowledge sources — declared, not coded.

L2Layer

Stack Profile

Model, STT/TTS voices, and channel mix selected per tenant from vetted profiles.

L3Layer

Industry Pack

Vertical-specific flows, vocabulary, and compliance presets for regulated domains.

L4Core

Engine

One agent runtime — retrieval, tool use, and conversation state — shared by every tenant.

Voice pipeline
TelephonyTwilio
Speech-to-textDeepgram
Reasoning + tool useGemini + Claude · FAISS RAG
Text-to-speechElevenLabs
Latency budget
~750ms

End-to-end, per voice turn

Second channel · Web chat

The same engine answers web chat over WebSocket — same knowledge base, same tools, same compliance gates. One brain, two mouths.

State & memory

Postgres holds tenant state; Redis keeps conversation memory hot enough to stay inside the latency budget.

Compliance, on by default
Consent Matrix

Every outbound contact is checked against recorded consent before a call is placed.

PII Redaction

Personal data is redacted automatically from transcripts, logs, and model context.

PCI Pause

Recording and transcription pause the moment a caller reads out card numbers.

DNC Registry

Do-Not-Call registry checks run before any outbound campaign touches a number.

AI Disclosure

Callers are explicitly told they are speaking with an AI agent — always, by default.

03

The Outcome

A ~750ms end-to-end voice latency budget keeps conversations human-grade. One unified engine serves two channels, and compliance is built in for regulated verticals — new tenants onboard without touching code.

Built with

08 technologies
01FastAPIAPI layer
02Gemini + ClaudeReasoning · tool use
03FAISSVector retrieval
04TwilioTelephony
05DeepgramSpeech-to-text
06ElevenLabsText-to-speech
07PostgresTenant state
08RedisHot memory
Next issue — yours?

Have an agentic ai problem like this?

Tell us what you're building — we'll tell you exactly how we'd ship it.

Keep reading

From the archive

All 15 case studies →