Every call answered. In the caller's language.
A patient messages your clinic at 9:40 on a Saturday night. A minute later they are booked, confirmed and told the fee. Nobody on your team picked up a phone.
It plugs into the numbers, channels and systems you already run. Nothing to rip out.
- Twilio
- Plivo
- Slack
- Zendesk
- HubSpot
- Salesforce
- Notion
- Google Sheets
- Microsoft 365
Watch one conversation. Start to finish.
Keep scrolling and it plays. The clock runs, the agent reaches for its tools, and the record writes itself. Pick another at the top and it starts again from the first message.
- Channel
- Phone
- Language
- Malayalam
- Tools called
- 0
- Hand-off
- —
spoken in Malayalam · shown in English
- check_slotswaiting
- book_appointmentwaiting
- transfer_to_humanwaiting
- knowledge_basewaiting
- calling_hourswaiting
- 00:00 · keep scrolling to play it
- Intent
- —
- Booked
- —
- Fee quoted
- —
- Hand-off
- —
- Call
- Systems
One customer. Every channel. One memory.
A message on WhatsApp. A call back a minute later, from an agent that already knows what was asked. A booking, a confirmation in the chat, an email to the desk. Pick a business and watch it run.
- WhatsApp · message in“Can I see Dr. Anitha tomorrow?”
- AgentReads it in Malayalam
- System check · check_slotsClinic diary · 2 slots free
- ConditionAsked to be called?
- Phone · schedule_follow_up · if asked for a callRings in a minute, offers 09:30
- WhatsApp · reply · if stayed in chatSlots sent as a tappable list
- Action · book_appointmentPW-2417 · 09:30 · token 3
- WhatsApp · send_messageReference, time and fee
- Email · clinic deskBooking with the transcript
- Also into
It remembers.
Called on Monday, messaged on Friday? Same conversation. Nobody is asked to start over.
It checks before it speaks.
Diaries, menus, orders and CRMs are read at the moment of the answer, through tools you control. Never from memory.
It knows when to stop.
When a person is needed, a person arrives — with the transcript already open.
Someone calls. It gets handled.
No hold music. No voicemail. The agent picks up, understands, and finishes the job.
They call.
Your number, on your carrier or ours.
It listens.
In their language. They can cut in mid-sentence.
It thinks.
With your prompt, your knowledge, your rules.
It gets it done.
Books it, takes the order, or hands over to a person with the notes.
Change any part. The agent stays the same.
- Voice9 vendors
- Speech-to-text5 vendors
- Phone carrier11 carriers
Don't take our word for it. Take a call.
Pick an agent. Type your number. Your phone rings in seconds. Then try to break it.
Order a coffee. From a cafe that doesn't exist.
It reads you the menu as a list you can tap. It tells you when an item is off. It sends a payment page, a receipt, and answers when you ask where your order is. The cafe is made up. The agent is the one your customers would get.
- 1 × Flat White
- INR 180.00
- 1 × Butter Croissant
- INR 140.00
- Subtotal
- INR 320.00
- Delivery
- INR 30.00
- GST
- INR 17.50
- Total
- INR 367.50
- 09:12 ƒ send_cataloguesentFive rows of the Menu table, sent as a tappable list
- 09:13 ƒ lookup_recordsrule heldChocolate Croissant marked unavailable — offered the Butter one
- 09:15 ƒ place_orderrule heldPriced from the shop's rows. No price field for the model
- 09:16 ƒ place_ordersentPayment link sent with the test-card warning in the same message
- 09:31 ƒ order_statusreadAnswers only for orders placed from this number
Now try it on your own phone.
A fake cafe on a real number. Change your mind halfway. Ask for something that isn't on the menu. Pay on the test page. The one thing you can't do is get it to make up a price.
- It tells you it's a demo — and that the payment page is a test — before you can pay.
- Every price comes from the shop's own menu rows. The agent has no field to type one into.
- It can only see orders placed from the number it's talking to. Nobody else's.
Your own number. Answering in minutes.
No developer account. No webhooks. No app review of your own. Connect the number your customers already message — and the agent that answers your phone starts answering WhatsApp too, in their language, with your knowledge behind it.
- The account and number stay in your own Meta business portfolio.
- Meta bills its message charges to you directly — we never mark them up.
- Conversations stay on WhatsApp, opt-outs are honoured on the number, and a person can take over with one click.
How much did it really handle? Hour by hour.
Most dashboards tell you it went well. This one shows you the hours it didn't — and the reason a person was needed, every time.
- Conversations
- 3,906
- Resolved by the agent
- 3,181
- Handed to a person
- 725
- Asked for a person18
said so, in any language
- Payment question12
- Outside the agent's scope9
Find the hour a person was needed.
Leave it alone and the cursor walks the day. Point at an hour and it stops there, opened up.
One platform. Every desk that answers a phone.
Pick a desk. Watch where the conversation comes in, what the agent does with it, and what you get out the other end.
The same question, the four-hundredth time today. Answered like it was the first.
What the agent does- ƒ knowledge_baseAnswers from your own help pagesdone
- ƒ your APIFinds the order and where it isdone
- ƒ zendesk.createTicketWrites the ticket when it can't fix itdone
- Answered at 2 a.m. without a queue
- A person gets the case already written up
- Every reason for a hand-off, counted
One console. Everything it did, and why.
The agent, its numbers, its knowledge, its tools — every call it took and the score each one got. In one place, not six.
Design the agent in the browser
Persona, voice, knowledge and tools — then test it on a live call before it ever answers a customer.
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.
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.
Measure what it costs and what it resolves
Containment, escalation, sentiment and cost per agent, on dashboards you define over your own events.
An agent is only as good as what it can look up. So it looks up yours.
- Twilio & PlivoNumbers you own, inbound and outbound. Your account or a managed one.available
- WhatsApp, SMS, email, web chatOne agent on every channel, with one history.available
- ZendeskTickets raised and updated from the conversation, not after it.available
- Google SheetsRows appended and looked up against the sheet you already keep.available
- Slack & NotionAlerts and notes where the team already works.available
- Your own APIAny REST endpoint as a tool, with secrets filled in at run time.available
- WebhooksSummary, outcome and extracted fields, after every conversation.available
- Knowledge basesYour site and documents, read at the moment of the answer.available
- HubSpot & SalesforceContacts and cases from the call.coming soon
- Google Calendar & Microsoft 365Bookings straight into the diary.coming soon
Start with one. Add the rest when you're ready.
Same agent, same knowledge, same history on every channel. A caller who messages you later is not a stranger.
- Phone callsInbound and outbound on numbers you own or we provision, metered by the second.
- WhatsAppYour own number, connected in minutes. Text, photos and voice notes.
- Web chatA widget on your site that knows every page of it, in your brand.
- Agent builderPersona, voice, knowledge and tools — tested on a live call before it answers anyone.
- Voice pipelineSpeech in, speech out, with barge-in. Every stage on a swappable vendor.
- KnowledgeCrawled sites and uploaded documents, retrieved at the moment of the answer.
- WorkflowsBookings, orders and tickets raised from the conversation, not after it.
- Human hand-offA person brought in with the context, or taking over the chat in one click.
- AnalyticsContainment, escalation and cost per agent, on dashboards over your own events.
- APIStart calls, read transcripts and receive outcomes from your own code.
A personal touch. In the caller's own language.
A caller in Kochi doesn't want to be answered in textbook English. So we choose speech models for how people there actually talk — and tell you straight what is possible in each country before you buy.
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.
A person joins. Nobody starts over.
The agent brings a person into the conversation instead of transferring the caller away — and picks up again when they're done.
Scale without losing control. Every action, accounted for.
Here's the question your security team will ask: who can see what? The answer is one matrix, on the server. And every change lands in a trail that can't be quietly edited.
- Two-step sign-inRequired
- Idle sign-out8 hours
- Session revokeAny device
- Workspace dataScoped on the server
- Your vendor keysAES-256-GCM
| Viewer | Member | Admin | Owner | |
|---|---|---|---|---|
| Read transcripts | ||||
| Hear recordings | ||||
| Edit agents | ||||
| Publish agents | ||||
| Manage numbers | ||||
| Stream audit log |
- 09:41agent.publish · admin3f9a…c21
- 09:38workspace.mfa-policy · ownera07e…91d
- 09:12data.export · admin6c1b…e04
- 08:57data.retention-sweep · systemd42f…7aa
Each row carries the hash of the one before it, so a deleted row breaks the chain.
- Server-side scoping
Every query is scoped to the caller's workspace in the data layer — never trusted from the client.
- Role-based access
Each route is guarded by a permission; the console gates navigation and actions on the same set.
- Encrypted BYO credentials
Your carrier tokens and API keys are AES-256-GCM encrypted at rest, masked on return, and never logged.
- Verified-domain isolation
Web-chat domains and CORS both require a verified host, so branding never widens access.
- Consent before the call
The demo only rings a number after a code sent to it proves it belongs to the person asking.
Three ways in. Pick the one that fits.
Hear it on your own calls
A walkthrough on a real phone line, with your script and your language.
- A live agent on a real number
- Your script, your knowledge
- Pricing for your volume
- India and Gulf coverage, answered honestly
Ask the hard questions
Carriers, compliance, deployment, partnerships — answered by the people who built it.
- Managed, bring-your-own or white-label
- Numbers and rules, country by country
- Agency and reseller margins
- Outcome pricing for larger accounts
Build it into your product
Everything the console does, your code can do. Start a call in one request.
The platform, counted. Not described.
Every figure here was counted from the file named under it, not written by a marketer. If one of them is wrong, it is wrong in the product too.
Latest from the blog.
All postsQuestions. Answered.
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 I connect my own WhatsApp Business number?
Yes. Mirakash is a verified Tech Provider on Meta's WhatsApp Business Platform, so you connect your own number through Meta's sign-up window inside Mirakash — no developer app of your own. The account and number stay in your Meta business portfolio, Meta bills its message charges to you directly, and the same agent that answers your phone answers WhatsApp, including photos and voice notes.
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.