Use the notification center

What notifications represent

The notification center can contain high-signal CRM events, shared-inbox activity, personal-email alerts, assignments, operational events, and governance events enabled for your account. A notification is personal attention history. It is separate from conversation unread state and does not replace the source record's owner, status, SLA, or next action.

Process the feed

1. Open the bell in the header or go to Notifications.
2. Use Unread when starting an attention pass; use All to reconstruct recent context.
3. Open a notification through its linked title or action.
4. Verify the workspace, customer or record, and current state. Another teammate or automation may have changed it since the notification was created.
5. Complete, reassign, or schedule the underlying work.
6. Return to Notifications and choose Mark as read when you have reviewed it.
7. Choose Clear only when it no longer belongs in the active feed. Cleared notifications remain recoverable in Cleared.

The center refreshes as relevant activity changes and includes a Load more control for older pages.

Understand feed actions

Configure high-signal preferences

Open Settings → Notifications. Preferences include:

• persisted in-app feed and categories for assignments, work, customer, operations, and governance;
• shared-inbox alerts;
• personal-email alerts;
• desktop alerts, subject to browser permission; and
• notification sound and volume.

Turning the feed off does not clear existing history. Inbox unread state remains in each inbox even when a notification category is disabled.

Choose alerts by required response, not by curiosity. An operator may prioritize assignment and shared-inbox alerts; an administrator may add operations and governance. Too many enabled categories can bury the one signal that requires action.

Configure desktop alerts

1. Enable the relevant feed and category first.
2. Turn on desktop alerts in WRKZY.
3. Allow notification permission in the browser prompt.
4. Trigger a safe test event and verify the alert opens the intended workspace record.
5. If the setting says the browser blocked alerts, change the site's permission in browser settings, then test again.

Sound is optional. Set it to a level suitable for the operator's environment; never depend on sound as the only escalation path.

Triage examples

• Conversation assigned to you: open the conversation, verify identity and urgency, then accept or reassign ownership.
• Customer activity: open the linked customer or work record and decide whether it changes the next action.
• Personal email alert: review it in Private Mail; share only necessary context if the team must act.
• Operational warning: inspect the channel, delivery, import, campaign, or automation evidence before retrying.
• Governance event: an Owner/Admin should verify the actor and expected change in the relevant access or audit view.

When notifications look wrong

• Missing alert: check category, shared/personal inbox preference, and browser permission; then verify the source event actually occurred.
• Repeated alert: open the record and determine whether it reflects repeated source events before clearing.
• Link opens unavailable content: confirm workspace access and whether the record was archived or your role changed.
• Count differs from the feed: refresh and review All, Unread, and Cleared; updates may have occurred in another tab.
• Clear or read update fails: retry once after refresh. The source work is unaffected, so continue there and preserve the error if it persists.

Measurable notification health

Useful notifications reduce assignment-to-action time and missed high-signal events. Measure response to actionable alerts and the age of unread items, not the total number generated or cleared.