WhatsApp users have long accepted one hard rule: tapping send means the message leaves immediately. That assumption is now being rewritten in beta, where the messaging giant is testing the ability to compose something today and have it arrive at a chosen moment tomorrow — or two weeks from now. The option appears in the Android beta build 2.26.40.7, and it drags the app closer to a capability rivals have offered for years.
- Long-press to schedule: holding the send button opens a date and time picker inside the conversation, with a scheduling window of 10 minutes to two weeks.
- Pending messages stay manageable: queued items live in a dedicated section of each chat’s information screen, where they can be reviewed, rescheduled or deleted before dispatch.
- Privacy is unchanged: scheduled content keeps end-to-end encryption and is delivered even when the phone is offline or the app is closed.
- Access is narrow for now: only a small group of Android beta testers has it, and no date has been announced for the stable release or for iOS.
What the beta actually does
The mechanism is deliberately frictionless. There is no third-party app, no separate scheduling menu and no need to leave the chat. Once the text is written, a long press on the send arrow surfaces a selector at the bottom of the screen; after confirming a day and a time, the message is queued and the application handles delivery on its own.
The supported window is wider than it first sounds: the earliest slot is 10 minutes away, the latest two weeks. Text is not the only payload — links, photos and videos can be scheduled too, albeit with a notable restriction. Only a single image or video can ride along per message, so assembling an entire album in advance is off the table, and deleting a queued item before it fires leaves the recipient with no notification and no trace that it ever existed.
Groups behave differently. A scheduled message only reaches members who already belonged to the conversation when it was queued; anyone who joins afterwards will not receive it, even if they are in the group by the time it goes out. On the receiving side, testers report that the other party sees no marker indicating the message was prepared in advance, though it remains unconfirmed whether that behaviour will survive into the final build. Nor has the company said whether scheduling will eventually be tied to a paid plan.
Architecture explains part of the delay, priorities explain the rest
The obvious comparison is Telegram, which has supported scheduled messages since 2019. Instagram Direct introduced the capability in 2025, and workplace platforms such as Teams and Slack have let users time their sends for years. For an app with more than 2 billion active users, the lag is conspicuous.
Some of the explanation is technical. End-to-end encryption means WhatsApp’s servers are not meant to read message contents, yet a scheduled message requires the infrastructure to hold something temporarily. Reconciling a queue with that security model takes engineering care, even if the underlying privacy promise stays intact.
The rest is a question of investment. WhatsApp has spent recent years pushing revenue-generating tools — the Business API, product catalogues and payments in India and Brazil — ahead of consumer conveniences that produce no direct income. The arrival of scheduling reads as a response to competitive pressure rather than a long-standing internal priority.
Work, boundaries and the right to disconnect
The workplace angle is the most consequential. Eight European Union countries have passed right-to-disconnect legislation over the past four years, following France’s 2017 framework and Spain’s 2018 recognition of digital disconnection within data protection law. In that environment, drafting a message at 11 p.m. and having it land at 9 a.m. carries real value: it satisfies the sender’s urge to get a task off their plate without intruding on the recipient’s evening.
It is, however, an imperfect fix. The recipient cannot tell when a message was written, only when it arrived, so the tool does not by itself settle whether making contact is appropriate. Nor is it clear how scheduling will behave in busy group chats, where the timing of a message can shape who replies first and how the thread is interpreted.
More immediately, users will want to know whether queued messages stay visible in the conversation as pending items, the way Telegram displays them, or simply materialise at the appointed hour. That design decision will determine whether scheduling feels like a deliberate tool or a source of confusion about what has genuinely gone out.
The feature is less a novelty than an admission that the instant-send contract no longer fits how people actually use messaging. Scheduling shifts a small but meaningful amount of control back to the sender, and it arrives at a moment when the boundaries between work and personal time are being written into law across Europe. As the capability graduates from beta to the wider user base, the interesting question will not be whether it functions, but how quickly it recalibrates expectations around availability — turning silence at midnight into something chosen deliberately rather than a courtesy people happen to extend.
Sources & References