WhatsApp business automation, built and maintained
A WhatsApp business agent answers your customers on the channel they already use, at the speed they already expect. It runs on the official WhatsApp Business API rather than someone's phone, holds the whole conversation history in one place, answers the repetitive questions, takes the order or the booking, and hands the conversation to a human the moment it stops being routine.
What problem this solves
“We answer WhatsApp from three personal phones, nobody knows what was promised to whom, and at eight in the evening nobody replies at all.”
Most businesses that sell by conversation are running WhatsApp on personal phones. Three people, three devices, three partial versions of what was promised to whom, and no record that survives someone leaving. At eight in the evening nobody replies at all, and a customer who waits long enough goes and messages a competitor instead.
The measurement problem is as expensive as the response problem. When conversations live on personal phones there is no conversion rate, no first-response time, no way to tell which questions come up often enough to be worth answering once and for all.
Moving to the official API fixes the record-keeping and the after-hours gap at the same time, and it is the only version that survives the business growing past the people currently holding the phones.
Replies in seconds around the clock, one shared history instead of three phones, and conversation-to-sale you can actually measure.
Market contextIn LatAm WhatsApp isn’t a channel, it is the channel — around 530M active users in the region and close to 72% of conversational commerce. Note: since January 2026 Meta prohibits general-purpose bots on the WhatsApp API, so we build defined-scope business agents only.Source: Aurora, WhatsApp Ecommerce Statistics in Latin America
What runs, end to end
- 01Message arrives
- 02Intent + CRM context
- 03Answer, book or charge
- 04Escalate to a person
- 05Logged in the CRM
Who this is for
Any business that sells by conversation rather than by checkout: retail and e-commerce with a catalog worth asking about, clinics and salons taking bookings, services quoting per job, and anyone whose customers open WhatsApp before they open a browser.
The regional fit is sharpest in Latin America and Spain, where WhatsApp is not one channel among several but the channel. For a US business it fits the Hispanic market and any customer base that already messages rather than calls.
Note the constraint, because it changes what we will build: since January 2026 Meta prohibits general-purpose bots on the WhatsApp API. We build defined-scope business agents — support, catalog, orders, scheduling, handoff. An agent that will answer anything about anything is not something we can ship on this channel.
- Sectors
- Any business that sells by conversation
- Strongest fit
- LatAmSpain
What it costs
| Size | Build | Monthly |
|---|---|---|
| Micro | Build$650–$1,300 | Monthly$180–$350/mo |
| Small business | Build$1,600–$3,200 | Monthly$450–$900/mo |
| Mid-market | Build$4,000–$7,500 | Monthly$1,000–$2,000/mo |
All prices are in US dollars. Out-of-scope work is $35–$60/hour. AI usage is billed at cost plus 20%, or you bring your own API key.
See it running
An interactive simulation, no signup and nothing to install. It uses a fictional business and made-up data, and says so on the page — what is real is the flow, the handoffs and the systems it touches.
Open the demo — A business agent on WhatsAppFrequently asked questions
- Do we need an official WhatsApp Business API account?
- Yes, and we set it up as part of the build — number verification, business verification with Meta, and the message templates that have to be approved before you can start a conversation. It is the step most likely to add calendar days, so we start it first.
- What does WhatsApp itself charge?
- Meta bills per conversation, and the rate depends on the country and on who started it. It is billed at cost plus 20% or directly to your own account. We model it against your real message volume on the audit call, because the difference between markets is large enough that an average would mislead you.
- Can it take payment?
- It can send a payment link and reconcile the result, which covers most cases. Native in-chat payment depends on your market and on what Meta has enabled there. We scope whichever is actually available to you rather than the one that demos better.
- What happens to the conversations our team is already having?
- They move into a shared inbox — Chatwoot in the usual build — so history stops living on personal phones. Your team keeps replying as themselves; what changes is that the agent handles the repetitive share and everything is on one record.
- How do we stop it saying something wrong?
- Scope, not hope. The agent answers from your own documentation and catalog, with a confidence check before it replies and a hard handoff when it is unsure. Every conversation is logged, so the first weeks are where you tighten it against real questions rather than imagined ones.
Your customers already message you on WhatsApp. The question is how many give up waiting before anyone reads it.
Figures on this page are public industry benchmarks, not results measured on Amagenon client accounts. We will size the numbers against your own data on the audit call.
Find out what your process is actually costing you
A 30-minute call and a one-page report on the three highest-value automations in your business. Free while we build our first case studies.