Brella sends push notifications to the mobile app and to the web app through the browser. This list gives every notification, its exact text, what triggers it and what opens when the attendee taps it.
Before you start
Attendees receive push notifications only on devices where they are signed in and have turned notifications on (see How attendees turn notifications on).
Attendees of a white-label app receive notifications only through that app.
Invited registrants without an account can't receive push notifications. For meeting reminders they receive an email instead.
How attendees turn notifications on
The first time an attendee opens the event Home screen without notification permission, a sheet titled Get alerted when ... appears with Enable notifications and Not now. After Not now, the app can ask again later. The Notify me when they join button on an invited attendee's profile opens the same sheet when notifications are off.
Attendees manage notifications in Account > Notifications:
Mobile app: Menu > Settings > Notifications
Web app: Account > Notifications
Deep link:
/events/<event slug>/account/notifications
Without permission, the screen shows Enable Push Notifications with an Enable button. On the mobile app, if the attendee denied permission, Enable opens the phone's settings. With permission, the screen shows the Subscribe to notifications switch and, on the mobile app only, Adjust preferences, which opens the phone's notification settings. Show status shows technical details for support.
On the web app, the browser asks for permission. The browser shows the notifications also when the web app tab is closed. Clicking a notification opens the web app on the screen named under Web click opens in the tables.
Notifications
Titles and texts are in English on every device. <Full name> is the other attendee's name. Dates and times use the attendee's own date and time format; for virtual attendees with a time zone, their time zone.
Announcements
Trigger | Title | Text | Tap opens | Web click opens |
You send an announcement in Communications > Announcements (to all registrants or to the chosen registrant lists) | The event name |
| The event home screen, with an alert showing the heading and the content. If the announcement has a link, the alert has Visit link and Dismiss. | The event home screen |
Earlier Android notification example; appearance varies by device.
Meetings
Trigger | Title | Text | Tap opens | Web click opens |
An attendee sends a meeting request |
| The request message | The meeting chat | The meeting chat |
The other attendee accepts |
|
| The meeting chat | The meeting chat |
The other attendee declines |
| The message | The meeting chat | The meeting chat |
The other attendee cancels |
| The message | The meeting chat | The meeting chat |
The other attendee reschedules |
| The message | The meeting chat | The meeting chat |
An attendee sends a chat request |
| The message | The meeting chat | The meeting chat |
5 minutes before an accepted meeting starts |
|
| The meeting chat | The meeting chat |
<Table> is the meeting point, for example "Table 3". On a reserved point with a custom label it is "VIP, Table 3", or "VIP" when you hide the table number.
Meetings you create in the admin panel use these titles instead: An admin arranged a meeting for you with <Full name>, An admin scheduled a meeting for you with <Full name> and An admin cancelled your meeting with <Full name>.
Group meetings: Group meeting request from <Full name>, <Full name> accepted your group meeting request, <Full name> declined your group meeting request, <Full name> cancelled your group meeting, <Full name> rescheduled your group meeting, and 5 minutes before the start You have a group meeting in 5 minutes. Admin-created group meetings: An admin arranged a group meeting for you, Group meeting scheduled, Your group meeting has been cancelled.
No meeting or chat notification is sent between two attendees who blocked each other, or for a chat the attendee has hidden.
Chat messages
Trigger | Title | Text | Tap opens | Web click opens |
The other attendee sends a message in a meeting chat |
| The message | The meeting chat | The meeting chat |
Attendees don't receive this notification while they have that chat open. While a chat request is still pending, messages from the attendee who sent the request don't trigger it; the chat request notification covers them. An attendee who declined the meeting doesn't receive it.
Sessions
Trigger | Title | Text | Tap opens | Web click opens |
5 minutes before a bookmarked session starts | The session title |
| The session | The web app |
Networking time slots don't send this notification.
Session RSVP status
These notifications go to attendees whose seat request or waitlist place changes. They apply to sessions that use Require RSVP approval or Waitlist mode. <Session> is the session title.
Trigger | Title | Text | Tap opens | Web click opens |
You approve a pending seat request, or you turn off Require RSVP approval and the request gets a seat |
|
| The session | Schedule |
You reject a pending request or a waitlist place, or Brella turns it away: the mode is turned off with no seat left, or a seat opens while the attendee has an overlapping confirmed session or meeting |
|
| The session | Schedule |
A waitlisted attendee gets a seat: a seat opens, you confirm them, or you turn off Waitlist mode while seats are free |
|
| The session | Schedule |
People
Trigger | Title | Text | Tap opens | Web click opens |
An invited registrant joins the event after the attendee selected Notify me when they join on their profile | The event name |
| The attendee's profile | The attendee's profile |
Reminders you schedule
Trigger | Title | Text | Tap opens | Web click opens |
Communications > Reminders > Event reminder email runs; sent to joined attendees who receive emails |
|
| The event home screen | The web app |
Communications > Reminders > Pending notifications reminder emails runs; sent to attendees with pending meeting requests | No title |
| The event home screen | The web app |
Both reminders also send an email. Neither is sent after the event has ended.
Networking access
Trigger | Title | Text | Tap opens | Web click opens |
A registrant list change turns networking on for an attendee during the event | The event name |
| The app, no specific screen | People |
A registrant list change turns networking off for an attendee during the event | The event name |
| The app, no specific screen | People |
Registrant list changes that send these: changing a list's networking setting, adding or removing attendees from a custom list, moving attendees to another ticket type list, deleting a list, or changing the event's networking settings. The notifications are sent only while the event is ongoing.
Turning networking off through a registrant list doesn't cancel the attendee's pending meetings. They stay pending.
Pitch reels
Trigger | Title | Text | Tap opens | Web click opens |
You publish an attendee's uploaded, pending or hidden pitch reel video | The event name |
| The app, no specific screen | The event home screen |
You hide or delete a pending or published video | The event name |
| The app, no specific screen | The attendee's own profile |
What is not a push notification
Replies in Spaces update the app in real time but send no push notification.
Breakout room and session chat updates send no push notification.
Where attendees see past notifications
The Activity block on the event Home screen shows an unread count and opens Activity history. It lists announcements, meeting updates, "just joined" notifications, session RSVP status updates and pitch reel decisions. Tapping an item opens the announcement, the meeting chat, the profile or the session; pitch reel items open nothing. An RSVP status update is listed only when the push notification was delivered. Session reminders, meeting reminders, chat messages, scheduled reminders and networking access notifications are not listed. An empty list shows No activity yet.


