Features

Events

Describe an event once and get a whole promo timeline — save-the-date through day-of — with cadence presets, editable copy, and conflict warnings before you launch.

Open Events

Most promotion isn't one message, it's five spread over two weeks. Events is the page that writes that timeline for you: describe the event once, pick how hard you want to push it, and PromotionBot generates the queued messages leading up to it. Edit what you like, drop what you don't, launch.

Creating an event#

You give the event a name, a date and time, and an audience (categories or specific groups — same targeting as Compose). Optionally a location, a link, and a type — a party gets different default copy than a deadline.

From that, PromotionBot proposes a timeline.

The timeline#

Each message in the timeline has a role, which determines both when it goes out and what the default copy sounds like:

Role Default timing
Save the date 14 days before, midday
Announcement 7 days before, midday
Reminder 3 days before, early evening
Last call 1 day before, early evening
Day of On the day, morning (10:00) — for a morning event, 2 hours before it starts but never before 07:00

All times are in your organisation's timezone. These are the defaults a role carries on its own — a cadence preset can override them, and the deadline preset does exactly that (its 3-day reminder goes out at midday, not in the evening).

The day-of message always goes out before the event starts. For an event at 09:00 it is sent at 07:00; for an event that starts at 07:00 or earlier (or just after midnight) there is no day-of message, because there is no reasonable morning slot before it. Only a message on the event's own day is ever treated as the day-of ("Today: …"); when the last message is the day before, it reads as a last call instead.

Cadence presets#

Rather than assembling that by hand, pick a shape:

Preset Messages Timeline
Light 1 Announcement the day before
Standard 3 Announcement (7 days), reminder (1 day), day-of
Aggressive 5 The full ladder above
Deadline 3 Reminder (3 days), last call (1 day), morning-of at 08:00 (earlier for a morning deadline)

Standard is the right default. Aggressive is for your one big event of the year, not for every drinks night — five messages about the same thing is where communities start muting you. Deadline is shaped for applications and sign-up cut-offs, where the final morning is what matters.

A template card on the empty Events page starts the timeline from its preset (Party → Aggressive, Study session → Light, Recruitment → Standard); a blank event starts with three messages spread evenly from now to the event, which matches no preset until you pick one. Even spreading (the blank start, and Auto-space evenly) keeps messages in waking hours: each time is rounded to the quarter hour and kept between 08:00 and 21:00 in your organisation's timezone — or outside the sending number's quiet hours, if it has them — moving a night-time message later, or earlier if later would pass the event start. If the messages can't all fit before the event, nothing is moved and the timeline says so; times you set by hand are never moved. If a saved message still falls inside the sending number's quiet hours, creating the event or saving a draft shows a warning (nothing is moved; the send simply waits until the quiet hours end). A preset is highlighted only while the messages are exactly its own — move, add or delete a message and it becomes a custom timeline.

The preset only sets the starting shape. There is no message-count control — to end up with a different number of messages, add or delete messages in the timeline (see Editing the timeline).

Messages that would land in the past — or within the next five minutes — are dropped automatically, so creating an event two days out with the Aggressive preset won't try to send a save-the-date for last week. The wizard's Review step counts only the messages that will be created and names the ones skipped for being in the past.

Editing the timeline#

Every message is editable: rewrite the copy, move the time, change the role label to anything you like (a custom "Early bird" message is fine), add messages, delete messages. A timeline can hold up to 30 messages, which is far more than you should ever use.

No message can go out after the day of the event — except one you tick After the event. Use it for a doors-open note after midnight, an afterparty, or a thank-you the next morning: a ticked message goes out at or after the event's start, and can be scheduled until the end of the day after the event. (A note before the start is just an ordinary message — leave it unticked.) It sits outside the promo order (it's never the day-of reminder), Auto-space evenly leaves it where it is, and if you leave its text blank it gets a short thank-you note you can edit like any other message. Saved cadence presets don't include after-the-event messages.

If your deployment has AI enabled, you can have message copy suggested per message. Same rule as everywhere else: it's a draft, you're the editor.

Saved cadence presets#

If your organisation has a house style — "we always do save-the-date, two reminders, and a morning-of" — save it as your own preset. Admins can publish a preset to the whole organisation so committees inherit it instead of reinventing the cadence each time; anything you don't publish stays private to you.

Changing a draft's audience or timeline#

Until you launch, a draft's audience, sender and timeline stay editable: open the event and choose Edit audience & timeline. You get the same category / specific-group picker and the same message rows as when you created it. Changing only who hears it, or the number it sends from, keeps every message exactly as it is. Changing the timeline — a different rhythm, more or fewer messages, new send times — rebuilds the messages, so you're asked first: copy you edited on the old messages is replaced (text you write in the rows themselves is kept). Changing the event's date rebuilds the timeline too, and also asks first. Specific groups have to be on the number the event sends from, so the picker only lists that number's groups; if you switch the sender, any groups you picked on the old number are named and have to be removed before you can save. If you're a member with a launch request waiting for an admin, saving changes here — or saving any message's text or time — makes that request outdated: an admin can no longer approve it, so send a new request afterwards. Once an event has launched its audience, sender and timeline are fixed; Clone it to get an editable draft of the same plan, or make a Revised plan to copy it, messages and all, to a new date.

Before you launch#

Launching materialises the timeline into real queued sends. Before it does, PromotionBot checks for the things that go wrong:

  • Conflicts — other events or scheduled sends hitting the same audience around the same time. Two committees promoting different parties into the same year group on the same evening is the classic one. Click the conflicts line in the checklist to see which sends they are; an event you can open is a link.
  • Health warnings — groups that will be skipped or squeezed when a message sends: an empty audience, suppressed groups, inactive groups, groups at risk of hitting their daily cap, messages already in the past, and two messages landing on the same day. Cooldown is not among them — it's evaluated when each message actually sends, not at launch.

Launch always sends the saved messages. If you've typed into a message without saving it (the card is marked Unsaved), or have unsaved changes in Edit audience & timeline, Launch stays disabled and says why until you save or undo them — and leaving the page (or cloning it) asks first, so typed text isn't lost by accident.

Launch (or Request to send, if an admin approves your launches) is at the top of the event as well as under the checklist; both are disabled for the same reasons, shown under the checklist.

Clicking Launch never sends straight away. It opens a confirm that shows:

  • the fan-out — N messages × M groups = F sends;
  • your quota — how many messages are left on your monthly plan allowance (or your trial allowance while you're on a trial);
  • every health warning, labelled Blocking, Warning or Info.

Warnings and info are there so you launch knowing; you can still go ahead. A Blocking one — for example an audience that resolves to no groups, or a timeline whose messages are all in the past — means the launch can't work, so the confirm's button is disabled until you fix it. If you're a member sending from the shared number, the button reads Request to send: nothing goes out until an admin approves it.

Admins can also suppress groups so no event reaches them, without changing their categories — useful for a group that asked to be left out of event promotion. Note the scope: the suppression list is org-wide and admin-only, so a suppressed group is skipped by every event launch, not just this one. There is no per-event suppression.

After launch#

  • Queued messages appear in the calendar alongside everything else you have coming up.
  • Each message respects the same gates as any other send — caps, cooldown, quiet hours. A message whose groups are all blocked is skipped, and the reason is recorded.
  • Each message is its own source. So the cooldown (20 hours, for a timeline message) stops a single message repeating into a group — it does not stop your announcement and your reminder from both landing there. Spacing the ladder is what does that, and the daily cap is the real ceiling on same-day volume.

You can clone an event for next term, or transfer ownership to whoever's running it this year — the timeline comes along.

Members creating events#

Members create their own draft events with the same wizard admins use — templates included. A draft sends nothing, and editing it before launch needs no approval. What happens at launch depends on the number it sends from:

  • The shared number: the member clicks Request to send instead of launching. That lands in the approval queue for an admin to review — copy, timeline, and audience all visible before anything is queued. The launch button reads "Pending approval" (and the event row shows a Pending approval pill) and disables itself once submitted, so nobody fires three duplicate requests while waiting.
  • The member's own connected number: launching sends directly, like any other send from their own number.

A member can only pick the shared number or their own — never a teammate's — and only what the number mode allows: no shared number in Personal numbers mode, no personal number in Shared number mode. Viewers can't create events.

A worked example#

Event promotion playbook walks a real two-week timeline end to end, including what to put in each message.