Our AI agent can ring you back now.Get a call back

Voice and chat agents that answer like a person

Mirakash agents pick up in under a second, speak the caller's language, and hand off to a human without dropping the thread. Built for phone lines in India and the Gulf, priced per minute of talk time.

Runs on the numbers, channels and systems you already use

Twilio
Plivo
WhatsApp
Slack
Zendesk
HubSpot
Salesforce
Notion
Google Sheets
Microsoft 365
Confluence
Gemini

What changes the day the agent picks up

Every call answered

Nights, weekends, festival days. The agent picks up in under two seconds, and a queue of fifty callers is no different from a queue of one.

In the caller's language

Hindi, Malayalam, Tamil, Arabic, English — and the switching between them mid-sentence that real callers do, without a menu first.

A human, one step away

When the agent reaches its limit it consults a person who joins with the transcript, and the caller never repeats themselves.

India & the Gulf

Built for the calls other agents don't pick up

Numbers that work in Kochi and Dubai, speech models trained on how people there actually talk, and a clear answer on what is possible in each country before you buy.

EnglishHindiMalayalamTamilArabicCode-switching

Under a second to first word

Speech in, speech out, with barge-in — the caller can interrupt and the agent stops talking.

Per-second billing, ₹0 for voicemail

Answering-machine detection ends the call before it costs anything, and every call is metered by the second.

Consult-and-resume handoff

The agent brings a person in rather than transferring the caller away, so nobody starts over.

Configure, deploy and improve from one console

The agent, its numbers, its knowledge, its tools, the calls it takes and the score each one gets — all in the same place, on one API-first, multi-tenant platform.

Design the agent in the browser

Persona, voice, knowledge and tools — then test it on a live call before it ever answers a customer.

app.mirakash.com/overview
Overview /Agent overview
N
Calls today
1,284+12%
Containment
78%+4pt
Avg latency
620ms−40ms
Cost / call
$0.019on target
Live calls · now8 active
Ringing
+1 415 · billing
+1 646 · refund
+44 20 · hours
Active
+1 312 · order
+1 210 · booking
Wrap-up
+1 917 · resolved
Calls handled · 12w
Live activity
call.completed+1 415 · 2m14s
number.provisioned+1 646 555 0142
agent.publishedBilling v4
escalation.openedrefund · #4471
call.scoredCSAT 4.8
agent.startedFront desk

Sub-second voice, any vendor

Speech-to-text, the model, and text-to-speech on pluggable adapters or native Gemini Live. Swap a stage; the agent stays.

app.mirakash.com/calls
Conversations /Live calls
N
BoardTableLive
Agent: Front desk ▾Filter8 live · avg 1:24
Listening3
+1 415 555 0142
billing · 0:18AI
+1 646 555 0188
refund · 0:41AI
+44 20 7946 021
hours · 0:07AI
Thinking2
+1 312 555 0170
order status · 1:12AI
+1 210 555 0133
booking · 0:52AI
Speaking2
+1 917 555 0121
reschedule · 2:03AI
+1 503 555 0199
address · 1:35AI
Handoff1
+1 628 555 0146
escalated · 3:40JD

Watch it work, step in when needed

Every call and message as it happens. Take over in text, or bring a person in who arrives with the context.

app.mirakash.com/workflows
Workflows /Workflow runs
N
RunsBuilderTriggers
TriggerIntentToolAction
Event · streamstep
call.received→ transcribe
intent.detected→ call tool
agent.stuck→ escalate to human
tool.returned→ resume speaking
silence.detected→ reprompt caller
sentiment.dropped→ soften tone
call.ended→ score + summarize

Measure what it costs and what it resolves

Containment, escalation, sentiment and cost per agent, on dashboards you define over your own events.

app.mirakash.com/analytics
Analytics /Support · agent analytics
N
DashboardMetricsWidgets
Containment
78%+4pt
Escalation rate
9.2%−1.3pt
Avg sentiment
+0.42+0.05
Cost / call
$0.019
Calls over time · 30dmetric: calls
Escalations · count
Cost · $/call
Recent calls
call.completed2m14s
escalationrefund
call.completed0:48
intent.detectedbooking
call.scored4.8

Connected to the systems that hold the answers

API & connectors
  • Twilio & Plivonumbers you own — inbound and outbound, bring your own account or use a managed one
  • WhatsApp, SMS, email & web chatthe same agent on every channel, with one conversation history
  • Zendesk, HubSpot & Salesforcetickets, cases and contacts created from the call, not after it
  • Google Sheets, Calendar & Microsoft 365bookings and lookups against the data you already keep
  • Slack & Notionalerts and notes where the team already works
  • Your own endpointsany REST API as an agent tool, secrets interpolated at run time
  • Webhookssummary, outcome and extracted fields delivered after every conversation
  • Knowledge basescrawled sites and uploaded documents, retrieved at the moment of the answer

One platform, every desk that answers a phone

Start from an agent built for the job, on the screen the team doing that job actually uses.

Resolve the routine calls. Hand off the rest, with context.

Order status, password resets, opening hours — answered in seconds, in the caller's language. Anything the agent can't settle goes to a person with the transcript attached.

Explore support agents
app.mirakash.com/qa
QA /Review queue
N
ScorecardsEscalationsIssues
Escalations
7
Failing
2
Avg score
4.6
Resolved
92%
#ns41
Refund escalated
+1 646 · billing
AMescalated
#ns38
Outage · West region
+1 855 · tech
PKescalated
#ns34
Tier-2 handoff
+1 628 · disputes
JDopen
#ns2f
SLA breach risk
+1 312 · warranty
AMreview
#ns27
Repeat caller
+1 917 · payment
PKopen
Order statusTier-1 triageAccount & passwordAfter-hours line

Your data, on your terms

Isolation between workspaces is built into the platform, not bolted onto the interface. These are the guarantees the code enforces today.

Security & multi-tenancy
  • Server-side scopingEvery query is scoped to the caller's workspace in the data layer — never trusted from the client.
  • Role-based accessEach route is guarded by a permission; the console gates navigation and actions on the same set.
  • Encrypted BYO credentialsYour carrier tokens and API keys are AES-256-GCM encrypted at rest, masked on return, and never logged.
  • Verified-domain isolationWeb-chat domains and CORS both require a verified host, so branding never widens access.
  • Consent before the callThe demo only rings a number after a code sent to it proves it belongs to the person asking.

Book a demo

Hear it on a real call, in your language, on your use case.

Book a demo
  • A live agent on a real phone line
  • Your script, your knowledge
  • Pricing for your volume
  • India and Gulf coverage, answered honestly

Talk to us

For deployment, carrier and compliance questions, or a partnership.

Contact us
  • Managed, bring-your-own or white-label
  • Numbers and regulatory questions by country
  • Agency and reseller margins
  • Outcome-based pricing for larger accounts

Build on the API

Everything the console does, your code can do.

API reference
curl -X POST https://api.mirakash.com/api/v2/calls \
  -H "authorization: Bearer mk_live_…" \
  -d '{ "agentId": "agent_billing_v4",
        "to": "+971501234567" }'

Frequently asked questions

What exactly is Mirakash?

An all-in-one platform for running AI voice and chat agents end to end: an agent builder you can test in the browser, a realtime STT → LLM → TTS voice pipeline, telephony and phone numbers, omnichannel messaging, an event-driven workflow engine, knowledge and RAG, QA scorecards, human-in-the-loop escalation, analytics with cost per agent, and a full API — all on one multi-tenant system.

How is one workspace kept from seeing another's data?

Isolation is enforced in the data layer, not the UI. Every scoped query runs through a shared helper tied to the caller's organization, and cross-tenant access throws by construction. Any bring-your-own credential is AES-256-GCM encrypted at rest and decrypted only in-process.

Can the web chat be white-labeled?

Yes. The embeddable web-chat widget carries your theme, logo, and custom domain, resolved only for verified hosts, so branding never widens access. The same agent also answers on phone, WhatsApp, SMS, and email.

How do connectors and the API work?

Mirakash is API-first, and its connectors really fire — Slack, Zendesk, Google Sheets, Notion, and webhooks execute for real and are env-gated. Agent tools call your own endpoints, with runtime {{VAR}} interpolation so a URL or header can be an environment-variable decision. You can even point an AI agent at the API and have it call endpoints directly.

What happens automatically when a call comes in?

An inbound call emits an event. The voice pipeline transcribes and responds in under a second, the agent uses its knowledge and tools to resolve the request, workflows fire on every event, and if the agent hits its limit it escalates to a human — with no manual step.

How does human-in-the-loop work?

When an agent can't resolve something, it doesn't drop the caller. It escalates to a queue that routes to a human provider or another agent, gets an answer, and resumes the original conversation — consult-and-resume, not a blind transfer. Every escalation is tracked and assignable.

Can I run this in the UAE, Saudi Arabia or Qatar?

Yes, and the split is worth knowing before you buy. Inbound works immediately: a UAE number, or a toll-free 800 number in Saudi Arabia and Qatar. Outbound does not run on a number bought from any cloud telephony provider — UAE numbers are inbound-only under the carrier's own terms — so it runs on a number registered to your trade licence, over your own operator's SIP trunk, which Mirakash imports. The agent handles Gulf Arabic and Najdi alongside Hindi, Urdu, Malayalam, Tamil and Tagalog, which matters in a country where most residents are expatriates.

Put an agent on your line this week

A walkthrough on a real call — voice pipeline, numbers, workflows, QA and human handoff working together.