Notification Center
Gordon CRM includes a Notification Center that surfaces important system events directly in the dashboard. Instead of relying on email or external monitoring, you can see what's happening — and what needs your attention — right from the top bar.
The Bell Icon
A bell icon appears in the top-right corner of the dashboard (on both desktop and mobile). When you have unread notifications, a red badge shows the count.
Click the bell to open the notification panel. From there you can:
- Click any notification to mark it as read and expand its full details.
- Mark all as read using the button at the top of the panel.
Per-User Read Tracking
Each team member has their own unread count. When you read a notification, it only clears for you — other members of the workspace still see it as unread until they read it themselves.
Action Links
Some notifications include action links — small clickable chips below the notification body (e.g., "View Broadcast ↗", "View Contact ↗"). These navigate directly to the relevant page so you can take action without searching for it.
Notification Types
Automation Depth Limit
| When it fires | The automation engine stops a chain after exceeding 3 recursive steps. |
| What it means | You likely have a circular automation chain — two or more rules that trigger each other in a loop. |
| Action links | View Automations |
The notification includes enriched details that identify the specific trigger and blocked rule:
Automation chain depth limit reached The automation engine stopped after 4 chain steps to prevent an infinite loop. Trigger: tag applied "Pong". Blocked automation: "When tag Pong added → Add tag Ping".
Grouping: If multiple contacts hit the same chain, they are grouped into a single notification with a count (e.g., "×50") rather than creating 50 separate alerts. When the count increments, the notification reappears as unread for all users.
What to do: Open the Automations page and look for tag-based rules that form a cycle. Remove or deactivate one side of the cycle. See Loop Protection → Depth Limiter for detailed remediation steps.
Broadcast Sent
| When it fires | A broadcast finishes sending successfully. |
| What it means | Your broadcast was dispatched. The notification includes the recipient count and the number of suppressed contacts. |
| Action links | View Broadcast |
This is an informational notification — no action is required. It confirms that the broadcast sweeper completed processing.
Broadcast Failed
| When it fires | A fatal error occurs during broadcast processing. |
| What it means | The broadcast could not be sent. The notification includes the error message. |
| Action links | View Broadcast, Sender Settings |
What to do: Check the error message in the notification body. Common causes include missing or unverified sender identities. The "Sender Settings" link takes you directly to your domain configuration. See Sender Identities for troubleshooting.
Email Bounce
| When it fires | An email bounces (the address is invalid or unreachable). |
| What it means | The contact has been automatically suppressed and will not receive future emails until the suppression is cleared. |
| Action links | View Contact |
Grouping: Each bounced contact creates its own notification. If the same contact bounces multiple times, the events are grouped into a single notification with an incrementing count.
What to do: Review the contact's email address for typos. Bounce suppressions can be cleared from the contact detail page if the address has been corrected.
Email Complaint
| When it fires | A recipient marks your email as spam. |
| What it means | The contact has been permanently suppressed. Complaint suppressions cannot be cleared — this protects your sender reputation. |
| Action links | View Contact |
Grouping: Each complained contact creates its own notification. If the same contact generates multiple complaints, the events are grouped into a single notification with an incrementing count.
What to do: Review your email content and sending practices. Frequent complaints can damage your sender reputation and affect deliverability for all emails from your workspace.
Retention
Gordon CRM keeps the most recent 50 notifications per workspace. When a new notification is created and the limit is exceeded, the oldest notifications are automatically removed.
Related Documentation
- Loop Protection — How the automation depth limiter works and how to resolve circular chains.
- Broadcasts — The broadcast lifecycle, audience targeting, and sending process.
- Subscriptions & Consent — Suppression types, clearing suppressions, and email eligibility logic.