WhatsApp Chatbot for Business: Monthly SaaS vs Owning It

Short answer: rent a WhatsApp chatbot platform if what you need is broadcasts, a shared team inbox and menu-style flows. Own the bot if it has to answer questions from your own documents or act on your own systems. Either way you pay Meta for messages. The decision is about what you pay on top of that, every month, for as long as the bot runs.

Every page that ranks for “WhatsApp chatbot” in India is written by a company selling a subscription to one, so none of them works through the comparison below. I build these, so I have a bias too. I have tried to make it visible by saying where renting is the better call. All prices were checked on the vendors' own pricing pages on 23 October 2026, and they change, so check them again before you sign anything.

The cost nobody avoids: Meta's per-message fees

A real WhatsApp chatbot runs on the WhatsApp Business Platform (the API), not the free WhatsApp Business app. Since 1 July 2025 Meta charges per delivered message, priced by category and by the recipient's country. Indian businesses can now be billed in rupees, and Meta requires accounts billed in India to move to INR by 31 December 2026.

• Marketing templates (offers, broadcasts) are the expensive category, a little under a rupee each on Meta's INR rate card.
• Utility (order updates) and authentication (OTPs) cost a fraction of that.
• Service messages, your replies when a customer writes to you first, are what a support chatbot mostly sends. From 1 October 2026 each business number gets 1,000 free service messages a month, and the 1,001st is charged.
• Conversations that start from a Click-to-WhatsApp ad open a free window of up to seven days.

A bot that mainly answers incoming questions sits largely inside the cheap or free categories. A bot that mainly sends promotions does not, and no platform choice changes that.

What the subscription platforms add

Platforms such as WATI and Interakt are Business Solution Providers: they connect you to the API and give you a dashboard. You pay a plan fee, and on top of Meta's rate, often a per-message markup.

The markup is easiest to see on Interakt, which publishes its per-message rates: a service message is ₹0.128 on Growth, against ₹0.115, the utility and authentication rate on Meta's INR rate card for India. Only Interakt's Enterprise plan says it has no markup. WATI's page says per-message charges vary by category and links its rate card separately.

None of this is a scandal. A team inbox, a broadcast scheduler, template management and a Shopify connector are real software, and building them yourself would cost far more than the subscription.

Three years of each, worked through

An illustration, not a client: a business that wants an AI assistant answering customer questions on WhatsApp, with a couple of staff handing over to a person when the bot cannot help. Plan fees only, before GST and before Meta's charges, which are the same in every column.

At current exchange rates the build costs about what one year of either plan does, so the owned bot breaks even around the end of the first year and is ahead from then on. The Interakt column is also the optimistic one: 100 AI messages a month is a few a day, so any real volume adds the per-message AI charge on top. An owned bot's model usage depends on your volume and the model you choose; for short answers grounded in a few documents it is small, and it can be estimated before you commit.

When renting is the right answer

If the job is broadcasts to a customer list, abandoned-cart reminders from Shopify, catalogues and a shared inbox for five people, rent a platform. That is exactly what they are built for, it works on day one, and building it yourself would be paying to recreate a product that already exists. The same goes for a menu bot (press 1 for timings, 2 for location) with no AI in it.

Renting also wins if nobody in the business will own a piece of software. An owned bot needs someone, in-house or hired, to keep the WhatsApp app credentials valid, update the documents it answers from, and fix it when Meta changes something.

When owning it is the right answer

• It must answer from your documents. Policies, product manuals, fee structures, a price list that changes monthly. This is retrieval-augmented generation (RAG): the bot looks up the relevant passages and answers only from them.
• It must refuse rather than guess. When nothing relevant is found above a similarity threshold, a well-built bot says it does not know and hands over to a person. A generic AI agent tuned for engagement will often improvise.
• It must touch your systems. Look up an order in your own database, book a slot in your own calendar, write a lead into your own CRM.
• You want the data. The conversations and the customer records live in a database you own, not in a vendor's dashboard you export from.

What an owned WhatsApp chatbot actually is

Less than people expect. Meta's Cloud API sends every incoming message to a webhook you host. Your code verifies it, retrieves the relevant passages, asks a model for an answer grounded in them, and posts the reply back to the Graph API. A minimal handler:

// 1. Meta verifies the webhook once with a GET request.
if (req.method === "GET") {
  const ok = url.searchParams.get("hub.verify_token") === env.VERIFY_TOKEN;
  return new Response(ok ? url.searchParams.get("hub.challenge") : "forbidden",
                      { status: ok ? 200 : 403 });
}

// 2. Every customer message arrives as a POST.
const msg = body.entry?.[0]?.changes?.[0]?.value?.messages?.[0];
if (msg?.type === "text") {
  const passages = await retrieve(msg.text.body);        // vector search
  const answer = passages.length
    ? await answerFrom(passages, msg.text.body)          // grounded reply
    : "I don't have that in our documents. A person will reply shortly.";

  await fetch(GRAPH_URL + "/" + env.PHONE_NUMBER_ID + "/messages", {
    method: "POST",
    headers: { Authorization: "Bearer " + env.WA_TOKEN,
               "Content-Type": "application/json" },
    body: JSON.stringify({ messaging_product: "whatsapp", to: msg.from,
                           type: "text", text: { body: answer } }),
  });
}

The reply goes out inside the 24-hour window the customer opened, so it is a service message. The real work sits in retrieve and answerFrom: splitting documents sensibly, choosing the threshold, and checking that answers cite what they used. That is also where most cheap chatbots cut corners.

Two things this does not remove. Outbound messages outside that window still need templates approved by Meta, owned bot or not. And your number still needs a verified Meta Business account, which takes paperwork rather than code.

A quick way to decide

1. Write down the ten questions customers ask most. If a menu answers them, rent a platform or use the free app's quick replies.
2. If the answers live in documents that change, or need a lookup in your systems, you need RAG and probably an owned bot.
3. Multiply the platform's plan plus its AI add-on by 36 and set that next to a one-time build plus its running cost.
4. Decide who maintains it. If the answer is nobody, rent.

If the answer points to owning it, the AI chatbot page has my fixed prices and a live assistant on this site built the same way, which you can try before deciding anything.