actionUrl target such as the related agent, campaign, call, or billing record.
Manage notifications
- Open a notification to review its related item.
- Select Mark as read for completed items; dismissed state shows a confirmation toast.
- Dismiss messages that no longer need attention.
- Use Mark all as read after reviewing the list. Empty states show No notifications / You’re all caught up for each tab.
Reminder types you will see
Notifications are workspace reminders. Each carries a status (Pending, Active, Dismissed, Completed) and a priority where lower numbers mean more urgent (expiry alerts use 10–30).Decide what needs action
Open the related agent, call, campaign, billing item, or workspace setting before making a change. Check the event time, workspace, and current status because the underlying condition may already be resolved. For recurring alerts, look for a shared cause such as unavailable calling service, invalid contact data, insufficient credits, or a recent configuration change. Record the resolution so other team members can recognize the same event.Work as a team
Assign important notifications to the person who owns the related agent or campaign. Keep the item unread until ownership is clear, then document the outcome in your team’s normal tracking process. Dismiss informational items only after confirming that no follow-up is required. Use Mark all as read carefully because it affects every visible notification. A workable rota: one person triages the bell each morning, assigns campaign warnings to campaign owners and billing events to the workspace manager, and leaves processing results for the agent builder to verify. Unowned notifications older than a day get reassigned in the team standup - silent alerts are how credit exhaustion and failed campaigns go unnoticed.Account activity
Use account activity when you need a broader history of workspace actions. Availability depends on your role and plan. If an expected notification does not appear, confirm that you are viewing the correct workspace and that your role includes access to the related feature. Also check whether the event appears in the feature’s own history or logs. Notifications are scoped to the active account and workspace. Another team member may see a different set based on role, access, and the actions they performed.Troubleshoot an alert
Find the first checks for common problems.
