Broadcast Message Type Notification Codes
Zenoti assigns specific notification type codes to ezConnect broadcast messages. Understanding these codes helps you interpret analytics data accurately — the reports and analytics dashboard and the ezConnect report scheduler exclude broadcast notification types from sent-messages counts so that bulk broadcast traffic does not inflate two-way conversation metrics.
Note: For conceptual background on ezConnect broadcasts, see Broadcast and bulk messaging.
Before you begin
Your organization must have ezConnect enabled.
You need the following permission to view guest profiles referenced in broadcast conversations:
Permission: View Guest Profile — Required to see guest profile details associated with broadcast conversations. Admin path: Configuration > Security > Security Roles > [your role] > Guests > View Guest Profile
Steps
Understand broadcast notification type codes
Zenoti assigns a notification type code to each broadcast type. The following table lists each broadcast type, its notification type code, and whether it uses a dedicated code or the legacy shared code.
| Broadcast type | Notification type code | Notes |
|---|---|---|
| Unconfirmed Appointments | 770 | Dedicated code assigned to this broadcast type |
| Center Hours Change | 771 | Dedicated code assigned to this broadcast type |
| Provider Unavailability | 772 | Dedicated code assigned to this broadcast type |
| Confirmed Appointments | 105 | Retains the legacy code shared with All Appointments |
| All Appointments | 105 | Retains the legacy code shared with Confirmed Appointments |
Note: Broadcast messaging is SMS-only. WhatsApp broadcast is not supported for any broadcast type.
Understand how broadcast codes affect analytics
The reports and analytics dashboard and the ezConnect report scheduler exclude notification types 105, 770, 771, and 772 from the sent-messages count. This exclusion prevents bulk broadcast traffic from inflating two-way conversation metrics, so the counts you see in reports reflect only direct agent-to-guest messaging activity.
The following table summarizes which notification type codes are excluded from each area.
| Area | Excluded notification type codes |
|---|---|
| Reports analytics dashboard — sent-messages count | 105, 770, 771, 772 |
| ezConnect report scheduler — sent-messages count | 105, 770, 771, 772 |
| Pinned-chats conversation view | 770, 771, 772 (105 was already excluded) |
Understand how broadcast codes affect the pinned-chats view
The pinned-chats conversation view excludes notification types 770, 771, and 772 in addition to the existing exclusion of type 105. This means broadcast messages sent for any of the five broadcast types do not appear as events in the pinned conversation timeline, keeping the pinned view focused on direct two-way conversations between agents and guests.