You schedule a message for 7 AM, shut the laptop, and go to bed. In the morning the message is either in the chat or it isn't, and nobody tells you which until you look. Almost every guide on this topic blurs "device off" into a single condition. It is two conditions, and mixing them up is exactly why people find an unsent message waiting for them at breakfast.
Do scheduled WhatsApp messages send when your phone or computer is off?
It depends on what does the sending. Phone off is fine: WhatsApp Web and browser extensions keep sending. Computer off is not, unless the send runs on a server: the WhatsApp Business API, or Blueticks' Pro offline gateway.
- Phone off, computer on - sends normally
- Phone off for over 14 days - stops, WhatsApp unlinks the device
- Computer off, browser extension - does not send
- Computer off, server-side sender - sends normally
- Both off, no server - nothing sends
The rest of this article is about why those five lines are true, which sender puts you in which row, and how to prove it on your own account in about three minutes. If you want the mechanics of scheduling inside the browser first, that is covered in the WhatsApp Web scheduling guide.
Two switches, not one
"Device off" is really two independent switches: your phone, and the machine running the sender. WhatsApp's multi-device architecture decoupled them in 2021. Your phone is the account owner, but it is not the mail carrier. Whatever is holding the live session at send time is.
That gives you a simple test to run on any tool you are considering:
Where does the code that presses Send actually run?
If the answer is "in a browser tab on your machine," your computer has to be awake. If the answer is "on someone's server," it does not. If the answer is "on your phone," then your phone has to be awake, and usually unlocked, which is a stricter requirement than most people expect.
Your phone being off is almost never the blocker. Your computer being off almost always is. Everything below follows from that.
Which senders survive which device state
Six ways people actually schedule WhatsApp messages, and what each one needs to be powered on.
| Sender | Works with phone off? | Works with computer off? | Who it's for |
|---|---|---|---|
| WhatsApp Web / Desktop, sent by hand | Yes, up to 14 days | No | Anyone at a desk |
| Browser extension scheduler (Blueticks free tier) | Yes | No | Solo operators, daytime sends |
| Android automation (Tasker, MacroDroid, SKEDit) | No, phone must be on and usually unlocked | Yes | Android tinkerers |
| iPhone Shortcuts | No, phone must be on | Yes | Reminders, not real sends |
| WhatsApp Business API via a provider | Yes | Yes | Approved businesses, per-message fees |
| Blueticks Pro offline gateway | Yes | Yes | Operators who need overnight sends |
Two rows send with everything dark. Both of them work for the same reason: the session lives on a server, not on your hardware. Everything else is running on a device you own, and a device you own can be off.
If you are still choosing between categories rather than device states, the schedule vs automate breakdown is the better starting point.
Stop guessing whether your 7 AM message went out. Blueticks is free to install and schedules straight from WhatsApp Web with no API application and no per-message fees, from your own number. When you need sends to fire with the laptop shut, switch on the Pro offline gateway. Start free.
Why your phone can be off (and the 14-day fine print)
Your phone can be powered down, out of battery, in a drawer, or on a plane. A linked WhatsApp session keeps working. WhatsApp's Help Center is explicit that linked devices work even when your phone is not connected to the internet, and that you can link up to four companion devices to one account (About linked devices).
This is the part most articles get right and then stop. There is a limit, and it is a hard one.
If your phone goes unused for more than 14 days, WhatsApp logs out every linked device. Not a warning, not a degraded mode. The session is gone and the QR scan has to be redone from the phone. That applies to WhatsApp Web, to WhatsApp Desktop, and to any scheduler riding on a linked session, including a hosted gateway.
In practice this only bites two groups:
- People who scan the QR from a spare phone or a second SIM they then leave in a drawer.
- People who set up an always-on gateway from a phone they are about to replace.
The fix is boring and takes 60 seconds: open WhatsApp on the phone, let it sync, and the 14-day clock resets. Put a recurring calendar reminder on it if the account matters. This is the single most common way a perfectly configured "offline" setup silently dies three weeks after you built it.
Why your computer usually cannot be off
Here is the sentence most tool comparisons will not write plainly, so I will.
The Blueticks extension needs your computer on.
Same for every other browser-extension scheduler, without exception. An extension is JavaScript running inside Chrome. It drives a live WhatsApp Web session, waits for the scheduled minute, and injects the message into the chat the way you would if you were sitting there. If Chrome is not running, that code is not running. If the laptop is asleep, suspended, hibernated, or shut down, that code is not running.
What that means concretely:
- Lid closed, machine asleep: the message does not send at its scheduled time. It sends when the machine wakes and the session reconnects, which is late, and "late" on a 9 AM client follow-up is the same as wrong.
- Machine shut down overnight: nothing goes out until you boot it.
- Chrome quit but the machine awake: nothing goes out. The tab is the runtime.
- Machine awake but WhatsApp Web logged out: nothing goes out.
Sleep settings are the quiet killer. A laptop set to sleep after 15 minutes of inactivity is, for scheduling purposes, a computer that is off. If you are going to run a browser-based scheduler for anything that fires outside your working hours, you need a machine that stays awake, and you need to actually verify it stays awake rather than assume the power settings do what the label says.
This is also why recurring schedules are where people get burned. A one-off send you can babysit. A weekly 8 AM reminder running for six months on a laptop you close every night will miss sends, and you will not notice until a client asks why they stopped hearing from you.
Phone schedulers need the phone awake, which is worse
There is a persistent belief that phone-based scheduling apps are the offline answer, because the phone is always with you and always on. The premise is wrong in a specific way.
Android automation (Tasker, MacroDroid, SKEDit and similar) works by hooking Android's accessibility services and driving the WhatsApp app UI: open the chat, paste the text, tap the send button. The phone has to be on. The screen usually has to be on. In many configurations the device has to be unlocked, because a locked screen means the automation cannot see or tap the send button.
Then Doze gets involved. Google's own documentation is unambiguous: when a device is unplugged, stationary, and the screen is off for a while, Android enters Doze mode and "defers background CPU and network activity," suspends network access, ignores wake locks, and defers AlarmManager alarms to the next maintenance window (Android developer docs). A phone on a nightstand at 3 AM is the exact scenario Doze was designed for. Your 7 AM automation may fire at 7:00, or at 7:11 when the next maintenance window opens, or not at all if the OEM added its own battery optimizer on top. This is why Android scheduling apps get one-star reviews that all say the same thing: "worked for a week, then started missing."
iPhone Shortcuts is more honest about what it is. A personal automation can trigger at a time you set, open WhatsApp, and pre-fill the message. You still tap send. It is a very good reminder. It is not a scheduled send, and it certainly is not a send that happens while the phone is off.
The Android scheduling walkthrough covers the setups that hold up best if you are committed to this route. But be clear-eyed about the trade: you have swapped "my computer must be on" for "my phone must be on, awake, and not being throttled by the battery optimizer." That is not an upgrade.
The only two ways to send with everything off
Both options move the send off your hardware. That is the entire trick. There is no third mechanism.
1. The WhatsApp Business API
The WhatsApp Business API (now the Cloud API) genuinely sends server-side. Meta's infrastructure delivers the message. Your phone can be off, your computer can be off, your office can be on fire. The message goes out. If you are building anything programmatic, this is the real thing, and it is covered properly in the WhatsApp scheduling API guide.
Now the honest cost, because the "just use the API" advice is given far too casually:
- You need approval. A Meta developer account, a Meta app, a WhatsApp Business Account, and App Review for the permissions you request. This is not an afternoon.
- You will use a provider. Most businesses go through a Business Solution Provider rather than integrating with Meta directly, which is another vendor, another contract, another bill.
- Templates outside the 24-hour window. When a customer messages you, a 24-hour customer service window opens and you can reply freely. Outside that window you can only send pre-approved template messages, in the Marketing, Utility, or Authentication categories.
- You pay per message. Meta moved from conversation-based to per-message pricing effective July 1, 2025, with rates that vary by template category and recipient country (Meta's pricing documentation).
- It is not your number. This is the one that stops most people. Meta's own phone number documentation states that registered numbers "cannot be used with WhatsApp Messenger." A number already active on WhatsApp has to be deleted from WhatsApp before you can register it on the platform (Cloud API phone numbers).
Read that last one twice. The API is not a way to schedule messages from the WhatsApp account you already use. It is a separate business channel on a separate number. For a support desk sending order updates, that is correct and good. For a consultant who wants a follow-up to leave her own number at 8 AM tomorrow, it is the wrong tool at roughly a hundred times the setup cost.
2. A hosted gateway on your own number
The other route keeps your existing number and moves the session onto a server. Blueticks' offline gateway is a Pro plan capability. You scan a QR code once from your phone's Linked Devices screen, exactly as you would for WhatsApp Web, and the session lives on Blueticks' servers instead of in your Chrome tab (engine management guide).
After that, your laptop is irrelevant to delivery. Close it, shut it down, drop it in a lake. Scheduled messages, recurring reminders and campaigns fire from the server. Your phone can be off too, subject to the same 14-day linked-device rule as everything else on WhatsApp.
The trade-offs, stated plainly: it is a paid tier, it is bound by the 14-day rule, and it uses your personal or business number rather than a separate API channel, which means WhatsApp's normal rules about bulk and unsolicited messaging apply to you in full. It is the right answer for scheduled sends from your own number outside your working hours. It is not a bulk cold-outreach machine, and treating it as one is how numbers get banned.
Test it yourself in three minutes
Do not take my word for any of this, and do not take a vendor's. Run this on your own setup before you trust a real send to it. It costs three minutes and it tells you exactly which row of the table you are actually in.
- Message yourself. Open WhatsApp Web and start a chat with your own number. WhatsApp allows this and it makes a perfect test target.
- Schedule a message three minutes out. Text like
offline test 07:14. Note the exact minute. - Close the laptop lid. Do not just close the tab. Let the machine actually sleep. Walk away from it.
- Watch your phone. At the scheduled minute, look at the chat on your phone.
- Read the result.
- Message arrived on time, laptop shut: you have a server-side sender. You are safe overnight.
- Nothing arrived, and it turns up the moment you open the laptop: you have a browser-based sender. It needs the machine awake. Plan around that.
- Nothing arrived at all: the session is broken. Check whether WhatsApp Web is still linked before you debug anything else.
Then run the inverse. Schedule another test, leave the computer awake, and power your phone all the way off. It should arrive. If it does not, your linked session has expired and you need to re-scan.
What breaks in the real world: power settings that "should" keep a machine awake but don't, a second WhatsApp Web tab in another browser that steals the session, a phone that has been off for over two weeks, and a company laptop with a forced overnight update policy. Each of those turns a working scheduler into a silent one. Check the send status in your scheduler dashboard rather than assuming a queued message means a sent message.
Frequently asked questions
Can you send a WhatsApp message when your phone is off?
Yes, as long as something else is holding a linked WhatsApp session: WhatsApp Web, WhatsApp Desktop, a browser extension on an awake computer, or a server-side gateway. WhatsApp's multi-device support means linked devices work without your phone connected. The exception is the 14-day rule: if your phone stays unused for over 14 days, WhatsApp logs out every linked device.
Will a scheduled message send if my laptop is asleep?
Not with a browser extension. The extension runs inside Chrome, so a sleeping machine means the send does not fire on time. It typically goes out when the machine wakes and reconnects, which is late. Only a server-side sender, the WhatsApp Business API or a hosted gateway like Blueticks Pro, sends while your computer is off.
Does the Blueticks free plan send when my computer is off?
No. The Blueticks extension needs your computer on. The free and lower paid tiers schedule from WhatsApp Web in your browser, which means the machine has to be awake at the scheduled minute. Offline sending with the computer off is the Pro plan's gateway.
Do Android apps like SKEDit or Tasker work when the phone is off?
No. They drive the WhatsApp app through Android's accessibility services, so the phone must be powered on, and usually unlocked. Android's Doze mode also defers background alarms and network access when the device is idle with the screen off, which is why these automations miss or delay overnight sends.
Is the WhatsApp Business API worth it just for scheduling?
Rarely, for an individual. It genuinely sends regardless of your devices, but it requires Meta approval, typically a provider, pre-approved templates outside the 24-hour customer service window, per-message fees, and a number that cannot also be used in the regular WhatsApp app. If you want scheduled sends from your existing number, a hosted gateway is the cheaper path. If you are building an automated product messaging system, the API is the right tool.
