WhatsApp brings scheduling to iOS a week after Android

WhatsApp has started testing message scheduling on iOS, as reported by the website WABetaInfo. The feature reached subscribers of the TestFlight program.

The move came a week after the feature debuted in the Beta version for Android.

The idea is simple. In addition, the user schedules a message to be sent at a future date and time, instead of sending it right away.

Other communication apps already offer a similar solution. Slack and Teams are on that list.

How scheduling works in practice

The flow follows the pattern already known in the market. First, the user writes the message as usual.

Next, just tap and hold the send button. That brings up the date and time settings.

The current limit reaches two weeks in advance.

All scheduled messages are gathered in a dedicated section. It appears on the group's or contact's details page.

Privacy was also taken into account. Until the content is sent, only the author can see and review it.

Why this matters for WhatsApp's professional use

The app has become a work channel at many Brazilian companies. Therefore, this feature solves a very real annoyance.

The first case involves business hours. Writing at night and delivering in the morning avoids interruptions outside working hours.

The second case deals with time zones. Distributed teams gain predictability in communication.

In addition, there's the obvious personal use case. A birthday message scheduled in advance falls into that category.

For those who handle support or customer service, the change also matters. Follow-up reminders no longer depend on an external alarm.

The current stage of testing

It's worth tempering expectations. On iOS, the feature appeared in version 26.42.10.19 of WhatsApp Beta, distributed via TestFlight.

For now, there's no release date for the general public.

Even so, the expansion across platforms indicates progress. The feature went from Android to iOS in just one week.

What to watch going forward

First, watch how it behaves with the device offline. Local scheduling depends on the device, so delivery may vary.

Second, note the two-week limit. That cap clearly defines the scope of use for anyone thinking about long-term automation.

Third, assess the impact on API-based flows. Those who already build on the official platform usually handle scheduling in their own backend.

Finally, test it as soon as it reaches the stable channel. Beta features often change behavior before the final release.

Follow our profile on Instagram!