A scheduled message is useful when the timing is part of the work: a reminder tomorrow morning, a follow-up after a delivery, or a message that should not wake a customer tonight.

It is also a feature that deserves a little care. Check the recipient, timing, and wording before you schedule. For bulk messages, check consent and policy before you think about speed.

Schedule a message in a conversation

Open the customer conversation and write the message as you normally would. Add an attachment first if the follow-up needs one, then use the schedule control beside the composer.

Choose a future date and time. WATeamInbox shows the timezone used for the schedule, so read it before you confirm. A time that looks right on your laptop can be wrong for a teammate working elsewhere.

Write for the future reader

A scheduled message may be sent after the current conversation has moved on. Include enough context that the customer understands why they are receiving it, but do not include details that could become stale.

Before you confirm, check:

the customer and connection are correct
the date and timezone are correct
the message does not depend on an unconfirmed detail
any attachment is the final version

You can review upcoming scheduled messages from the conversation before they are sent.

WATeamInbox schedule message popover with future send time presets — Choose a preset or a future time in the workspace timezone before scheduling the follow-up. The date and conversation shown here are synthetic demo data.

WATeamInbox conversation showing an upcoming scheduled message with edit and cancel actions — Choose a preset or exact future time, then review it before scheduling. The message and time shown here are synthetic demo data.

Use broadcasts for a real audience

Broadcasts are for permission-gated bulk work, not for sending the same message to every contact by default. Build the audience from a clear set of contacts or tags, preview the recipients, and make sure the message is appropriate for everyone included.

Keep the audience narrow enough to explain. “Customers with a delivery update” is a useful rule. “Everyone in the database” usually needs another question first.

WATeamInbox broadcast wizard showing the message step with personalisation tokens — Write the campaign message separately from the audience, then use supported personalisation tokens when they help. The campaign shown here is synthetic demo data.

WATeamInbox broadcast preview showing recipients, delivery estimate, and sample message — Review the audience and sample message before moving to the schedule step. The recipient counts and message shown here are synthetic demo data.

Only send messages to people your business has a reason and permission to contact. Respect opt-outs and your organisation’s communication policy. WhatsApp account restrictions remain possible, especially when a team sends high volumes or messages that recipients do not expect.

WATeamInbox paces bulk work and records per-recipient outcomes, but no tool can make an unwanted message safe. Test a small audience and keep a human review step for important campaigns.

WATeamInbox broadcast schedule step showing timing, send pace, and risk acknowledgement — The final step keeps timing, pacing, and the bulk-messaging risk acknowledgement visible before scheduling. The counts and date shown here are synthetic demo data.

After you schedule

Tell the team what the scheduled message is for. If another person needs to cancel or reschedule it, they should not have to reconstruct the reason from the thread.

For a one-to-one follow-up, a short shared note is usually enough. For a broadcast, keep the audience rule and approval context with the job in your team’s normal process.

Keep going

Try the workflow with one real conversation.

Create a small Cloud workspace and test the handoff with a teammate, or use the open-source application on infrastructure you control.

Create a Cloud account See Cloud plans Read self-hosting docs

Schedule a message in a conversation

Write for the future reader

Use broadcasts for a real audience

Check consent and account risk

After you schedule

Try the workflow with one real conversation.