How to Add AI Customer Support to WhatsApp
Published on by
Antoni
For a lot of your customers, WhatsApp is not "a channel". It is where they already talk to their family, their landlord and the shop down the street, so it is where they will talk to you. This guide covers what they expect there, what you need before you start, the exact setup steps, how conversations move between the agent and your team, and what to measure.
Key Takeaways
- WhatsApp support is conversational by nature. Customers expect a fast, human-sounding reply, not a menu. An agent that answers in plain language fits; a scripted bot does not.
- You need three things before you start: a Facebook account, a WhatsApp Business account with a phone number, and content the agent can answer from.
- Setup is a few clicks with Meta's Embedded Signup: connect from the Channels page, log in, pick a number, set a response delay and a tone.
- The agent replies to customers, it does not message them first. Outbound templates and proactive messages are not part of the integration.
- Hand-off is the safety net. Conversations the agent cannot resolve wait in Live Desk, and your team's reply lands in the same WhatsApp chat.
Why WhatsApp matters for support
In large parts of Latin America, India, Southeast Asia, Africa and much of Europe, WhatsApp is the default way people message anyone, including businesses. If you sell there, customers will find your number and write to it whether or not you planned for it. The only question is whether someone answers.
WhatsApp also changes how customers behave. On a website chat bubble, people half-expect a form. On WhatsApp they expect a conversation, so they write the way they text: short, informal, often in three messages instead of one. That makes it a bad place for the Bot ("Reply 1 for orders, 2 for returns" is a dead end in a channel built for talking) and a very good place for an agent that understands what the customer meant and answers it.
What customers expect on WhatsApp
| What the customer expects | What that means for your setup |
|---|---|
| A reply within minutes, at any hour | Something has to answer when your team is asleep |
| To write in their own words and language | No menus; the agent needs to read intent, not keywords |
| Short answers they can read on a phone | Content written for chat, not pasted from a policy PDF |
| To not repeat themselves | Whoever picks up next needs the full history |
| A real person when it matters | A clear hand-off path, and a human reply in the same chat |
Every row is a place where a scripted bot quietly loses a customer, and silent customers are lost revenue.
What you need before you start
The WhatsApp integration docs list three prerequisites. Have them ready and the technical part takes minutes.
| Prerequisite | Notes |
|---|---|
| A Facebook account | Used to log in to Meta's signup flow |
| A WhatsApp Business account | You can create one during setup if you do not have one |
| A phone number for WhatsApp Business | Use a dedicated, professional business number |
Give the agent something to answer from
The item that is not on the prerequisites list, and matters more than any of them, is content. An agent does not learn on its own; it searches your knowledge base and answers from what it finds. Before you connect WhatsApp, make sure it has read the things customers will ask about. The training guide has the details; the short version:
- Import your website. Paste your address in the Add box and import the whole site. Pricing, help and FAQ pages get read first.
- Add FAQs for the top questions. Write the question the way a customer would type it on a phone ("where is my order", "how do i cancel") and keep the answer short. FAQs produce the most precise answers.
- Add policies as files or text snippets. Refund rules, shipping times, opening hours. Be specific: "Refunds take 5 to 7 business days" beats "We process refunds promptly".
- Test with Ask your agent. Ask what you expect to hear on WhatsApp and check the answer and the items it was built from.
Setting up FutureBase on WhatsApp
Step 1: Start the connection
- Open Channels in your dashboard and choose Add channel.
- Find WhatsApp in the channel library and choose Connect.
- Click Connect with WhatsApp.
Step 2: Complete Meta's signup
A popup opens with Meta's Embedded Signup:
- Log in with your Facebook account.
- Select an existing WhatsApp Business account, or create one.
- Add or verify the phone number you want to use.
- Grant the requested permissions.
Quick setup configures the webhook for you. If the popup never opened, your browser blocked it; allow popups and click again.
Step 3: Set the response delay and tone
After connecting you land on the channel settings:
- Response delay is how long the agent waits before answering, from 0 to 30 seconds, default 2. It exists for exactly how people use WhatsApp: "hi", then "i ordered last week", then "nothing arrived", as three messages. A delay of 2 to 5 seconds lets the agent batch them into one reply instead of answering each fragment.
- Personality sets the tone of voice. It is chosen once in your agent's Settings under Tone of voice and applies to every channel, WhatsApp included. More on choosing one below.
Click Save Settings.
Step 4: Send a test message
Message your WhatsApp Business number from your own phone. The agent should reply from your knowledge base. Try the awkward cases too: a typo-ridden question, two questions in one message, and one you know is not covered, so you see hand-off from the customer's side.
Manual setup, if you run your own Meta app
The docs also describe a manual path: create a Business-type app in the Meta Developer Console, add the WhatsApp product, copy the Phone Number ID and an access token, and enter both under the Manual Setup tab. You then get a Callback URL and a Verify Token to paste into your app's WhatsApp webhook configuration, where you also subscribe to the messages field.
Two things trip people up: temporary tokens expire after 24 hours, so use a System User token with the whatsapp_business_messaging permission for production, and the verify token is case-sensitive.
What the integration does and does not do
| Supported | Not supported |
|---|---|
| Private one-to-one chats to your business number | WhatsApp groups |
| Text messages | Images, documents and voice notes (acknowledged, not processed) |
| Replies to messages customers send | Proactive outbound messages |
| Context from up to 50 previous messages | Pre-approved message templates |
| Automatic read receipts | Multiple numbers on one integration |
On the outbound limitation: WhatsApp allows free-form replies within 24 hours of a customer's last message, and anything outside that window needs a template. Because the agent only ever answers incoming messages, it stays inside the window by design.
How the agent handles a WhatsApp conversation
Once connected, every message follows the same flow:
- A customer sends a message to your WhatsApp Business number.
- WhatsApp forwards it to the agent via webhook, verified with Meta's signature header.
- The agent reads the message together with the conversation history.
- It builds an answer from your knowledge base.
- The reply goes back to the customer in the same chat, and the message is marked as read.
The history is what separates this from the Bot. The agent keeps context from up to 50 previous messages, so "and what about the blue one?" works, and a customer who comes back the next day does not start from zero. Every conversation also shows up in your dashboard, so nothing on WhatsApp happens out of sight.
Handing off to your team
No agent resolves everything, and the ones that pretend to are how you end up with a bot. The job is to make the hand-off clean.
Turn it on. Open Actions, then Hand off to your team. There you decide whether hand-off happens (with it off, a question the agent cannot answer simply ends there), who hears about it, and what the customer reads when a person takes over. Hand-off is free on every plan.
Where it lands. Every hand-off waits in Live Desk. You can also get an email, or a thread in Slack or Discord that your team replies from. Live Desk shows how long each customer has waited, amber after 5 minutes and red after 30.
How a reply gets back to WhatsApp. A teammate writes in Live Desk and sends. That takes over the conversation, the agent goes quiet, and the reply arrives in the customer's WhatsApp chat. The customer never leaves the app, never gets a ticket number, and never repeats themselves, because the person replying can see everything the customer said and everything the agent already tried.
Giving it back. Once the person has done the thing only a person could do, they choose Give back to AI and the agent answers the next message. A closed conversation reopens on its own when the customer writes again.
Different languages. A customer who writes in Portuguese keeps reading and writing in Portuguese. Your team turns on Translate in the conversation header to read the thread in their own language and reply in it; the reply goes out in the customer's. For a number serving several countries, that is the difference between one support team and three.
Tone tips for WhatsApp
The agent's wording comes from the personality you pick and the content it answers from. Both need to suit a phone screen.
Pick a personality that reads like a text. Friendly (the default) or Casual usually fits consumer brands; Professional fits B2B; Supportive suits traffic that skews towards frustrated customers chasing orders. Personality also shapes the hand-off message, so the "let me get a colleague" moment sounds like the rest of the chat.
Write knowledge for chat, not for print. A 600-word policy page produces long answers. A short FAQ produces a short one. For your top questions, write the FAQ answer the way you would text it: the fact, the one condition that matters, and what to do next.
One idea per message. Customers on WhatsApp skim. If an answer needs three steps, write three short lines, not a paragraph.
Cover what the agent cannot do. Add an FAQ for "can I send you a photo" that says a person will look at it, so the agent says so instead of ignoring the image.
What to measure
You need a few numbers that tell you what to fix next, looked at weekly and filtered to WhatsApp (Live Desk's channel menu narrows the list to one channel).
| Measure | How to read it | What to do about it |
|---|---|---|
| Hand-off rate | Share of WhatsApp conversations that reach Live Desk | Read the hand-off reasons; most point at a missing FAQ |
| Wait time | How long handed-off customers wait for a person | Rows keep turning red: add Slack or Discord notifications, or people |
| Unanswered questions | Questions the agent could not answer, from the Conversations tab | Add the content, then re-test with Ask your agent |
| Repeat contacts | Customers writing back about the same thing | Usually a vague answer; make the FAQ specific |
| After-hours share | Conversations handled while nobody was online | The clearest proof of value to show your team |
The number that matters is your own trend: hand-off rate falling as content improves, wait time holding steady as volume grows.
Frequently asked questions
Do I need a developer to add AI support to WhatsApp?
Not for the standard path. FutureBase uses Meta's Embedded Signup, so you connect WhatsApp from the Channels page by logging in with Facebook, picking or creating a WhatsApp Business account and verifying a phone number. A manual path with your own Meta app and webhook exists for teams that want it, but it is optional.
Can the AI agent message customers first on WhatsApp?
No. The integration replies to messages customers send to your WhatsApp Business number. Proactive outbound messaging and pre-approved message templates are not supported, which also keeps you inside WhatsApp's 24-hour customer service window, since every reply follows a customer message.
What happens when the agent cannot answer a WhatsApp question?
With hand-off turned on, the conversation waits in Live Desk, and optionally reaches your team by email or as a Slack or Discord thread. A teammate replies from Live Desk and the reply lands in the same WhatsApp chat. When the person is done, they give the conversation back to the agent.
Does the agent handle voice notes and images on WhatsApp?
It responds to text messages. Images, documents and voice notes are acknowledged but not processed, so if your customers often send photos of a problem, plan for a person to pick those up from Live Desk.
Ready to answer WhatsApp at 2am without staffing it? Start free with FutureBase and put an agent on your WhatsApp Business number: trained on your docs, handing off to your team with full context, and replying in your customer's language. See how teams use it for 24/7 customer support and multilingual customer support.
