Experience Lion CRM — The King of WhatsApp CRM 7 Days Free Limited Access
→ Request Access

WhatsApp Automation Tool: A 2026 Buyer’s Guide

What a WhatsApp automation tool really costs in India, which of the three routes fits your team, and what actually gets a number banned.

Search for a WhatsApp automation tool and you get the same page fifteen times. A numbered list of platforms, a feature grid, a price starting from, and a closing line telling you to pick the one that fits your needs.

None of them answer the two questions that actually decide the outcome: which route are you automating on, and what will that route cost you after 1 October 2026?

Those are not tool questions. They are architecture questions, and they get settled before you compare a single feature. There are three ways to automate WhatsApp — a browser extension over your existing account, the free WhatsApp Business app, and Meta’s official Business API. They have different costs, different limits and different ways of failing. A tool that is excellent on one route cannot do the job of a tool on another, so a side-by-side price comparison across routes tells you nothing.

The second question is more urgent. On 1 October 2026, Meta starts charging for service messages — the free-form replies your team sends inside the 24-hour window after a customer writes in. Those are free today. They are also the single largest category of traffic that automation produces. No other software category gets repriced this hard by that one change, because automation exists to reply at volume inside exactly that window.

This guide covers what these tools actually do, the three routes and how to choose between them, what genuinely triggers a ban, what it costs in India in August 2026, which automations pay for themselves, and how to roll one out in thirty days.

In this guide

What a WhatsApp automation tool actually does

A WhatsApp automation tool sends or handles messages without a person doing it each time. That is the whole definition, and it is broader than it sounds.

The useful way to think about it is by trigger. Every automation is a rule with three parts: something happens, a condition is checked, a message goes out. What changes between tools is which triggers they can see and which messages they are allowed to send.

  • A customer message arrives. The tool replies instantly, or routes the chat to the right agent, or opens a bot flow.
  • A clock ticks. A follow-up fires two days after a quote with no reply. A reminder goes out the morning of an appointment.
  • Something changes in another system. An order ships, a payment fails, a lead is added to your CRM, a form is filled.
  • A person clicks a button. An agent triggers a saved sequence rather than typing it.

That is it. Everything sold as WhatsApp automation is some combination of those four triggers with a different interface on top.

What matters is that the trigger you need determines the route you must be on. Clock-based and system-based triggers need software running on a server that can send whenever it likes. A browser extension can only act while a browser is open on somebody’s laptop. That single mechanical fact eliminates about half the options for most buyers, and no feature grid states it.

Six things people mean by automation

The word covers six mechanically different jobs. Tools are usually good at two or three of them and sold as if they do all six.

  1. Instant replies. An acknowledgement the moment somebody writes in, and an away message outside business hours. The simplest automation and the one with the clearest return, because response time is the strongest predictor of whether an enquiry converts.
  2. Keyword routing. The message contains the word price, so it goes to sales. It contains order, so it goes to support. Cheap to build, and it removes the triage work that eats an agent’s morning.
  3. Chatbot flows. A structured conversation that collects information or answers a known question end to end. Genuinely useful for the eight questions you get every day. Frequently oversold beyond that.
  4. Follow-up sequences. A quote goes unanswered, so a reminder fires on day two and day five. This is where most unclaimed revenue sits, and it is the least implemented of the six. We have a full breakdown of what a good follow-up WhatsApp message looks like.
  5. Bulk and scheduled sending. One message to many people, now or later. The riskiest category by a wide margin, and the one that gets numbers banned. Read how to send bulk WhatsApp messages without getting banned before you send anything, and use scheduling to control when batches land.
  6. System-triggered notifications. An order confirmation from Shopify or WooCommerce, a payment reminder from your billing system, a status change in Zoho, HubSpot, Salesforce, Pipedrive or Odoo. This needs an API on both ends, and we have measured each of those integrations separately because the WhatsApp half is usually much thinner than the marketplace listing suggests.

Only jobs 1 to 4 are what most small businesses actually need. Jobs 5 and 6 are what most automation tools are built and priced for. That mismatch is the main reason teams overpay.

Three routes, and why the route decides everything

Route one: a browser extension over WhatsApp Web. It runs inside the WhatsApp Web tab you already use, on your existing number. It can send quick replies, save contacts in bulk, add notes and stages to chats, set follow-up reminders and send messages to lists at a controlled pace. There is no per-message fee, no template approval and no verification process, because Meta is not involved — you are still the one sending. It also cannot do anything while the browser is closed. Our detailed comparison of the category is in best WhatsApp CRM extensions for Chrome, and Lion CRM’s own extension sits in this route.

Route two: the free WhatsApp Business app. It has three real automations built in — a greeting message for first contact, an away message for out of hours, and quick replies you trigger by typing a shortcut. All free, all fine, all limited to one primary device. It also has broadcast lists, with a catch most people learn the hard way: a broadcast reaches a maximum of 256 people and only those who have saved your number in their phone. For a shop with a regular customer base that is workable. For anything else it silently reaches almost nobody.

Route three: the official WhatsApp Business API. Software runs on a server, holds your number, and can send whenever a trigger fires. This is the only route with real chatbots, real system integrations, real multi-agent assignment and real analytics. It is also the only route with a per-message bill, template approval, a 24-hour window rule and a verification process. Everything in the WhatsApp Business API pricing guide applies from the moment you switch to it.

The mistake is treating these as three price points on one ladder. They are three different machines. A ₹799-a-month extension and a ₹3,599-a-month API platform are not cheap and expensive versions of the same product — one cannot fire a reminder at 9am on Tuesday, and the other cannot avoid charging you per message.

Route comparison

Chrome extension Business app Official API
Instant auto-reply Yes, while browser open Yes, greeting and away only Yes, always
Keyword routing Basic No Yes
Chatbot flows No No Yes
Scheduled follow-ups Yes, if the tab is open No Yes
System-triggered sends No No Yes
Fires while you sleep No Greeting and away only Yes
Multiple agents, one number Shared session only No Yes, with assignment
Per-message cost None None Yes
Template approval needed No No Yes for outbound
Setup time Minutes Minutes Days to weeks
Typical India cost ₹499–₹1,500 per user Free ₹999–₹17,000 plus messages
Realistic team size 1–8 1 3 and up

Read that table by row, not by column. Find the row that describes the job you actually need automated, and the column tells you which route you are on. The price row is the last one you should look at.

If you are choosing rather than reading, Lion CRM covers two of these three routes — a Chrome extension for teams still working out of WhatsApp Web, and an official-API platform for when clock-based and system-based triggers become the point. See the platform.

What actually gets a number banned

This is where buying advice turns into marketing. The standard claim is that unofficial tools get you banned and the official API does not, so pay for the API. That is imprecise enough to be misleading, and it pushes small teams into spending they do not need.

The accurate version: Meta enforces on sending behaviour, not on the shape of your software. The signals that get a number restricted are the same whichever tool produced them.

  • Block rate. The share of recipients who block you. This is the strongest single signal by a distance.
  • Report rate. People tapping report spam.
  • Cold outbound volume. Many messages to people who have never messaged you, in a short window.
  • Message uniformity. Identical bodies fired at speed, with no variation and no conversation.
  • Reply rate near zero. Healthy messaging produces replies. A batch that produces none looks like a list blast, because it is one.
  • Account age and warm-up. A number that sent twelve messages last week and four thousand today is an obvious pattern.

So the risk line does not run where vendors draw it.

Low risk. A six-person team using an extension to handle conversations customers started — replying, labelling, adding notes, following up on live enquiries. Consent is real, volume is human, blocks are rare. This is a productivity layer over normal messaging.

High risk. Any list you bought, any scrape, any batch of hundreds of identical messages to people who do not know you. The official API does not protect you here — it just bills you for it and shows Meta a cleaner audit trail while your quality rating falls.

The honest rule is short: the API makes volume legitimate, not safe. What makes volume safe is opt-in, relevance and variation. If you have those, both routes work. If you do not, neither does.

What you pay: two meters, not one

Route three has two meters running, and quotes usually show one.

Meter one is the platform fee. A monthly subscription to the software, often priced per seat or per contact. This is the number on the pricing page.

Meter two is Meta’s per-message charge, which the platform passes to you, normally with a markup of ten to thirty percent. It scales with volume forever and is invisible until the first invoice.

Then 18% GST lands on both. In India these services are classified as OIDAR, so GST applies to the platform fee and the message charges alike. It is recoverable as input credit if you are registered, which makes it a cash-flow cost rather than a real one for most businesses — but it is absent from every rate card.

For automation specifically, the split between the two meters is unusual. Most automation traffic is replies inside an open window, which are free today. So automation buyers look at the two-meter model, see a message bill of almost nothing, and conclude the platform fee is the whole cost. That conclusion is correct until 1 October 2026 and wrong afterwards.

What it costs in India right now

Meta’s rates as of August 2026:

Message type India rate When you pay
Marketing template ₹0.8631 Always, on delivery
Utility template ₹0.115 Only outside an open 24-hour window
Authentication ₹0.115 Always
Service (free-form reply) Free until 1 Oct 2026 Inside the 24-hour window

The marketing rate rose from ₹0.7846 to ₹0.8631 earlier this year, an increase of about ten percent that arrived without a contract change. Utility and authentication stayed broadly flat.

Stack the layers on one marketing message: ₹0.8631 from Meta, roughly ₹0.09 of provider markup, plus GST on both, is about ₹1.12. That is thirty percent above the published rate — which is why message-heavy automation should always be modelled at the real rate, not the quoted one.

Platform fees in India run roughly ₹999 to ₹17,000 a month depending on tier and seat count. Extension tools run ₹499 to ₹1,500 per user per month with no second meter at all.

1 October 2026 reprices automation hardest

From 1 October 2026, Meta charges for service messages — the free-form replies sent inside the 24-hour window after a customer writes to you. Utility templates sent inside that window lose their free status too. Incoming customer messages still cost nothing, and the 72-hour free entry window from click-to-WhatsApp ads is expected to survive.

Meta had not published the final rate card as of early August 2026. That is not a reason to wait. The direction is certain even if the number is not.

Here is why this matters more to automation buyers than to anyone else. The entire purpose of an automation tool is to produce replies inside the 24-hour window at volume. Instant acknowledgements, bot answers, routing confirmations, follow-up nudges to people who wrote in this morning — every one of those is a service message. A tool whose value proposition is we reply for you is a tool whose output line goes from zero to billable overnight.

Three consequences worth planning for:

  • Messages per resolution becomes a cost metric. A bot that takes nine turns to answer a question a human answers in three just became three times more expensive to run. Nobody measures this today because it has always been free.
  • Chatty automation gets expensive. Confirmation messages, thanks for that, one moment please, progress pings. Free today, a line item in October. Audit your flows for filler now, while it costs nothing to remove.
  • Good automation gets more valuable, not less. Every question a bot answers correctly on the first try is a human exchange you do not pay for. This is the strongest case a WhatsApp AI chatbot has ever had, and it arrives in seven weeks.

The teams most exposed are the ones who look safest today: inbound-heavy service businesses whose message bill currently reads close to zero. A services business handling 150,000 outbound service messages a month pays almost nothing today. At the current utility rate that becomes roughly ₹23,400 a month. The bill does not rise. It appears.

Ask any vendor you are evaluating two direct questions: how will you bill service messages from October, and will your reporting show me messages per conversation before then? A vendor who cannot answer the second one cannot help you control the first.

The template category trap

On route three, every outbound message that starts a conversation must use a template Meta has approved, and Meta assigns the category during approval. It does not always agree with what you intended.

The rates are not close. A marketing template costs ₹0.8631 and a utility template costs ₹0.115 — a factor of seven and a half. A follow-up reminder that mentions a discount, a delivery update that suggests a related product, an appointment confirmation with a promotional line at the bottom: each of those can be reclassified as marketing, and most dashboards do not flag it.

Automation makes this worse than it is for campaign senders, because automated templates fire continuously and unattended. A miscategorised template in a campaign costs you once. A miscategorised template in an automation costs you every day until somebody notices.

Auditing your approved templates for category drift takes an afternoon and is usually the largest single saving available on the whole bill. The full arithmetic is in the WhatsApp Business API pricing guide.

The 24-hour window is the whole design constraint

Almost every rule on route three follows from one mechanism. When a customer messages you, a 24-hour window opens. Inside it you can send free-form messages. Outside it you can only send approved templates.

This is not a billing detail. It is the constraint that shapes what your automation can be.

  • Anything reactive is easy. Replying, routing, bot flows, clarifying questions — all inside the window, all currently free, all simple.
  • Anything proactive is a template. Follow-ups after two days, appointment reminders, re-engagement, abandoned-cart nudges. Approved in advance, categorised by Meta, billed per send.
  • Timing changes the price of an identical message. A shipping update sent while the customer is mid-conversation is free. The same text two days later costs ₹0.115. Automation that knows window state is worth real money, and very little software surfaces it.

The design lesson: build automation that gets its work done inside open windows. Batch your notifications to fire when windows are open, answer completely on the first reply rather than across six turns, and use the free entry windows from ads rather than paying to reopen a conversation you let lapse.

Five automations worth building first

In rough order of return per hour spent.

1. The instant first reply. An acknowledgement within seconds, every time, including at 11pm. Response time is the strongest lever on conversion in this channel, and this is the cheapest automation to build on any route. Our guide to WhatsApp auto reply covers the mechanics on each route.

2. The two-touch follow-up. One nudge at day two, one at day five, then stop. Most businesses send zero follow-ups and lose the enquiry silently. This single sequence usually returns more than every chatbot flow combined.

3. Business-hours routing. Route to whoever is on shift, and set an honest expectation out of hours. A message that says we will reply by 10am tomorrow outperforms silence and outperforms a fake instant reply that nobody follows up.

4. The eight-question bot. Not a general assistant. A flow that answers the eight questions you genuinely get every day — hours, location, price range, availability, delivery time, warranty, payment methods, how to book. Cheap to build, and after October it directly reduces the message count per conversation.

5. Appointment and payment reminders. Only if you have appointments or invoices. Utility templates, low rate, and the return is measured in reduced no-shows rather than in messages sent.

Everything else can wait until these five are live and measured.

Four that demo well and rarely pay

The AI assistant that handles everything. Impressive in a demo on prepared questions. In production it answers the easy ones your bot already covered and hands you the hard ones anyway, having spent four extra messages discovering that. After October you pay for those four.

Deep drip campaigns. Six-message nurture sequences imported from email thinking. WhatsApp is not email. It is a channel people treat as personal, and message four of a sequence they did not ask for is where the block rate comes from.

Full CRM sync on day one. Bidirectional sync between WhatsApp and your CRM sounds like the goal. In practice it is a three-month project that delivers less than the two-touch follow-up you could ship this week. Do it after, not before.

The chatbot builder itself. Every vendor demos the drag-and-drop canvas. The canvas is never the constraint. Writing flows that match how your customers actually ask things is the constraint, and no builder helps with that.

Lion CRM is built around the five that pay, not the four that demo — instant replies, follow-up sequences, routing and a pipeline you can see, on your own WhatsApp Business Account rather than ours. See the platform.

Sending limits nobody mentions until you hit them

On route three there is a second ceiling that has nothing to do with money.

Meta caps how many unique contacts you can start conversations with in a rolling 24 hours, and the cap rises in tiers as your quality rating holds. A new unverified number starts at 250 unique contacts a day. Completing business verification moves you up, and consistent good-quality sending moves you up again through 1,000, 10,000 and 100,000 to unlimited.

Two things follow.

Start business verification on day one. It takes longer than every other setup step combined and it gates everything above the starting tier. Teams routinely discover this in week three, with a campaign scheduled.

Your quality rating is an automation risk, not just a marketing one. A rating drop lowers your tier, and a lowered tier can stop a notification flow that has nothing to do with the messages that caused the drop. One bad marketing batch can break your order confirmations. The same rating also gates the green tick, which is why treating it as a marketing metric alone is a mistake.

Worth knowing before you compare hosting claims: since Meta retired the on-premise option, effectively everything in this market runs on Cloud API, whatever the sales deck implies. The distinction and what it means for control is covered in Cloud API vs on-premise.

On routes one and two, the limits are different but real: a browser session can only send at human pace, and the Business app’s broadcast list reaches 256 people who have saved your number. Neither route has a tier system, because neither route is talking to Meta’s servers on your behalf.

Three teams, three real monthly bills

A three-person boutique agency, entirely inbound. About 400 conversations a month, all started by the client, all answered by a human within the window. An extension at ₹799 per user is ₹2,397 a month, one meter, no templates, no verification. An API platform would be ₹3,599 plus a negligible message bill. Today the extension wins clearly. After October the gap narrows a little, because the extension has no way to automate a first reply and the platform does — but at 400 conversations that saving does not cover ₹1,200 of difference. Stay on the extension.

A twelve-person clinic group with appointments. 2,000 inbound conversations, 3,000 appointment reminders, 900 follow-ups a month. The reminders are utility templates sent outside windows, so they cost about ₹345 from Meta. The platform fee at this seat count is the real number, call it ₹8,000 all-in today. October adds roughly ₹300 on the service side. The reminders alone justify route three, because no extension can fire at 9am on a Tuesday without somebody’s laptop being open. Route three, and the message bill is not the reason.

An eight-person e-commerce support desk. 12,000 inbound conversations a month, mostly order status, answered by a mix of bot and agent, averaging seven messages per resolution. Today the message bill is close to zero and the platform fee is everything. From October, 84,000 service messages at the current utility rate would be about ₹9,660 a month before markup and GST — call it ₹13,000. Cutting the average from seven messages to four, by answering order status in one bot turn instead of a conversation, takes that to about ₹7,400. The automation redesign is worth more than switching vendors.

Sector detail for these three shapes sits in WhatsApp CRM for real estate for the enquiry-heavy case, healthcare clinics for the appointment case, and e-commerce for the support-desk case, with the plumbing in the Shopify and WooCommerce integration guides. Agencies running this for clients should read WhatsApp CRM for marketing agencies instead, because the seat maths inverts.

Do you need an automation tool or a CRM?

These are sold as one category and they are two products.

An automation tool is built around messages. Its data model is flows, triggers and templates. It is excellent at making the right message go out at the right moment, and it usually has a thin idea of who the person is.

A CRM is built around relationships. Its data model is contacts, stages and history. Automation is one of six jobs it does, alongside assignment, pipeline, notes and reporting. Our full breakdown is in WhatsApp CRM software, and the channel-versus-software distinction is in WhatsApp CRM vs WhatsApp Business API.

The honest test: if you cannot answer where each open enquiry stands, you have a CRM problem and automation will not fix it. Automating a pipeline you cannot see just produces faster confusion. If you can already see the pipeline and the bottleneck is people typing the same things, you have an automation problem.

Most teams under ten people have the first problem and buy for the second. A Kanban view of live conversations usually reveals which one you actually have inside a week.

If your outbound is campaign-shaped rather than trigger-shaped — segments, broadcasts, promotional sends — that is a third product again, covered in WhatsApp marketing software.

And if you are being asked to run this for other businesses, the decision changes shape completely. You are no longer choosing automation for one team, you are choosing a platform to resell, where multi-tenancy, branding and margin outrank every feature on this page. That is a separate evaluation, covered in whitelabel WhatsApp CRM software, the India comparison and the best WhatsApp CRM to resell. If you want the fastest version of that path, we wrote up launching your own WhatsApp CRM SaaS in seven days.

What to check before you buy

Ask these before you look at a demo. The answers separate vendors far better than any feature list.

  • Whose Meta Business Portfolio will hold the WhatsApp Business Account? If it is yours, the vendor is a partner you can replace. If it is theirs, leaving needs their cooperation at the exact moment your interests diverge.
  • What is your markup on Meta’s per-message rate, as a number? Ten to thirty percent is normal. Refusing to say is not.
  • How will you bill service messages from 1 October 2026? Every vendor has to answer this. Few have published it.
  • Can I see messages per conversation in reporting? This becomes your main cost lever in seven weeks.
  • What happens to my flows if I leave? Chatbot flows, routing rules and canned replies have no export format anywhere in this industry. Assume you rebuild them.
  • Is the automation limited by seat count? Some plans meter automation by agent, which makes a cheap tier expensive the moment you grow.
  • Does the tool know whether a 24-hour window is open? Surprisingly few surface it, and it is the difference between a free message and a paid one.
  • What is the actual setup time to first automated message? On route three, verification is the long pole. Get a date, not a range.

Get the first three in writing. The rest you can verify in a pilot.

One reason the markup question works: it is the number your vendor is least keen to discuss and the easiest for you to check afterwards. If you want to see why, the WhatsApp Business API reseller guide lays out the same economics from the provider’s side of the table. Reading it as a buyer tells you exactly which parts of the quote are cost and which are margin.

The mistakes that cost the most

Choosing a route by price instead of by trigger. The cheapest tool that cannot fire at 9am is not cheap, it is the wrong machine.

Buying route three for jobs one to four. Instant replies and follow-ups on a small inbound team do not need an API, templates or verification. Plenty of teams pay ₹40,000 a year for a capability they use once a quarter.

Automating before you have measured. If you do not know your current response time and follow-up rate, you cannot tell whether the tool worked. Measure for a week first. It costs nothing.

Building the bot before writing the answers. The eight questions come first. The flow is the easy part.

Ignoring October. A budget built on free service messages is about to be wrong, and the inbound-heavy teams whose bill reads zero today are the most exposed.

Treating the API as ban insurance. It legitimises volume. It does not make a bought list safe.

Skipping business verification. It gates your sending tier and it takes the longest. Start it on day one, even if you are only piloting.

Letting flows sprawl. Every extra confirmation message was free to add and will not be free to keep.

A 30-day rollout plan

Week one — measure, do not buy. Count last month’s inbound conversations, your median first-response time, how many enquiries got any follow-up, and your average messages per resolution. That last number is your October exposure. Most teams cannot produce it, which is itself the finding.

Week two — pick the route, then the tool. Use the comparison table. Decide which triggers you genuinely need. Only then shortlist three tools inside that one route, and ask the eight questions above. If you are going route three, start business verification this week regardless of which vendor you pick.

Week three — ship two automations, not ten. The instant first reply and the two-touch follow-up. Run them on one real team with real conversations for a full week. Resist every other flow.

Week four — measure the same four numbers and model the bill twice. Once at today’s rates, once assuming service messages bill at the current utility rate. If the second number changes your answer, choose the tool that reduces messages per conversation rather than the one that is cheaper today.

Do that and you end the month with two automations that work, a measured before-and-after, and a bill you have already stress-tested against the change that lands in October. That is a better position than most businesses running fifteen flows they have never measured.

Want to see it working before you commit? Lion CRM runs on your own WhatsApp Business Account, with a Chrome extension for teams still living in WhatsApp Web and a full official-API platform for when the triggers move to the server. See the platform.

Frequently asked questions

What is a WhatsApp automation tool?
It is software that sends or handles WhatsApp messages without a person doing it each time. It works off four kinds of trigger: a customer message arriving, a clock, a change in another system, or an agent clicking a saved action. In practice it covers instant replies, keyword routing, chatbot flows, follow-up sequences, scheduled or bulk sending, and notifications from systems like your store or CRM.

How much does a WhatsApp automation tool cost in India?
Browser-extension tools run roughly ₹499 to ₹1,500 per user per month with no per-message fee. Official-API platforms run roughly ₹999 to ₹17,000 a month depending on tier and seats, plus Meta’s per-message charge, plus a provider markup that is commonly ten to thirty percent, plus 18% GST on both. Meta charges ₹0.8631 per marketing message and ₹0.115 per utility or authentication message as of August 2026.

Can I automate WhatsApp for free?
Partly. The free WhatsApp Business app gives you a greeting message, an away message and quick replies, which covers the simplest instant-reply automation at zero cost. It does not do routing, chatbots, follow-up sequences, multiple agents or anything triggered by another system, and its broadcast lists reach a maximum of 256 people who have already saved your number.

Will a WhatsApp automation tool get my number banned?
Not by itself. Meta enforces on sending behaviour rather than on which tool you used. Blocks, spam reports, high volumes of cold outbound, identical message bodies at speed and near-zero reply rates are what trigger restrictions. A small team automating replies to conversations customers started is low risk on any route. Blasting a purchased list is high risk on every route, including the official API.

Do I need the WhatsApp Business API to automate WhatsApp?
Only for some jobs. You need it for chatbot flows, messages triggered by other systems, anything that must fire while nobody is at a computer, several agents sharing one number with proper assignment, and outbound template messaging at volume. Instant replies, quick replies, notes and manual follow-ups all work on a browser extension over your existing account, with no per-message fee and no template approval.

What changes for WhatsApp automation on 1 October 2026?
Meta starts charging for service messages, which are the free-form replies sent inside the 24-hour window after a customer writes to you. Utility templates inside that window also lose their free status. Automation is the category most affected, because producing replies inside that window at volume is exactly what these tools do. Messages per conversation becomes a real cost metric, and Meta had not published the final rate card as of early August 2026.

What is the 24-hour window and why does it matter?
When a customer messages your business, a 24-hour window opens during which you can send free-form replies. Outside that window you can only send templates that Meta has approved in advance, and those are billed per message by category. It matters because the same message can cost nothing or ₹0.115 or ₹0.8631 depending only on when it is sent and how Meta categorised it.

How many messages can I send a day on the official API?
Meta caps the number of unique contacts you can start conversations with in a rolling 24 hours. A new unverified number starts at 250. Completing business verification raises it, and consistently good quality moves you through 1,000, 10,000 and 100,000 to unlimited. Replies inside open windows do not count against that cap, and a drop in quality rating can move you back down a tier.

Is a WhatsApp automation tool the same as a WhatsApp CRM?
No. An automation tool is built around messages, so its data model is flows, triggers and templates. A CRM is built around relationships, so its data model is contacts, pipeline stages and history, with automation as one of several jobs. If you cannot currently say where each open enquiry stands, that is a CRM problem and automating it will only produce faster confusion.

Which WhatsApp automations should I build first?
Two: an instant first reply that fires within seconds at any hour, and a two-touch follow-up at day two and day five for enquiries that go quiet. Those two return more than everything else combined for most businesses. After they are live and measured, add business-hours routing and a small bot covering the eight questions you genuinely get every day.

Become a Reseller