Telephony & numbers
Give your agent a real phone number without a telephony project of your own. Provision numbers in one click across three account models — bring your own Twilio, a managed subaccount we resell, or the platform master — handle inbound and outbound, with auth tokens AES-256-GCM encrypted at rest.
Getting a voice agent on a real phone number is its own project
Standing up telephony means a Twilio account, subaccounts, credentials to store safely, and inbound/outbound wiring — before a single call connects. Most teams stall here, and the ones that push through leave auth tokens sitting in plaintext.
The flow, end to end
Choose
Pick an account model — your own Twilio, a managed subaccount, or the platform master.
Provision
Search available numbers and claim one to your workspace in a single click.
Route
Point the number at an agent; inbound calls reach it and it can dial out.
Secure
Auth tokens are encrypted at rest the moment they're saved and decrypted only in-process.
What's in the box
One-click numbers
Search and provision a phone number to a workspace in one click — no separate telephony console.
Three account models
Bring your own Twilio, run on a managed subaccount we resell, or fall back to the platform master.
Inbound & outbound
Numbers take incoming calls and place outgoing ones, routed to the right agent per workspace.
Encrypted at rest
Twilio auth tokens are AES-256-GCM encrypted at rest, masked on return, never logged.
Per-workspace routing
Each number belongs to a workspace and routes to its agent — isolation enforced server-side.
Bring your own Twilio, resell a subaccount, or use the master
Mirakash provisions numbers across three account models so you can start on the platform master, graduate to a managed subaccount we resell, or bring your own Twilio and keep full ownership — all through the same one-click flow.
- ✓BYO Twilio, managed resold subaccount, or platform master
- ✓One provisioning flow across every account model
- ✓Numbers scoped to a workspace and its agent
Auth tokens usable in memory, opaque everywhere else
When a workspace brings a Twilio auth token, Mirakash encrypts it with AES-256-GCM at rest, decrypts it only in-process at the moment a call is placed, masks it on every read, and keeps it out of logs entirely. The plaintext never lingers beyond the instant it's needed.
- ✓AES-256-GCM encryption for every stored auth token
- ✓Masked on return; never rendered or logged in plaintext
- ✓Decrypted only in-process, at the moment of use
Realtime voice pipeline
Sub-second STT→LLM→TTS with barge-in, on ~11 pluggable provider adapters or native Gemini Live.
Learn moreWorkflows & automation
An event-driven, node-graph engine that turns any signal into the right action, automatically.
Learn moreSecurity & multi-tenancy
Role-based access, strict org isolation, and encrypted BYO credentials — by construction.
Learn moreReady to put an AI agent on every call?
Book a walkthrough and see the voice pipeline, telephony, workflows, QA, and human handoff working together — on one platform.