What you can build
The things businesses ship on Amomic-AI today, what each one takes, which plan it needs, and an honest list of what this is not for.
This page is for deciding whether Amomic-AI fits. Every scenario below is built from things that ship today. Each one names the plan it needs and the pages that build it, so you can skim the shape and then go deep on yours.
Underneath all of them is one model: you build one agent, give it knowledge and tools, and deploy it onto each channel where customers reach you: your website, your WhatsApp number, your phone line. Every conversation lands in one Inbox and every person in one contact directory. How it fits together explains the model on one page.
Plans are summarised here; Plans & limits has the full table.
Answer customers #
A support agent on your website and WhatsApp #
Plan: Free for the website; Starter or above for WhatsApp.
The most common first build. Point a knowledge base at your help centre, upload the PDFs that were never turned into web pages, and paste the exceptions your team knows by heart. Write a purpose that says what the agent owns and what it hands off. Then deploy the same agent twice: as a widget on your site and on your WhatsApp Business number. When your warranty terms change, you update one source and both channels answer correctly from the next sync.
The work is mostly in the knowledge. Expect an hour on sources and testing, and a few minutes on everything else.
→ Quickstart · Knowledge bases · Web chat · Set up WhatsApp · Reply modes
An AI receptionist on your phone line #
Plan: Starter or above. In India, your business is verified once before you get a number.
Your number rings and the agent answers. Call language decides what callers may speak: English only, Hindi + English, or All Indian languages, which follows the caller across Hindi, English and nine other Indian languages. You write the opening line callers hear. Common questions are answered instantly from a fact sheet built from your knowledge, and the agent searches for anything more specific.
Every call gets a transcript, a call outcome with a summary and next step, and optionally a recording. Add a few questions on the number's Outcomes tab, such as why people call or whether it was sorted out, and the answers are added up on that number's dashboard.
→ How voice works · Get a number · Languages · Outcomes on incoming calls
Appointment booking #
Plan: every plan. The Calendar is included; the agent books on whichever channels it is deployed to.
Set up a booking calendar with your opening hours, slot length and how many bookings share a time. Turn on Book appointments on the agent's Tools tab and the agent offers only free slots, takes the booking in the conversation, and sends confirmations and reminders. Your team sees every booking on Calendar and can book on a customer's behalf. Connect Google Calendar so busy time there blocks slots here and new bookings appear there.
→ Appointments and calendars · Connect Google Calendar · Tools and actions
Bring in your team when it matters #
The agent's most useful skill is knowing when to stop.
Live handoff, during your live hours: on web chat, WhatsApp or a phone call, the agent passes the customer to whoever is available in Live support, with an AI-written summary so the customer doesn't repeat themselves. On WhatsApp, anyone can also take over a conversation from the Inbox.
Tickets, for everything else: when your team is closed or nobody picks up in time, the agent opens a ticket, matches the customer to your contacts, and reads back a reference such as AM-4F91C2E0. Your team works it in Tickets, replies reach the customer on the channel they came from, and your backend can hear about it on the ticket.created webhook.
→ Human handoff · Tickets · Escalate to a ticket
Reach out to customers #
WhatsApp broadcasts and calling campaigns #
Plan: Growth or above. Admins and owners.
A WhatsApp broadcast sends an approved template to tagged contacts or a CSV. A call batch has an agent call each person on the list with a script you write, using per-person details from your CSV, and records what each person said on an outcome form you design. Both run inside a sending window in your workspace's time zone, respect opt-outs and frequency caps, and report every recipient's result.
Veloria Home, the example business in these docs, uses a call batch to remind customers about annual maintenance contract renewals.
→ Campaigns · Create a campaign · Call scripts · Call outcomes
Recurring payment reminders with Duesly #
Plan: Growth or above.
For customers who pay you on a cycle. Add each customer once with their amount and how often they pay. Duesly raises each payment when it falls due, reminds the customer on WhatsApp with a way to pay, follows up, and stops after two follow-ups. Payments are collected through your own UPI or QR, or through a connected payment account.
Connect your own systems #
All of these use the REST API with a key from Developers, on any plan. Keys are for servers only.
Order and delivery updates from your backend #
Your systems know when an order ships. Your backend calls POST /messages with an approved WhatsApp template and the values to fill in. A shipping update almost always falls outside WhatsApp's 24-hour window, so a template is required: a free-form send there is refused with 409 and session_window_closed. Send an Idempotency-Key built from your order id, and a retry after a timeout returns the original response instead of messaging the customer twice.
If the customer replies, the window opens and your agent takes the conversation from there.
→ Order-shipped update · Sending messages · Templates · The 24-hour window
A call triggered by your CRM #
Your CRM knows a policy expires in seven days. It calls POST /calls with the number, the caller ID to use, and a short script or purpose. The agent opens by identifying your business and saying it is a virtual assistant, then holds a real conversation. Ask for answers with capture and read them back from the call or the call.outcome webhook. A 201 means the call is ringing, not answered.
Outbound calling over the API is your compliance decision
The platform enforces operational guards: the caller ID must be a number your workspace owns with an agent on it, and concurrent calls are capped per workspace. Calls you place through the API are not checked against do-not-call registries and are not held to calling hours. Whether and when to call a person is your decision. Campaign call batches, by contrast, only dial inside their calling window. See Calling responsibly.
→ Trigger a call from your CRM · Placing calls · Call outcomes API
Conversations in your warehouse #
A scheduled job walks GET /conversations with a cursor, fetches the transcript for anything new, and writes both. Transcripts contain only customer and agent messages, not the internal record of what the agent looked up. A key with only conversations:read is all it needs.
→ Sync conversations · Conversations API · Pagination
What this is not for #
Worth saying plainly, because finding out in week three is expensive.
It is not a bulk blaster. Campaigns send approved WhatsApp templates and agent calls to a list, inside a sending window, with opt-outs, frequency caps, plan limits and audience checks. They don't bypass Meta's template approval or those controls, and the API has no generic batch-send shortcut. If your plan depends on forcing promotional volume through an unverified list, this is the wrong tool.
It is not your CRM. Contacts hold name, phone, email, WhatsApp ID, tags, per-channel consent, a cross-channel activity timeline and what the agent remembers about the person. There are no deals, pipelines or stages, and no merge for duplicates. Your CRM stays the system of record; POST /contacts is the seam between the two.
One agent, one job. An agent can have its own purpose and instructions for Phone, WhatsApp and Web chat, but its knowledge and tools are shared across them. Two genuinely different jobs, such as support and sales, need two agents.
Where to start #
Build the first one
Quickstart: from sign-up to an agent answering on your website.
Find your setup path
Setup directory: what each goal needs and how to verify it.
Wire up your backend
Your first API call: a key, a check, and a real message.
Look up a word
Glossary: every term in these docs, with a link.