WhatsApp AI Agent: What You Own and Pay For

Two ways the work gets delivered

Most builders offer one of two arrangements, sometimes both.

You own and run it. You pay for the build once. The automation runs on a server or account in your name, and your team (or someone you hire later) maintains it.

They run it for you. You pay a smaller setup fee plus a monthly fee. The builder hosts the automation, watches it, fixes bugs, and makes small changes.

The first suits a business with someone technical in house who can read an error log. The second suits a business with no interest in servers. Either way, certain things must stay yours.

What must always be in your name

Whatever the arrangement, these belong to you from day one:

• Your Meta business portfolio (formerly Business Manager) and the WhatsApp Business Account inside it.
• The WhatsApp phone number. It is your customers' way of reaching you. If it sits in someone else's account, so does your customer channel.
• AI model API keys, such as an OpenAI or Google Gemini key. Usage is billed to whoever owns the key, and the key holder can switch it off.
• Where the leads end up, whether that is a Google Sheet, a CRM, or a database.

If the builder needs access, add them as a user on your accounts. Do not let them create the accounts under their own login "to save time". If you part ways later, pulling a phone number or verified business out of someone else's portfolio is slow, and sometimes you have to start again.

The server can reasonably sit with the builder under the managed model. Even then, get in writing how you would take your workflows and data with you if you leave.

The running costs, explained

A WhatsApp agent has ongoing costs that you pay, whoever built it.

Meta's message charges

Meta bills per delivered message on the WhatsApp Business Platform. The rate depends on two things: the message category and the country code of the person receiving it. The categories are:

• Marketing: offers, promotions, broadcasts.
• Utility: order updates, reminders, and other transactional messages.
• Authentication: one-time passcodes.
• Service: free-form replies to a customer who messaged you first.

Messages customers send to you are not charged. Under Meta's current pricing, each business phone number gets its first 1,000 service messages free each month. Meta updates rates on a published schedule, so check the official pricing page before you budget instead of trusting a figure from last year.

One rule shapes how your agent behaves: free-form replies are only allowed inside a 24-hour window that opens when the customer messages you. Outside that window, you can only send pre-approved templates. A good builder designs around this from the start.

Platform fees

Many builds connect through a WhatsApp Business Solution Provider such as AiSensy, Wati or Interakt instead of Meta's Cloud API directly. Meta does not charge for platform access, but providers charge their own subscription on top of Meta's message fees. Ask your builder which route they chose and why.

Hosting and AI usage

If the automation runs on a self-hosted tool such as n8n, someone pays for the server. The AI model bills per use too, and on a busy inbox it can become the largest variable cost. Ask for an estimate based on your real message volume.

Getting the WhatsApp side set up

Some of these steps can take longer than the build:

1. Business verification in your Meta business portfolio, using documents that match your legal name, address and phone number. A decision can take minutes or a couple of weeks.
2. Registering the phone number on the API. A personal WhatsApp number has to be deleted from the app first. A WhatsApp Business app number can either be deleted and moved, losing its chat history, or connected through a provider that supports Meta's "coexistence" onboarding, which keeps the app working alongside the API.
3. Display name approval. Your business name only shows in chat headers once the name is approved and the business is verified.

Start verification early. It is the most common reason a finished agent sits idle.

Testing before it talks to customers

An agent that works in a demo can still embarrass you with a real customer. A sensible order:

1. The builder tests against their own scripts and edge cases.
2. Your team tests it, asking the odd questions real customers ask.
3. A short live trial with real leads, with a person watching the conversations.
4. Go live, followed by a support period where the builder fixes what turns up.

Ask what happens when the agent does not know an answer. The safe default is a handoff to a human, never a guess about prices, stock, or policy.

What a clean handover includes

When the build is done, you should receive:

• A written scope stating what the agent does and what it does not do.
• A short demo video and a plain-language guide for your team.
• Logins shared securely, through a password manager, never pasted into a chat.
• Confirmation that every account and key listed earlier is in your name.
• An agreed support period after go-live, in writing.
• Your sign-off before the final payment.

On the managed model, also ask for a monthly summary of leads captured and anything that failed.

When a WhatsApp AI agent is a good fit, and when it is not

It fits when most enquiries arrive on WhatsApp, the same questions come up daily, and leads go cold waiting for a reply.

It is a poor fit when enquiries are rare and complex, or when nobody on your side can own the account. If your sales process already loses leads after the first reply, fix that first; an agent only speeds up what happens next.

Risks to plan for

• Lock-in: accounts in the builder's name, or workflows nobody else can read.
• Cost drift: marketing broadcasts and AI usage growing without anyone watching the bill.
• Wrong answers: an agent that invents details can cost you a customer. Limit what it is allowed to answer and log every conversation.
• Licensing: n8n's free self-hosted edition allows builders to run automations for clients, but not to let clients build their own workflows on it. If you expect your team to edit flows, raise it before the build.

FAQ

Do I need the WhatsApp Business API, or is the WhatsApp Business app enough?

For an AI agent that replies automatically and connects to other systems, you need the API (the WhatsApp Business Platform). The app is designed for a person replying by hand.

Can I keep my current WhatsApp number?

Usually. A WhatsApp Business app number can be connected through a provider that supports coexistence, so the app keeps working. Otherwise the number has to be deleted from the app first, and its chat history is lost.

Who pays Meta for messages if an agency built my agent?

You do, either directly to Meta or through your provider's invoice. The WhatsApp Business Account should be in your name under either delivery model.

What should happen if the agent cannot answer a question?

It should hand the conversation to a person on your team and tell the customer someone will follow up. Guessing should never be the fallback.

Talk it through with us

Weighing up a WhatsApp agent, or unsure what you own in the one you have? We will look at your setup and tell you plainly what we would change. Book a free 30-minute call.

AI chatbots for business