Voice, wherever your customers already are. Not just WhatsApp.
EPIC's voice backend reaches customers on WhatsApp, on Telegram, and on a real phone number — the same PBX, AI agent, and unified inbox behind all of it. WhatsApp Calling is live on EPIC's platform right now, not a roadmap item. Calls route to your PBX extension, your IVR, or your AI agent, and the agent can call out too.
One backend. Every channel has its own real plumbing — we don't pretend otherwise.
Each channel actually works differently under the hood. Here's the honest version of each.
WhatsApp Voice
Meta's own Business Calling API — live on EPIC today. It's app-to-app only: a WhatsApp call can't ring a real phone number by itself. EPIC's SIP infrastructure is what bridges it to a PBX extension or the outside phone network.
Telegram Voice
Different plumbing: Telegram's official Bot API doesn't carry live calls at all, only voice notes. Real Telegram calling runs through a SIP gateway connected to a Telegram account, which EPIC can route the same way — and unlike WhatsApp's call API, that gateway path can reach PSTN directly. Different architecture, same backend behind it.
A real phone number
No platform restrictions at all — EPIC's own SIP trunk and the IDT Express carrier contract reach any number, domestically or internationally. This is the channel the other two ultimately connect through.
One number. You decide where the call goes.
This is how it works today — proven, not planned.
Customer calls your WhatsApp number
Same number your customers already text. No new app, no new number to remember.
EPIC routes it
The call hits EPIC's platform first — this is where you set the rule for what happens next.
It goes where you tell it to
Your PBX IVR, a specific extension, or straight to your AI agent — your choice, configurable.
Agent can call back out, too
Your AI agent can place outbound WhatsApp calls — with the customer's consent. WhatsApp requires an opt-in permission request before a business-initiated call, so this is for callbacks and confirmed follow-ups, not cold dialing.
To your PBX
Route into an IVR menu or a specific extension on your existing hosted PBX — the call behaves like any other line coming into your office.
To your AI agent
The same agent that already handles WhatsApp text (ACE) can answer and make voice calls — proven and working, not a separate build.
To a human, with handover
Calls and chats share one inbox, so a conversation can move from AI to a real person without the customer starting over.
Whether you're a business or you're building the agent
Run entirely on WhatsApp
If your customers already message you on WhatsApp, now they can call that same number too — and you decide who or what answers.
- One number for calls and messages — nothing new for customers to learn
- Calls route to your team, your IVR, or your AI agent
- Unified inbox — text and voice history in one place, with AI-to-human handover
- Records tied into Odoo automatically
Bring your own agent. Use our telephony.
Building an AI voice agent and don't want to become a telecom company to give it a number? EPIC already is one.
- Onboard your WABA with EPIC — we're an approved Meta Tech Provider
- We add a number to your WABA, or manage the one you already have
- Real SIP infrastructure and a carrier contract (IDT Express) behind it — international numbers and international outbound calling, available now
- You control call routing and agent parameters; we run the backend
The infrastructure behind it
Not a reseller promise — EPIC already holds this:
What's real right now — the honest version
- ✓Customer-initiated calls are live and free of Meta's own charges — a customer tapping "call" on your WhatsApp number costs nothing extra from Meta.
- ✓Outbound calls need the customer's consent first — WhatsApp requires a permission-request template the customer accepts before a business-initiated call goes through, and it's rate-limited per customer. This is built for callbacks and confirmed follow-ups, not outbound dialing campaigns.
- ✓WhatsApp Calling alone doesn't reach a real phone number — it's app-to-app. Getting a WhatsApp call to actually ring a PBX extension or a real phone line is what EPIC's own SIP infrastructure and carrier contract do — that's the part we're actually providing, not just a Meta feature we're relaying.
- ✓Access to this is still a phased Meta rollout — not every business or provider has Calling API access yet.
This isn't a feature. It's the whole loop.
A customer doesn't experience "WhatsApp Calling" and "ads" and "CRM" as separate things — they experience one conversation with your business. EPIC sits across the whole thing, not just one piece of it.
They find you
A Facebook or Instagram ad, built to send people straight into a WhatsApp conversation or a call — not a website they bounce off.
You answer — live today
One number, voice and text, routed to your PBX, your AI agent, or a person. This part is already real.
It becomes a booking or a sale
In-chat forms for appointments, a catalog for orders — no app switching, no losing the customer mid-conversation.
It feeds back
The outcome lands in Odoo. The same outcome tells Meta which ads actually led to a sale, not just a click.
We're building our public review program. See what real customers are saying about EPIC on Facebook and Google — or tell others about your own experience.