Problem

Notification senders may expect to see late confirmation responses recorded as a distinct “Confirmed Late” status after a notification’s broadcast duration ends. Contacts may state that they responded after the notification closed, but operators no longer see these late responses on the notification dashboard, details, or reports.

Root Cause

Confirmation timing in Everbridge Suite is determined by the notification’s broadcast duration. Historically, the platform accepted confirmation responses that arrived after the notification ended and moved them into a separate “Confirmed Late” status. That “Confirmed Late” status was available only for SMS and Mobile App (Mobile Push Alert) delivery paths, and confirmations could be made for up to ten days after the last notification attempt. For SMS and Mobile App deliveries, late confirmations could be recorded as “Confirmed Late” for up to ten days, while email and voice notification responses after the broadcast duration were not accepted and showed a “response time frame ended” error.

Solution

The time window during which confirmations are accepted is now fully controlled by the broadcast duration configured when the notification is created. Notification duration determines when the notification becomes inactive. Any confirmation attempts made after the broadcast duration has expired will not be accepted and will remain in a Not Confirmed status.

Because the separate “Confirmed Late” result was removed, late replies are no longer recorded as a distinct status, and late confirmations are no longer accepted after a broadcast or notification has ended. To have confirmations counted, set the broadcast duration to cover the full period during which recipients are expected to reply. For detailed guidance on configuring this setting, see EBS: Setting a Broadcast Duration for a Notification in Everbridge Suite.