Schedule anything, to anyone.

Row by row, on the five axes that actually differ — how it is delivered, how precise the timing is, what happens when your phone is off, what the fallback notification does, and what each network adds to the long-press send menu:

Messages go out from your own account, the same one you use every day, so the app is careful with it in two ways.

It will only send to people you already talk to. Recipients come from your existing conversations and platform contacts, never from your raw address book, so there is no way to schedule a message to someone who has never heard from you. That constraint does more for the safety of an account than anything else here.

And it paces every outgoing message automatically, because sending faster than a person plausibly could is the other thing that gets an account flagged.

• About 3 seconds between messages, varied rather than fixed — an identical interval is itself a pattern no person produces
• Up to 60 messages an hour, per platform
• A separate budget for each platform, shared across the whole app — a broadcast and a shortcut running at once cannot outpace the limit between them
• Kept across restarts — reopening the app does not hand you a fresh allowance

You are told where you stand: the composer estimates when a large broadcast will finish before you schedule it, and a message held by the hourly limit reads Waiting with the time it continues. Shortcuts are the exception — a Send action cannot sit out an hour-long wait, so past the limit it stops and tells you when sending resumes.

Pacing lowers the risk; it cannot remove it. Sending unsolicited messages in bulk can get any account restricted on any platform, however slowly it goes out. Message people who expect to hear from you.

Yes, at any point — and the reason it works mid-run rather than at the end is that cancelling and pausing are checked before every single recipient, not once when the broadcast starts. A run that has hours left to go still stops at the next person in the queue.

Nothing is ever sent twice. Resuming continues from the next unsent recipient rather than starting from the top, and the same is true if delivery is interrupted for any other reason. Pause All Delivery puts a banner across the library for as long as the hold is on, so it cannot be left on by accident.

It covers scheduled delivery only: a shortcut you are running is stopped with Shortcuts’ own controls, and a message you send by hand is a single send you already chose to make.

The one thing none of them can do is unsend. Stopping a broadcast governs who is still to come, never who has already received it.

Nothing is lost. On WhatsApp, Instagram, and Messenger the message stays in your pending queue and goes out the moment AI Reply Assistant next runs a background check or you open the app — and you get a notification at the scheduled time with a Send Now button if you would rather not wait. Telegram is unaffected either way: its messages are already on Telegram's servers.

The four habits that keep an on-device send on time are in Best practices for on-device scheduling above.

Text and rich text, photos, videos, documents, voice messages, polls, events, checklists and link previews — one-off, as a broadcast to many recipients, or on a recurring schedule, with personalisation variables resolved per recipient.

Four exceptions, every one of them on Meta: Instagram and Messenger carry neither events nor checklists; Instagram cannot schedule a document; polls schedule to groups only on both; and bold and italic are not rendered in either one’s DMs, though links still preview.