Automatic WhatsApp Message Sender: Scheduled, Triggered, and Auto-Reply
An automatic WhatsApp message sender means one of three different things. Here is which one you actually need, and why browser extensions can only fake the easiest of them.
An automatic WhatsApp message sender is one of three different products, and people searching for one usually want a different one than they think. There is scheduling, where you write a campaign now and it goes out Tuesday morning. There is event-triggered sending, where an order ships or an appointment approaches and a message fires with nobody touching it. And there is auto-reply, where an inbound message gets an instant answer. They share a name and almost nothing else.
Sorting out which one you need saves you from buying the wrong tool, and it explains why the free browser extensions can only do a bad version of the first one.
The three kinds, quickly
| What you want | What it actually is | Costs a message fee? | Needs a template? |
|---|---|---|---|
| Send this campaign at 9am Tuesday | A queue and a clock | Yes, per delivered template | Yes |
| Message the customer when the order ships | A webhook wired to a template | Yes, per delivered template | Yes |
| Answer instantly when someone messages us | An inbound webhook and a reply | No, it is free | No |
That third row is worth staring at. Auto-reply is not sending in the technical sense at all. It happens inside the 24-hour customer service window that opens the moment a customer messages you first. Inside that window you can send free-form text, images, and PDFs, with no template approval and no message charge. Businesses routinely pay for "automation" software to do the one thing WhatsApp gives away.
Scheduled sending
This is the simplest kind and the one people usually mean. You upload a list, pick an approved template, choose a time, and the platform holds the campaign until then.
Two details separate a real scheduler from a toy. The first is timezone handling. A campaign that fires at 9am server time reaches your Pacific customers at 6am, which is how you collect blocks. A scheduler worth using sends at 9am in each recipient's local time, which means it needs to know or infer their timezone.
The second is throttling against your messaging tier. On the official platform a new business portfolio can reach 250 unique customers in a rolling 24 hours. Verification lifts that to 2,000, and the tiers then climb automatically to 10,000, 100,000, and unlimited as you use at least half your current limit within seven days at a high quality rating. A scheduler that dumps 5,000 messages into the API at a tier-250 account does not beat the ceiling. It collects 4,750 errors and dents your quality rating on the way. A good one paces the send to your current tier and tells you how long the campaign will take.
This is also the only kind of automation a browser extension can attempt, and it attempts it by keeping a tab open. If your laptop sleeps, the campaign stops mid-list. If the tab is backgrounded, throttling slows it unpredictably. There are no delivery receipts, so you cannot tell who got the message. Scheduling a browser tab is not scheduling.
Event-triggered sending
This is where the money is, and it is the kind extensions structurally cannot do.
An event happens in a system you own. An order moves to shipped. An invoice becomes overdue. An appointment is tomorrow at 2pm. A lead fills in a form. Your system emits that event, something catches it, picks the matching approved template, fills in the variables, and posts it to Meta's Graph API. No human is involved and none of it depends on a computer being awake.
The reason an extension cannot do this is architectural, not a missing feature. Nothing can call into a browser extension. Your CRM cannot notify it. Your store cannot wake it. An extension can only act while a person has the browser open and the tab loaded, which means it can never be the thing that tells a customer their order shipped at 4am.
Common triggers that pay for themselves:
- Order shipped, with the tracking number. Cuts "where is my order" tickets more than any other single message.
- Appointment tomorrow, with a confirm or reschedule button. This is the classic no-show killer for clinics, salons, and trades.
- Payment failed or card expiring, which recovers revenue that would otherwise churn quietly.
- Invoice due in three days, sent as a utility template rather than a chased email.
- Form submitted, opening the conversation while the lead is still on the page.
All of those are utility-category templates, which matters more than it sounds. Utility templates deliver to United States phone numbers normally. Marketing templates have not delivered to US numbers since April 1, 2025, and fail with error 131049. So the triggered, transactional automation is exactly the automation that still works for a US business, while the promotional broadcast, the thing most people picture when they hear "bulk WhatsApp," is the part that no longer lands.
If the triggered message ends a workflow rather than starting one, keep the next step just as automatic. A confirmed appointment or an accepted quote usually needs paperwork, and dropping a contract into the chat as a PDF works far better when the customer can sign it without printing anything.
Auto-reply
The third kind is inbound. A customer messages you, and something answers immediately: outside business hours, while your team is on other chats, or with a menu that routes the conversation.
The economics here are unusually good. The customer messaging you first opens a 24-hour customer service window. Inside it, non-template messages are free, in both directions, as many as you like. So an auto-reply costs nothing. Neither does the human follow-up, provided it happens inside the day.
What auto-reply cannot do is start a conversation. If the window has closed, a free-form message fails with error 131047 and you must send a template instead. That is the boundary between the free channel and the paid one, and it is the single most useful thing to understand about WhatsApp's pricing model. We cover the setup in detail on the WhatsApp auto reply page.
How to set up an automatic WhatsApp message sender
Whichever kind you need, the foundation is the same and it takes an afternoon.
Register a phone number to a WhatsApp Business Account in Meta Business Manager. Use a number you do not mind losing from the WhatsApp app, because registering it to the API removes it from the app permanently and there is no way to have both. Complete business verification while you are there, since it is what lifts your first messaging tier from 250 to 2,000.
Write your templates. One per message you intend to automate, with numbered placeholders for the variable parts. Keep every promotional phrase out of the transactional ones. A shipping notification that mentions a discount code is a marketing template as far as Meta's reviewer is concerned, and it will stop reaching US customers.
Wire the trigger. For scheduling, that is a queue. For event-triggered sends, it is a webhook from your store, CRM, or billing system, which is what a WhatsApp API integration gives you. For auto-reply, it is Meta's inbound webhook pointed at your handler.
Then read the receipts. Meta posts back sent, delivered, read, or failed with an error code for every message. Store them. The failures are the most valuable data you will get, because they tell you which numbers are dead, which templates got miscategorized, and when you are hitting your tier ceiling.
What to avoid
Any tool that automates WhatsApp Web to do this. WhatsApp's Terms of Service prohibit "sending illegal or impermissible communications such as bulk messaging, auto-messaging, auto-dialing, and the like," and an extension that drives your session does exactly that. The ban risk is the price you pay for the zero-cost messages, and it comes due all at once. Our WhatsApp message sender page breaks down the three tool categories, and is bulk WhatsApp messaging allowed quotes the terms line by line.
Also avoid building the promotional broadcast first. It is the feature everyone wants and, for a US audience, the one that will not deliver. Build the triggered transactional messages, watch the support tickets drop, and run promotions through the free 72-hour window that a click-to-WhatsApp ad opens. That sequence is what the businesses actually succeeding on this channel did.
Frequently asked questions
How do I set up an automatic WhatsApp message sender?
Register a phone number to a WhatsApp Business Account, get your message templates approved by Meta, then wire the trigger: a scheduler for timed campaigns, a webhook from your store or CRM for event-triggered messages, or Meta's inbound webhook for auto-replies. Send through the Cloud API and log the delivery receipt Meta posts back for each message.
Can WhatsApp send messages automatically?
Yes, through the WhatsApp Business Platform. You can schedule campaigns, fire templates on events from your own systems, and auto-reply to inbound messages. The consumer WhatsApp app and the free WhatsApp Business app cannot do any of this, because neither exposes a public API for automated sending.
Is an automatic WhatsApp sender against WhatsApp's rules?
It depends entirely on how it sends. Automating through Meta's official Cloud API with approved templates is exactly what the platform is for. Automating by driving your WhatsApp Web session with a browser extension violates the Terms of Service clause prohibiting bulk messaging and auto-messaging, and gets the phone number banned.
Can I schedule WhatsApp messages for free?
Auto-replies inside the 24-hour customer service window are genuinely free, since non-template messages cost nothing. Scheduled campaigns are not: they send template messages, and Meta charges when a template is delivered. Free browser extensions avoid the fee by automating WhatsApp Web, which is prohibited and ends in a ban.
Why did my automatic WhatsApp message fail to send?
Read the error code on Meta's delivery callback. Error 131049 means a marketing template was sent to a US number, which Meta has blocked since April 2025. Error 131047 means you sent free-form text after the 24-hour service window closed. Rate limit errors mean you exceeded your messaging tier, which starts at 250 unique recipients per rolling 24 hours.
What is the difference between auto-reply and automated sending?
Auto-reply answers a customer who messaged you first, inside the free 24-hour service window, with no template and no charge. Automated sending starts the conversation, which requires an approved template and costs a message fee when Meta delivers it. Auto-reply is free because the customer opened the door.