Purpose: Use this article to review and troubleshoot Event-related messaging from the Communications tab.
The Communications tab provides a centralized history of messages associated with an Event, including automated communications generated by triggers and communications sent manually from the Event.
Administrators commonly use this tab to confirm delivery activity, validate trigger behavior, and troubleshoot missing or failed communications.
For overall Event navigation and lifecycle guidance, see Understanding the Event Screen.
In this article
Communications tab
The Communications tab provides a centralized view of all messages associated with the Event. This includes communications generated automatically by triggers and communications sent manually from the Event.
Each entry represents a communication event and includes delivery and processing details to help administrators understand what was sent, to whom, and what happened next.
What you can review
- emails and SMS messages sent to learners, contacts, instructors, or staff
- communications triggered by registrations, schedule changes, or booking activity
- the template used for each communication
- the recipient of the communication
- the date and time the communication was sent or scheduled
- the trigger that generated the communication where applicable
- delivery and processing status such as Sent, Opened, Bounced, or Failed
Reviewing communications helps confirm that learners and stakeholders received important Event information such as confirmations, reminders, joining instructions, and schedule updates.
Understanding communication records
Each row in the Communications tab represents a single communication instance.
Depending on configuration, this may include:
- automated messages sent by communication triggers
- manual communications sent from the Event
- messages tied to booking workflow transitions
The status of each communication reflects its delivery outcome and processing state. This is especially useful when diagnosing issues with missing or delayed messages.
When to use the Communications tab
Administrators typically review this tab:
- after enrolling learners to confirm confirmation emails were sent
- when validating that reminders or joining instructions were delivered
- when investigating whether a trigger fired correctly
- when troubleshooting delivery failures or missing communications
- when confirming which template or trigger generated a message
Note
Repeatable or automated messaging is configured using communication triggers and templates. The Communications tab provides visibility into communications that have already been generated or sent.
How this relates to Triggers
The Communications tab reflects the output of your communication setup:
- Templates define the message content
- Triggers define when communications are sent
- The Communications tab shows the resulting delivery history and processing status
If a communication appears missing or incorrect, review the associated trigger, template, and Event conditions to identify the cause.
Troubleshooting communications
When investigating communication issues, use this tab to:
- confirm whether a communication was generated
- check the delivery status such as bounced or rejected
- verify the intended recipient and template
- identify whether trigger conditions were met
If a communication does not appear, it may indicate that the trigger conditions were not met or that the trigger was not configured or enabled at the time.
Best practices
- Use the Communications tab to verify learner messaging and delivery outcomes.
- Review communication history if learners report missing or incorrect notifications.
- Confirm trigger behavior after major Event scheduling or enrollment changes.
- Review bounced or failed communications promptly to avoid delivery gaps.