Written by:
Rohan Chaturvedi
|
Fact Checked by :
Namitha Sudhakar
|
According to: Editorial Policies
Either you hired a developer and waited weeks, or you spent hours inside a no-code dashboard trying to figure out logic trees and configuration menus you had never seen before.
Building a WhatsApp AI agent used to mean one of the two things above.
Neither of those is a great use of your time.
Wati MCP changes that completely. Once it is connected to Claude, you build your WhatsApp AI agent the same way you would explain it to a colleague.
You describe the use case, the tone, the escalation rules, and what your business does. Claude handles the rest.
Forget the dashboard and the developer tickets. With Wati MCP and Claude, building a WhatsApp agent that qualifies leads and handles customer support is just a conversation away.
This guide walks you through the whole thing. From setup to a live, tested agent, in about 10 minutes.
Before you build your first WhatsApp AI agent, you need two things in place.
If you are already a Wati customer with Astra enabled, you are good to go. If not, you can create a free workspace here. It takes about two minutes.
Custom MCP connectors are not available on free Claude plans. You will need a Pro, Max, Team, or Enterprise plan to connect Wati MCP and start building.
If you have both of these ready, you are set. If you still need to connect Wati MCP to Claude, the setup guide walks you through it step by step in about five minutes.
Quickly Go Through: WhatsApp MCP Server – What it is, How it Works, and What You Can Do With it
Once Wati MCP is connected, this is where the fun begins.
Open a new chat in Claude and paste this as your first message:
“You are helping me operate Wati, the agentic platform for sales and support on WhatsApp, web, and voice. You have access to my Wati workspace via MCP. When I ask you to do a task, use the Wati tools to actually do it. Ask me clarifying questions before building, not after. Ready when you are.”
This tells Claude how to work with your Wati workspace. You only need to do it once per conversation.
Now tell Claude what you want to build. Be as specific as you can. Here is an example:
“Build me a lead qualification agent for my real estate business. Pull content from [your website URL]. When a lead is hot, push them to HubSpot and notify my sales team on Slack.”
Claude will ask a few clarifying questions about tone, escalation rules, and any specific scenarios it should handle. Answer them as you would explain them to a new team member.
Once you have answered the clarifying questions, Claude gets to work.
It configures the agent, sets up the instructions, pulls from your knowledge base, and brings it to a testable state. You do not manually touch a single setting.
Ask Claude to summarize what it built and how the agent will behave. This is a good moment to catch anything you want to adjust before testing.
“Summarize the agent you just built. What will it do when a customer asks about pricing? What happens when it cannot answer a question?”
Before you go live, it helps to know exactly what you are deploying.
Here is what your WhatsApp AI agent is capable of once it is built through Wati MCP.

Your agent can handle the entire top of your sales funnel on WhatsApp. It identifies serious buyers, asks the right qualifying questions, and pushes hot leads directly to your CRM.
Your sales team only gets involved when a lead is worth their time.
The agent answers common questions, resolves straightforward issues, and knows when to escalate to a human. It does not guess.
When a customer query falls outside what the agent knows, it hands the conversation to a human team member rather than attempting a response it cannot verify.
Wati’s Astra agents are built to handle conversations across multiple languages.
No need to set up separate agents for different markets. One agent, configured once, handles all the tasks.
Your agent does not have to live on WhatsApp alone. Once built, you can deploy the same agent to web and voice channels as well.
Same instructions, same knowledge base, different channels.
Building the agent is only half the job. Before your agent talks to a real customer, you want to know that it is going to handle customer questions the right way. The good news is you do not need to script a single test manually.
Just ask Claude:
“Send a test message to the agent saying I want to know about your refund policy.”
Claude runs the test and shows you exactly how the agent responds. From there you can adjust the tone, tighten the instructions, or handle edge cases you had not thought of.
When you feel good about how it is behaving, ask Claude to run a full eval:
“Run an eval on this agent before we go live.”
Wati checks four things automatically:
You want to see a score of 95% or above across all four before deploying.
If something falls short, describe the problem to Claude and ask it to fix it. Then run the eval again.
Once your agent is live, the work does not stop. You can monitor performance, fix issues, and improve your agent week over week, all from Claude.
Most businesses know they need better customer conversations on WhatsApp. The part that holds them back is not the idea. It is the assumption that building something like this requires a developer, a dashboard, and a week of back and forth.
That assumption is outdated.
With Wati MCP and Claude, building a WhatsApp AI agent is now a conversation. You describe what you need, Claude builds it, and your agent is tested and ready to go live before most tools have finished their onboarding flow.
No. The entire process happens through a conversation in Claude. You describe what you need, and Wati MCP handles the configuration.
The setup takes about five minutes if you are not connected yet. Building and testing your first agent takes another five to ten minutes, depending on how specific your use case is.
You need a paid Claude plan. Pro, Max, Team, and Enterprise all support custom MCP connectors. Free plans do not.
The agent escalates to a human rather than guessing. Escalation handling is one of the four criteria Wati checks during the eval process before your agent goes live.
Yes. You can build agents for different use cases, markets, or channels, all from Claude. Each one goes through the same build, test, and eval process before deployment.