Compose & send
Targeting an audience, attaching an image, varying your message per group, reading the delivery preview, scheduling, and watching a send go out live.
Open ComposeCompose is the send form: pick who, write what, check the preview, go. It unlocks once you've categorized at least one group.
Targeting#
Three ways to say who gets it, in increasing order of precision:
- Category chips —
first-year,alumni, or all groups. Pick one or several, matching the categories you gave groups on the Groups page. If your organisation has saved segments, they appear under "Included saved segments" — click one to apply its audience. - Specific groups — pick them individually. When you name groups explicitly, that list is used as-is and the category chips are ignored.
If your organisation has several numbers, you also choose which number sends. Groups belong to numbers, so switching the number changes the available audience.
Writing the message#
Plain text with WhatsApp formatting. Both WhatsApp's own markers and the markdown you probably type by reflex
work — **bold** is converted to WhatsApp's *bold* on the way out, and ~~strike~~ to ~strike~, so you
don't have to remember which app you're in.
Full guidance on what to actually write: Writing messages that land.
Personalisation tokens#
| Token | Becomes |
|---|---|
{groupName} |
The name of the group receiving the message |
{category} |
That group's category |
So Hi {groupName}! arrives as "Hi Year 2 — Law!" in one group and "Hi Alumni 2019!" in the next. The
message preview in Compose shows the tokens as you typed them — they are filled in per group when the send goes out.
Message variation (spin tax)#
Wrap alternatives in braces separated by pipes and PromotionBot picks one at random per group:
{Hey|Hi|Hello} everyone — {tickets are live|tickets just dropped}!
Every group gets a slightly different message. This matters more than it looks: identical text blasted to thirty groups in one window is a textbook spam signal, and varying it is one of the cheapest ways to look like a person. See Staying unbanned.
Braces without a pipe are treated as a token, not a variation — {groupName} keeps working exactly as above.
Image#
Click Image to attach a picture (the asset library also accepts video, audio, and PDFs) and your text becomes its caption. Uploads count against your plan's storage allowance (Plans & billing).
Files you'll reuse stay in the library and can be picked again later rather than re-uploaded each time.
Templates#
The Templates row holds your saved message presets. Click one to fill the composer; Manage presets → creates, edits, and deletes them. A preset can optionally remember its groups too.
Delivery preview#
Before you send, Compose shows a server-computed summary of what will actually happen:
Reaches 12 of 14 groups · 1 cooling down until 18:40 · 1 over daily cap
This is the most useful thing on the page. It is computed by resolving your audience and running the same gate checks the real send runs — inactive groups, caps, the cooldown — so it can't quietly disagree with the outcome. If the number is inside its quiet hours, the preview says it sends when quiet hours end, with that time in your own timezone — and "Send now" becomes Send when quiet hours end: it schedules the message for the moment the window closes instead of sending it.
Skipped groups are listed with the reason. Nothing is silently dropped.
If a daily cap is what's blocking groups, the preview says so and offers the upgrade path — but read Groups before raising a cap. Usually the right fix is a narrower audience, not more volume into the same one.
Send now, schedule, or repeat#
- Send now — dispatches immediately.
- Schedule → One-time — queues it for a date and time in your organisation's timezone. The scheduler fires it whether or not anyone's logged in. Two identical pending sends scheduled for within a minute of each other are rejected, however far apart you created them — so a double-click can't double-send, and neither can re-queueing the same thing for the same send time tomorrow.
- Schedule → Recurring — creates a repeating send on chosen weekdays ("every Mon/Wed"). You can see and stop it later on the calendar (Stop the series) or the Campaigns tab (Stop repeating).
- Campaign (admins) — saves the message as a named campaign, with a kind and a send time, for anything you'll want to name, pause, or measure over time. A campaign has no end date unless you set Run until; with one set, the form shows how many sends it covers ("Ends after 7 sends"). To remove an end date later, edit the campaign and empty the Run until field. After you save, you land on the Campaigns tab with the new campaign open.
On a phone, the main button (Send now, Schedule, Save campaign…) and the number of groups the send reaches stay pinned above the bottom menu, so you don't have to scroll to the end of the page to send.
If you restore a message after a failed send and its sender, category or group has since been removed, Compose says what was dropped instead of sending to it. If you stop tracking a send that never reported progress and then send again, Compose asks first, because the earlier send may still be running.
If a required field is missing (message, campaign name, date, time, weekday), Compose marks that field with a message next to it and moves you to it; the message disappears as soon as you fix the field.
If you're a non-admin sending on the shared number, Send now and Schedule each create a pending request for an admin instead of a send. See Team, roles & approvals.
When a send is too big for the hour#
If the fanout would take this number past its rate ceiling — 60 messages an hour, 400 a day — the send stops before dispatching anything and tells you how much room is left. Admins get a Send anyway — I accept the risk option; everyone else needs to split the audience or wait.
This isn't a plan limit and upgrading won't move it. Details and when it's reasonable to override: sending past the rate ceiling.
Live progress#
After "Send now", Compose swaps the form for a live progress view: a bar, a per-group status list, and an ETA based on the pace observed so far.
It is slow, and that's the point. Before each group PromotionBot sends a typing indicator and waits a moment scaled to how long the message is; after each group it waits a randomised few seconds, occasionally a longer pause. A forty-group send takes several minutes. There is no fast mode — the pacing is the anti-ban feature. Exact numbers: the send cadence.
Until the group list appears, keep the page open — the request can still be refused, and your text is unsaved. Once the list is showing you can move around the app; the send continues server-side. The Dashboard shows a small card — "Sending 3 of 12 · your message" — that keeps counting and then shows the result ("Sent to 12 groups", "Stopped — sends are paused", or how many failed) until you dismiss it. Open Compose again (or use the card's Open in Compose) and the live progress view is back where you left it. When a send from the Dashboard's quick-send box reaches only some groups, its card offers Resend to N failed groups: one resend of the same text to exactly the groups that failed, available once per send.
Reloading the page or closing the tab loses the live view, not the send: the message still goes out, and failures are collected on Analytics (below). "Back to compose" after the summary gives you an empty form, so the message you just sent is never one click away from going out twice. After an undo or a fix-text run, or a send that reached no group, the text stays in the composer and counts as unsaved again.
Scheduling works the same way: once "Schedule send" succeeds, the composer empties, and the confirmation names the time ("Scheduled for Fri 16 Oct, 20:00") with a View in calendar link.
At the end you get a summary: delivered, skipped, failed, with reasons. Failures are also collected on the Analytics page.
Test sends#
There is a test send button on Numbers (and in the onboarding wizard). It sends a fixed check message to the linked account's own chat to prove the connection works end to end.
Know what it does not do: it is not a preview of your draft. It sends canned text, not what you've typed, and
the self-send path applies only formatting normalisation — no
spin-tax variation, no {groupName}
substitution, and no link shortening. It
is also admin-only on the shared number.
To check a draft before it goes wide, use the delivery preview — which shows which groups will receive it and which will be skipped, though not the per-group token and spin text — or send to a single small group first by picking that group explicitly.
Links#
Any URL in your message is automatically rewritten into a per-group tracking link. You don't do anything; just paste the real URL. That's what makes Analytics able to tell you which audience clicked.