Message people who haven't done something yet

Email, push or text the guests who haven't booked a flight, finished a to-do, answered a question or chosen a session, with their own details merged in.

Do first
Find the event and the people in it

Attend can send one message to exactly the guests who still need to act, and it works out who they are when it sends. The message goes to the guests themselves, so always preview, show the organizer, and wait for a yes.

Who: a recipient rule

A recipientRule has a base, the people to start from (confirmed guests by default), and up to 5 conditions. Every condition must match.

Bases (base.kind):

  • attendees (confirmed guests);
  • guest_ids;
  • agenda_rsvp (agendaItemId, statuses from confirmed, pending, invited);
  • agenda_group_rsvp;
  • list_membership.

Conditions (conditions[].kind):

ConditionMatches guests who…Example
travel_missinghave no flight, hotel or transfer{kind:"travel_missing", travel:"flight", direction:"arriving"}
todo_incompletehaven’t finished a to-do{kind:"todo_incomplete", todoId}
field_missinghaven’t answered a custom question, or shared dietary or accessibility needs{kind:"field_missing", field:{attendeeFieldKey:"tshirt_size"}}, {kind:"field_missing", field:{system:"dietary"}}
agenda_unansweredhaven’t made a session choice{kind:"agenda_unanswered", agendaGroupIds:[…]}

For agenda_unanswered, a request waiting for approval, or declining every option, counts as answered. Get the ids from todos__getFormsBundle (to-dos), attendee_fields__listSetup (field keys) and agenda_items__getScheduleBundle (groups and sessions).

What: subject, body and merge fields

subject, body and pushTitle accept these merge fields: {{firstName}}, {{lastName}}, {{eventName}}, {{actionLink}}, {{missingItems}}, {{todoTitle}}. {{actionLink}} opens the guest app on the screen that matches the first condition: the to-do, or Travel’s add flight, hotel or transfer sheet. It never signs anyone in.

Use bodyFormat: "rich" for a branded email built from simple tags (<p> <br> <strong> <em> <a> <ul> <ol> <li> <h2>). Without it, the body is sent as your own HTML.

Steps

  1. See who matches. Call comms__previewRecipients with the rule and a limit. It’s read-only. Tell the organizer the count and a few names.
  2. Check reach. For push or SMS, call comms_edge__eventCommsReport: how many guests have push turned on or have agreed to texts.
  3. Dry-run the send. Call comms_edge__eventBulkSendComm with dryRun: true, plus channels (email, push, sms), category (organizer, event-update or reminder) and urgency. Pass previewGuestId to render it for one real guest. It returns counts per channel, a sample, the rendered message and the plan rows.
  4. Show the organizer the rendered message and the counts. Send only after they say yes, with the same input and dryRun: false.
  5. Follow a queued send. A rule-based send of up to 10,000 guests is queued and returns a sendId. Check progress with comms__getCommsSends (id is the sendId). A send to an explicit guestIds list (up to 1,000) goes in the same request. Recent sends are also in comms__getCommsBundle.

Rules

  • urgency: "urgent" breaks through guests’ quiet settings. Use it only when the organizer asks for it.
  • Don’t send the same message twice to retry. Check the send’s status first.
  • To send this automatically on a schedule instead, see Reminders.

Updated 2026-11-02 · View as Markdown