Six jobs.
One agent.
No new headcount.
Answering questions is where it starts. Below: the channels it works on, the actions it can take in your systems, the moment a human steps in, and the outreach, bookings and payments it handles on its own.
Three places your customers already are.
A phone number that answers in seconds, your WhatsApp Business number, and a chat widget that installs with one script tag. All three serve the same agent, so the answer is the same wherever they ask.
- Answers calls 24/7 in 10 Indian languages plus English, and follows a caller who switches mid-sentence
- Official WhatsApp Business — reads photos, button taps and shared locations
- Website widget that matches your brand automatically, with photo upload
- Update one knowledge source and all three are correct
Email arrives as ticket replies and appointment confirmations rather than as a conversational channel — worth knowing before you plan around it.
“When will my order arrive?”
One knowledge base. One tone. Three renderings.
It can look things up. It can also change them.
Point it at your website, your documents and your own API. Then let it do the work: check a live order, reschedule a delivery, apply a credit. Actions are a separate permission with their own guardrails — and a switch that withholds them entirely.
- Learns from your site, PDFs, spreadsheets, pasted notes, your API or an MCP server
- Live lookups mid-answer — real order status, not a cached guess
- Action tools confirm intent first and never claim success before your system returns it
- Turn actions off and the agent is never even told they exist
Every action is audited with the agent, channel, tool and outcome — and deliberately without the payload, so there's no second copy of customer data.
When it needs a person, it gets one.
Your team can take over a chat, a WhatsApp thread or a live phone call. The AI steps out, your teammate steps in with the full history and an AI-written summary, and hands it back when they're done. Anything left over becomes a ticket with a real clock on it.
- Mid-call takeover — the customer hears hold music, then your agent's voice
- Support hours, so the AI never offers a person who isn't working
- A sensitivity dial for how eagerly it escalates
- Tickets with SLA deadlines, assignment, internal notes and AI draft replies
Reach a whole list — and get paid by it.
Broadcast an approved WhatsApp template, or set an AI agent calling every person on the list for a real conversation. Every recipient comes back with an outcome. Duesly goes further and collects your recurring payments for you.
- WhatsApp broadcasts and AI call batches, up to 50,000 recipients
- Per-recipient outcomes you can filter and export
- Opt-outs, quiet hours and frequency caps enforced before every send
- Duesly: recurring reminders with payment links that settle themselves
Quiet hours and frequency caps applied automatically.
It fills the diary without double-booking you.
The agent checks real availability, offers up to three times, and books only the one the customer chooses. Bookings mirror into Google Calendar, and whatever is already in your calendar blocks the slot.
- Books over voice, WhatsApp and website chat
- Two-way Google Calendar sync — your existing meetings block availability
- Opening hours, durations, buffers, notice periods and closed dates
- WhatsApp and email reminders, and no-show tracking
“Can someone look at the AC on Tuesday?”
A real API, and docs your coding agent can read.
Send messages, place and end calls, read transcripts, open tickets, upsert contacts and drive campaigns from your own systems. Fourteen webhook events push the other way. And one command points Claude Code or Cursor at the actual contract.
- REST API with scoped keys, idempotency and cursor pagination
- 14 signed webhook events with retries, a delivery log and console replay
- Test and live environments, so you can integrate without texting a real customer
- MCP server, llms.txt and an OpenAPI 3.1 spec generated from the running service
{
"event": "lead.created",
"data": {
"name": "Anita Rao",
"phone": "+919876543210",
"source": "web-chat"
}
}The parts nobody demos, that decide whether it survives month three.
No add-ons, no separate SKUs. These come with the product.
One inbox
Calls, WhatsApp and chat in one place, tagged by channel, full transcripts.
Customer memory
Remembers a person across channels — and forgets on request, per contact.
Versions & rollback
Publish freezes a version. Roll back to exactly the agent that worked.
10 Indian languages plus English
Hindi, Bengali, Marathi, Tamil, Telugu, Gujarati, Kannada, Malayalam, Punjabi, Odia, English.
Analytics
Volume, channel mix and voice performance across every deployment.
Per-channel tone
One agent, brisker on a call than in writing — same knowledge either way.
Boring where it should be boring.
Who can do what, where your data sits, and exactly what it costs when you go past your plan.
Roles that differ
Owner, admin and member. A member works the day without changing how the product behaves.
Workspace isolation
Every read and write filtered by workspace first. No cross-workspace sharing exists.
Scoped API keys
Eleven scopes, read-only by default, hashed at rest, roll with grace or revoke instantly.
Honest metering
₹6/min voice, ₹2 per extra conversation. Prepaid credits, valid 12 months, GST on top-up.
Want the whole contract? Every limit, error and guarantee is written down — 66 pages of it, public, no signup.
Ready to hand over the routine?
Deploy Adya across calls, WhatsApp and your website in days — no engineering effort required.