It's 22:10 on a Sunday. Someone messages your shoe shop on WhatsApp: "Do you have the black ones in 38, and can I send them back if they don't fit?" Two questions, both answered on your website somewhere, both waiting until Monday.
To set up an AI agent for WhatsApp, you connect your WhatsApp Business number to an inbox that supports the Cloud API, give the agent your business information and a clear job, let it qualify and book, and decide in advance when it hands over to a person. In Wexio none of that needs code. The part that decides whether it works is the last one.
Before you connect: what WhatsApp requires, and the 2026 rule on AI
An AI agent runs on the official WhatsApp Business Platform (the Cloud API), not on the phone app. Tools that promise to automate the regular app by scraping it are the quickest route I know to a banned number. Skip them.
You need four things:
- A Meta Business account with a WhatsApp Business Account.
- A phone number registered on that account for the Cloud API.
- Admin access to the Meta Business account.
- Opt-in from anyone you will message first. People who write to you are fine. For people you contact first, read Meta's WhatsApp Business Policy.
One 2026 change is worth knowing. Meta updated its Business Solution Terms so that general-purpose AI assistants can't be offered over the WhatsApp Business API, effective 15 January 2026. An agent that answers questions about your own shop, your bookings and your returns is customer service, which is the thing the platform exists for. A bot that will chat about anything is the thing Meta closed the door on. Brief your agent accordingly, and we'll get to how below.
Not sure whether you should move from the free app at all? The free WhatsApp Business API guide covers what you can and can't get without paying.
Connect your number in Wexio
I'm the founder of Wexio, so this is the flow I know best. In the app, go to Settings, then Integrations, click Add Integration, open Channels and choose WhatsApp. Click Connect with WhatsApp Business, log in to Meta in the window that opens, approve the permissions and pick your business and number. If your Meta account has several numbers, you choose which one.
The webhook is set up for you and your message templates sync in the background. The WhatsApp connection guide has the screen-by-screen detail.
Two checks before you move on:
- A number can be active with one provider at a time. If messages don't arrive, it's usually still attached to a previous one.
- Only Owners and Admins can connect a channel.
Then send a message from your personal phone. It should show up in the inbox within seconds. If it doesn't, stop here and fix it. Everything after this assumes messages flow.
The same inbox also holds web chat, Instagram DMs, Telegram, Viber and email, so you aren't building a WhatsApp-only island. You can run the same agent on the other channels later and decide per channel.
Write the agent's job, and its limits
Create an assistant in the AI settings, choose the language it answers in, and give it a name customers will see. Keep internal names out of it. When a customer asks "am I talking to a person?", the agent should say it's an assistant for your business. Customers forgive a bot that's upfront far more readily than one pretending to be "Anna from support".
Then the instructions. This is where most people write "be friendly and helpful" and wonder why the agent drifts. Write a job description instead. For the shoe shop it might say:
- You answer questions about this shop's products, sizes, delivery and returns, using only the information provided.
- If you don't have the answer, say so and offer to bring in a person. Never guess a stock level or a delivery date.
- Do not discuss topics unrelated to the shop.
- Never promise a refund. A person decides.
That third line does double duty. It keeps the agent on the customer-service side of Meta's 2026 rule, and it stops the agent from becoming a free general chatbot at your expense.
Teach it what your team already answers
The agent is only as good as what it can read. Put in what you have: products and sizing notes, delivery times, the returns and cancellation policy, opening hours, and the ten questions your team types most. Copy those from your inbox, word for word, including the way your team phrases the answer. That's your tone of voice, already written.
Keep each document short and about one topic. "Returns policy" as its own page will be found more reliably than page 14 of a brochure. If you're in e-commerce, fashion or footwear, the sizing and returns documents will do most of the work. If you're a consultant or advisor, the equivalents are what you do, who it's for, how a first call works and what it costs to get started.
Voice notes and photos
A lot of WhatsApp customers send voice notes and photos instead of typing. Before launch, check how your agent handles them: send a voice note and a photo of a scuffed sole from your own phone and see what comes back. If the agent can't read something, it should say so and route to a person, not answer as if it had understood.
Let it qualify and book, not just answer
Answering is half the job. On WhatsApp the messages that make money are "can I book Thursday?" and "which one should I get?". A chatbot that only recites FAQs will leave those to your team.
Qualify with questions you'd ask anyway
Qualifying doesn't need a form. Put it in the instructions as a short sequence the agent follows when someone shows buying interest:
- For a shoe or fashion shop: what they're looking for, their size, whether it's a gift, and when they need it.
- For a cosmetics or DTC brand: skin or hair type, what they use now, and what they want to change.
- For a consultant or advisor: what they need help with, how urgent it is, and whether they've worked with someone before.
Two or three questions, asked one at a time in the customer's language, are enough. The conversation lives on the contact in the CRM people view, so whoever picks it up later sees the answers without asking again.
Book straight into the calendar
Wexio's agent can book through your connected calendar, Google Calendar among others, and the web widget can do the same. Connect your calendar in the integrations settings and the agent can offer free slots and confirm a booking inside the WhatsApp chat. For an advisor, that's the whole sales process: a qualified question, then a slot. For a retailer, it might be a fitting appointment or a call with a stylist.
I'd keep anything that moves money on a human decision. The agent can take the details of a return request. A person decides on the refund. That's the point of AI that knows its place: it answers everyone, and it answers to you.
Two ways to switch it on
Option A, the channel answers with the assistant. Open the WhatsApp channel in Settings, then Integrations, go to its AI tab and set AI auto-reply to Assistant. Every new conversation gets the agent. Use Rules if different people should get different assistants, for example a sales assistant for new contacts and a support one for existing customers. It's the quickest setup and fine for a small shop.
Option B, the agent lives inside a flow. Build it in the flow builder: a First Visit or Catch All trigger, then an AI Agent card with your instructions and a few route buttons, such as "Ready to book", "Order or return problem" and "Talk to a person". The agent holds the conversation and leaves through the button whose label fits, so name them for the situation, not for the tool. Each route can lead anywhere: a booking confirmation, a question card that collects an order number, or a handoff.
I pick Option B whenever a clear process sits behind the chat. If you want worked examples of flows, see AI agents for customer messaging.
Hand the chat to the right person without a loop
The worst WhatsApp bot experience is the loop. The customer types "person" three times and gets the bot three times. I'd build the exit before I polish a single answer, because it's the part customers remember.
Route by situation, not by guesswork
In a flow, send each route button to a different place. "Talk to a person" and "Order or return problem" can both land on an Assign Operator card, but you may want them to land on different people: returns to whoever handles the warehouse, sales questions to the owner.
The Assign Operator card has an auto-assign mode for the case where you don't care who answers. It looks at who is online right now, gives the chat to the person with the lightest load, and if nobody is online it falls back to a teammate you name in advance. Name that fallback. A chat nobody owns at 22:10 on a Sunday is the one that turns into a bad review.
What happens when the person joins
When an operator joins the conversation, the AI stops answering that customer. When it's resolved, the agent can pick up again next time. The operator sees the whole thread, including what the agent said, so the customer doesn't repeat themselves. That one detail, not retelling the story, is most of what "a good handoff" means to a customer.
If more than one person will be answering, agree who looks at what before you launch. Who watches the inbox on weekends, who owns returns, who owns "big order" enquiries. The software can route, but it can't decide that for you.
Write the triggers for handoff down
Put the handoff rules in the instructions in plain words. These are the ones I'd start with:
- The customer asks for a person, once. Don't make them ask twice.
- The customer is upset, or mentions a damaged or wrong item.
- The question involves money: refunds, discounts, price changes.
- The agent has no answer in the information it was given.
After a week of real conversations you'll see which of these fired too early and which too late, and you can adjust.
The 24-hour window, templates and what Meta charges
These are WhatsApp's rules, not Wexio's, and they shape what an agent can do.
The 24-hour window
When a customer messages you, you can reply freely for 24 hours. After that, you can only send a pre-approved message template. The agent works inside the window, which is most of its work. Reminders, follow-ups and anything you start yourself go out as templates, from a WhatsApp template card in a flow, or as a broadcast to people who opted in.
Cost on the Meta side
Since 1 July 2025, Meta charges per delivered template message, by category and country, instead of per conversation. Free-form replies inside the customer service window aren't charged, which is why an agent answering inbound questions is cheap on Meta's side. The current rate table is on Meta's pricing page, and I've explained the model in WhatsApp Business API pricing in 2026. For Wexio's own plans, see pricing.
Groups stay manual
If your number sits in WhatsApp groups, the agent won't answer there. AI auto-reply and flows don't run in groups in Wexio, by design. Someone in a group asking "is the bot reading this?" is reason enough.
Who picks the provider
If you're comparing platforms before committing, the WhatsApp Business API providers comparison sets out what to look at. The question I'd ask every one: what happens when a person needs to take over?
Test on real messages before it meets a customer
Use the assistant's test chat first. Paste in real messages from your inbox, including the messy ones with typos, half sentences and voice-note-style rambling. "Is this in 38" with no product name is exactly what your customers write.
Test these on purpose:
- A question the agent has the answer to. It should answer shortly and correctly.
- A question it doesn't have the answer to. It should say so and offer a person, not make something up.
- A request for a person. It should hand off on the first ask.
- A topic outside your business. It should politely decline.
- A booking request. It should offer real free slots and confirm.
Then go live on one job. For most shops that's FAQ plus returns questions, with handoff for anything involving money. For advisors it's qualify plus book. Add more once that's calm.
After a week, read a sample of real conversations and look for three things. Questions it couldn't answer: add a document. Handoffs that came too late: tighten the instructions. Handoffs that weren't needed: loosen them. That reading session is worth more than any amount of upfront polishing.
You can start with the free trial at app.wexio.io and connect your number there, so you can see real messages arrive before you decide anything.
FAQ
Can I put an AI agent on my existing WhatsApp number?
Yes, if the number is registered on the WhatsApp Cloud API through your Meta Business account. A number that's only used in the free Business app needs to be set up on the API first, and it can only be active with one provider at a time.
Is a WhatsApp AI agent the same as a WhatsApp chatbot?
Not quite. A chatbot usually follows a fixed menu: press 1 for hours, press 2 for returns. An AI agent reads what the customer actually wrote, answers from your information, asks follow-up questions, books, and hands off when it should. In Wexio you can combine both: a flow gives the structure and the agent handles the open conversation inside it.
Does the same agent work on Instagram, Telegram and my website?
Yes. WhatsApp, Instagram DMs, Telegram, Viber, email and the web chat widget all feed one inbox, and you choose per channel whether the agent answers. Facebook Messenger is not supported.
Can the agent send the first message?
Only through an approved template, like any business-initiated WhatsApp message, and only to people who opted in. Use a template card in a flow or a broadcast.
What happens when the agent doesn't know the answer?
With clear instructions, it says so and routes to a person. An agent that guesses instead is an instructions problem, and the transcripts will show you where it happened.




