You wrote the message at midnight. It needs to go out at 8am. Right now your only honest options are to stay up, set an alarm, or trust yourself to remember. WhatsApp still ships no future-dated scheduler on Android in 2026, so people reach for automation apps like Tasker and MacroDroid to fake one. They can work. They also break in ways nobody warns you about until a birthday message never fires. This guide walks the real builds, the real failure modes, and the path that doesn't depend on your phone being awake.
Can you schedule a WhatsApp message on Android natively in 2026?
No. As of June 2026 there is no native feature in the standard WhatsApp app on Android to schedule a regular chat message to a contact at a future date and time. There is no "send later" button, no calendar picker, no clock icon on the compose bar. To schedule a WhatsApp message on Android, you need an outside tool.
Let me be precise. WhatsApp's consumer app on Android lets you send now, forward, reply, and react. It does not let you queue a message for 8am tomorrow. Same on iPhone, WhatsApp Web, and Desktop. A tutorial claiming a built-in scheduler exists in the standard app is either out of date or confusing WhatsApp with a third-party tool bolted on top.
So the answer to can I schedule a WhatsApp message on Android with WhatsApp alone is no. Everything that follows is a workaround: on-device automation that simulates you tapping send, or a tool that sends through a separate session. The rest of this guide is about choosing the one that survives contact with reality. For the device-by-device native picture across iPhone too, see scheduling WhatsApp messages without a third-party app.
Does the WhatsApp Business app let you schedule messages on Android?
No. The WhatsApp Business app does not have a feature to schedule your own message to a contact at a future time. Its only native automation is greeting messages, away messages, and quick replies. All three are auto-replies or text shortcuts triggered by an incoming message. None of them schedules an outbound send.
This trips people up constantly, so here is exactly what each Business tool does, straight from how Meta describes them:
- Greeting message. An automatic reply sent to a customer when they message you for the first time, or after 14 days of no contact. It fires in response to their message, not on a clock you set.
- Away message. An automatic reply sent when someone messages you outside your set business hours. You can schedule the hours, but the message only goes out when a customer writes in. It never reaches out first.
- Quick replies. Saved text snippets you insert by typing a shortcut starting with
/. You still have to be in the chat, typing, and hitting send yourself. It is a typing shortcut, not automation.
You set these under Settings, then Business Tools, then Greeting Message or Away Message. They're genuinely useful for first-touch responses. But notice the pattern: every one is reactive. A customer has to message you first. There is no "Tools > Schedule message" path that lets you compose a message now and have it auto-send to a contact at 9am next Tuesday. That feature does not exist in the Business app.
So if your plan was to install WhatsApp Business expecting a free native scheduler, stop. You'll find auto-replies and nothing that schedules an outbound message. For a fuller breakdown of where each tool fits, the best apps to schedule WhatsApp messages roundup compares them side by side.
How do you schedule a WhatsApp message on Android with Tasker (step-by-step)?
Tasker schedules a WhatsApp message by combining a time-based trigger with a plugin called AutoInput, which uses Android's accessibility service to simulate taps on the screen. You build a task that opens a chat with your text pre-filled, then have AutoInput find and tap the send button at the scheduled time. The phone must be on and unlocked for it to work.
Tasker is the power-user tool. It does almost anything, which also means it has a learning curve. Here is the workflow that actually sends, not just opens, a message.
What you need first: Tasker (paid, one-time) and the AutoInput plugin (separate purchase after a trial). AutoInput needs its accessibility service switched on under Android Settings, then Accessibility, then AutoInput. Without that permission, the tap never happens.
- Build the open step. In Tasker, create a new Task. Add a Browse URL or Send Intent action pointing at
https://api.whatsapp.com/send?phone=COUNTRYCODE_NUMBER&text=Your%20message%20here. Use the full international number, no plus sign, no spaces, and URL-encode the text (a space becomes%20). This opens the chat with your message already typed into the box. - Add a wait. Insert a Wait action of 2 to 3 seconds so WhatsApp has time to load the chat before the next step runs. Skip this and AutoInput tries to tap a screen that hasn't rendered yet.
- Tap send with AutoInput. Add an AutoInput > Action step. Set it to click the send button. The reliable way is to match the send button by its description (it's labelled "Send") rather than by raw screen coordinates, because coordinates break the moment your resolution or WhatsApp's layout changes.
- Attach a time trigger. Create a Profile with a Time context set to your send time, and link it to the task. For a one-off, Tasker also pairs well with a calendar-event or alarm trigger.
- Disable battery optimization for Tasker under Settings, then Apps, then Tasker, then Battery, then Unrestricted. This is the step most guides skip, and it's the one that silently kills scheduled tasks overnight.
When it fires, your screen wakes, WhatsApp opens to the chat, the text is pre-filled, AutoInput taps Send, and the message goes. The Tasker community documents this exact api.whatsapp.com/send plus AutoInput-tap pattern as the standard approach.
What breaks: AutoInput matches UI elements by what's on screen. When WhatsApp ships an app update that moves or relabels the send button, your task taps the wrong thing or nothing at all, and you won't know until a send fails. The accessibility service can also get disabled by Android after an update or a force-stop. And if the phone is locked or the screen is off at trigger time, the tap can't happen at all. Test it on a throwaway chat before you trust it with anything that matters.
Is MacroDroid or Automate an easier alternative to Tasker?
Yes, MacroDroid is the friendlier option. It ships a dedicated WhatsApp Send action, so you don't have to wire up URLs and tap-detection by hand the way Tasker does. Per the MacroDroid documentation, that action still uses fake UI interactions under the hood, which means the same hard requirement: the screen must be on and unlocked, and MacroDroid's UI Interaction accessibility service must be enabled.
MacroDroid trades Tasker's flexibility for a guided builder. Here's the WhatsApp send flow:
- Create a new Macro.
- Add a Trigger: choose Day/Time Trigger and set your date and time.
- Add an Action: pick WhatsApp Send. Enter the recipient's full international number (or use the contact picker) and type your message.
- Leave Pre-populate unchecked. Per the MacroDroid wiki, if Pre-populate is checked the message is only written into the box and not sent automatically. Unchecked, it sends.
- Enable the MacroDroid UI Interaction accessibility service when prompted, and set MacroDroid to Unrestricted under battery settings.
Two limits worth knowing up front, both stated in MacroDroid's own docs: the WhatsApp Send action cannot send to groups (individual contacts only), and it cannot send while the device is locked or the screen is off.
Automate (by LlamaLab) is the third option. It's a visual, flowchart-style builder that, like the others, leans on the Accessibility API to simulate taps and interact with WhatsApp's UI. It's powerful and has a generous free tier, but building a reliable send flow means assembling blocks (open chat, wait, interact-click the send element) yourself, which puts its difficulty between MacroDroid and Tasker.
| Tool | Difficulty | Group sends | Recurring | Phone must be on |
|---|---|---|---|---|
| Tasker + AutoInput | High | Possible (fragile) | Yes | Yes, unlocked |
| MacroDroid | Low to medium | No (1:1 only) | Yes | Yes, unlocked |
| Automate | Medium | Possible (fragile) | Yes | Yes, unlocked |
| SKEDit | Low | Yes | Yes | Yes (auto-unlocks) |
If you want the least setup, SKEDit is the consumer-friendly version of all this. It's a dedicated WhatsApp scheduler Android app, a WhatsApp message scheduler Android users can run without building macros, wrapping the same Accessibility API approach in a normal scheduling UI. It even auto-unlocks the phone, sends, then re-locks. Free users get up to 5 scheduled messages a day per SKEDit's plan details. It still carries the core constraint of every on-device tool: the phone has to be powered on and online at send time.
Why do on-device automation apps fail to actually send (battery optimization, accessibility, phone must be on)?
On-device automation fails because it isn't really sending a message, it's puppeting your phone to tap the send button for you. That only works if the phone is awake, unlocked, has the accessibility service running, and isn't being throttled by battery optimization. Break any one of those and the message silently never goes out.
This is the part the breezy "schedule WhatsApp messages on Android in 3 easy steps" posts leave out. Here are the four ways these setups die, roughly in order of how often they bite:
- Battery optimization kills the trigger. Android aggressively sleeps background apps to save power. If Tasker, MacroDroid, or SKEDit isn't set to "Unrestricted" battery use, Android may freeze it before your scheduled time, and the send never fires. Manufacturer skins like Samsung's One UI and Xiaomi's MIUI are especially aggressive here.
- The phone is locked or the screen is off. These tools simulate screen taps. A locked phone with the screen off has nothing to tap. MacroDroid's docs say this outright; it cannot send when the device is locked. SKEDit works around it by auto-unlocking, but that's a band-aid over the same underlying limit.
- The accessibility service gets switched off. Android disables accessibility services after some updates, force-stops, or "clean up" actions by battery apps. When the service is off, the tap can't happen and your automation appears to run but does nothing.
- A WhatsApp update moves the send button. Coordinate-based or element-based taps assume a fixed layout. When WhatsApp ships a UI change, the tap lands on the wrong element or misses entirely. This is the classic "it worked for months, then quietly stopped" failure.
There's also a quieter cost: the screen lights up every time one of these fires. Schedule a 3am message and your phone wakes the room. None of this makes on-device automation useless, but it makes it the wrong choice for anything you can't afford to silently miss. As one Tasker regular put it, "the automation works until WhatsApp updates, and then you find out three sends later." That's the honest throughline. It works, until it doesn't, and it rarely tells you when.
What's the most reliable way to schedule a WhatsApp message on Android?
The most reliable way to schedule a WhatsApp message on Android is to stop depending on your phone being awake. Instead of puppeting the WhatsApp app, schedule the send through WhatsApp Web in a browser, where a tool queues the message and fires it from the session, not from a screen tap that needs an unlocked phone.
Every on-device approach above is fragile for the same root reason: it simulates a human tapping send on your physical phone. Move the scheduling to your linked WhatsApp Web session and the screen-tap dependency disappears. The message sends from the web session, so your phone can be locked, face-down, or in your pocket.
That's what Blueticks does. It's a Chrome extension that adds a scheduler directly to WhatsApp Web. You open a chat, type the message, pick a date and time, and it queues. The setup, end to end:
- Install the Blueticks extension from the Chrome Web Store on a computer.
- Open WhatsApp Web and link it to your phone the usual way (Settings, Linked Devices, scan the code) one time.
- Open a chat, write your message, and attach an image or document if you need one.
- Set the date and time in the scheduling control. For repeating sends, set a recurrence instead of a one-off.
- Confirm and walk away. The message queues and fires at the time you set.
This is also the only practical route for recurring sends and for sending to a list, which the on-device tools handle poorly or not at all. For the repeat case, the recurring WhatsApp message workflow sets a pattern once and runs on its own.
What breaks here, honestly: the free WhatsApp Web setup needs the browser tab open and the session connected to send. Close the tab or let the laptop sleep and queued messages wait until the session reconnects. Blueticks' paid offline gateway mode covers exactly this gap, sending even when your computer is closed, but on the free path, treat an open, connected tab as the requirement. The trade is straightforward: a one-time computer setup in exchange for sends that don't depend on your phone staying awake and unlocked.
Install the Blueticks Chrome extension and schedule your first WhatsApp message
How does scheduling on Android compare to iPhone and WhatsApp Web?
Android is the most flexible platform for scheduling a WhatsApp message because its open automation model lets apps like Tasker and MacroDroid simulate sends, something iOS blocks. iPhone has no auto-send at all; Apple's Shortcuts can only pre-fill a message you still tap manually. WhatsApp Web has no native scheduler either, but it's where browser-based tools add one.
The platform gap comes down to how each OS handles one app driving another:
| Platform | Native scheduler | On-device auto-send | Reliable route |
|---|---|---|---|
| Android | No | Yes (Tasker, MacroDroid, SKEDit, phone-on) | WhatsApp Web tool |
| iPhone (iOS) | No | No (Shortcuts pre-fills only, manual tap) | WhatsApp Web tool |
| WhatsApp Web | No | n/a | Browser extension scheduler |
On iPhone, iOS sandboxing stops any tool from tapping WhatsApp's send button on your behalf. Shortcuts can open WhatsApp at a set time with your text pre-filled, but you stand there and tap Send yourself. That's a reminder, not a scheduled send. The iOS Shortcuts limits are covered in the iPhone and Android without-an-app guide.
The irony: the platform with the most on-device flexibility, Android, still pushes you toward a non-phone solution once reliability matters, because the fragile screen-tap dependency is the whole problem. Whether you're on Android or iPhone, the route that survives an OS update and a locked screen is the same: schedule through WhatsApp Web. Around 72% of smartphones worldwide run Android (Statista, early 2026), so most people asking how to schedule WhatsApp messages on Android land here, on a workaround, because the native answer is still no.
Frequently Asked Questions
Can I schedule a WhatsApp message on Android without any app?
Not in a way that actually auto-sends. WhatsApp itself has no native scheduler on Android, and the WhatsApp Business app's greeting, away, and quick-reply tools are auto-replies, not scheduled outbound messages. To schedule a message that fires on its own, you need a third-party tool, either an on-device automation app like Tasker or MacroDroid, or a WhatsApp Web scheduler.
Does Tasker really send WhatsApp messages automatically?
Yes, but with conditions. Tasker paired with the AutoInput plugin uses Android's accessibility service to tap the send button at a scheduled time. The phone must be on and unlocked, the accessibility service must be enabled, and battery optimization must be disabled for Tasker. It also breaks when WhatsApp updates its UI, so test it before relying on it.
Why did my scheduled WhatsApp message not send on MacroDroid?
The three usual causes are: the phone was locked or the screen was off (MacroDroid's WhatsApp Send can't tap a sleeping screen), battery optimization froze MacroDroid before the trigger fired, or the UI Interaction accessibility service got disabled after an app update. Set MacroDroid to Unrestricted battery use and re-enable accessibility to fix it.
Is there a free WhatsApp message scheduler for Android?
Yes. SKEDit offers a free tier (up to 5 scheduled messages a day) using the Accessibility API, and it supports groups and recurring sends. MacroDroid has a free tier too. For computer-based scheduling, Blueticks' free plan schedules one message at a time on WhatsApp Web. All on-device free tools share the phone-must-be-on limitation.
What's the most reliable way to schedule WhatsApp messages on Android?
Schedule through WhatsApp Web with a browser extension rather than on-device automation. Browser-based scheduling sends from your linked web session, so it doesn't depend on your phone being awake, unlocked, or running an accessibility service that breaks on WhatsApp updates. It's also the cleanest route for recurring sends and sending to a list.
