Prospects are texted about scheduled events, and every event gets an outcome

Improvement

Week of October 19, 2026

Until now a prospect only heard about a planned event from the reminders, and an event booked less than an hour out produced no text at all.

Texts when an event is scheduled, moved or cancelled

Scheduled. The prospect gets one text with the date and time, the place, any details, and how to reply to their advocate. If the event type has a waiver the conversation hasn’t signed, the signing link is in the same text instead of a separate one.
Moved. Changing the time or the place texts the prospect the new time and place. Editing only the details texts nobody.
Cancelled. The prospect is told the event is off.
When an admin makes the change, the advocate gets the same notice. Advocates aren’t texted about their own changes.
Nothing is sent for an event that has already started, so tidying up or backdating a past event texts nobody.

These texts follow the same rules as reminders: the prospect must have a verified phone number, not have opted out of texts, and not be blocked from the conversation. Reminders now also say who the event is with, and the day-before reminder includes the date.

A reliable outcome for every event

Always asked. The advocate gets the “did it happen?” text after every event, not only for event types with a reward.
Three answers. “Yes, it happened”, “No, the prospect didn’t show”, or “No, we called it off”. No-shows are recorded separately from events that were called off.
Admins can record and correct it. Once an event has started, its card on the conversation timeline in the admin portal offers Happened, No-show and Called off. If an outcome is already recorded, Change lets you correct it. Changing an outcome to Happened creates the reward claim if the event type has a reward; changing it away from Happened leaves any existing claim in your inbox to decline.

Fixes

Scheduled texts (reminders and follow-ups) that the messaging provider rejected were recorded as delivered. They are now recorded as failed.
The event card on the timeline shows the event’s details.
Advocates can no longer schedule an event in the past. Admins still can, to log one that already happened.
When the advocate has no time zone on file, the event form uses the time zone of the browser filling it in rather than UTC.
An event can’t be edited once its outcome is recorded.
The conversation’s ⋯ menu keeps the edit link after an event has started, until an outcome is recorded (for up to 30 days), and shows the date: “Edit Test Ride (Oct 10)”.

Part of Community Events — contact support to enable it for your community.