Skip to main content
The Flags page is one list of everything needing attention — unreplied conversations, completed requests that need follow-up, health score drops, and the risks and opportunities your flag rules and playbooks raise. Find it in the sidebar, with a badge showing how many are active.
The Flags page: open risks, opportunities and unreplied threads, each with its type, status, assignee and account
This screen was called Alerts, and alerts and flags were two separate lists with two sets of row actions. They are one now, so a thread nobody answered and an account whose usage is falling sit side by side and are worked the same way. Old links to /app/alerts still land here.

Flag types

The first four are raised by Zudo itself and are re-checked on a schedule. The last two describe a condition that a rule is continuously evaluating.

Statuses

Marking something addressed does not close it. Whether an unanswered thread is still unanswered, or an account is still at risk, is decided by the job or rule that raised it — not by anyone clearing it off a list. Dismissing an unreplied thread also tells response time that the message needed no reply, so the wait isn’t counted against your team. A message the customer sends after that is timed as usual.

The table

Each row shows a summary, type, status, who it is assigned to, the linked account, the related thread or request, and when it opened. A flag rule assigns to the account’s CSM by default, so Assigned to → Unassigned is the useful view after a change: those are the flags on accounts that have no CSM either. A Gmail icon opens the thread directly in Gmail when applicable.

Filters

Actions

Use the three-dot menu on each row to:
  • Snooze — hides it for 4 hours. Available on the flags Zudo raises itself, because something re-checks those on a schedule. A risk or opportunity cannot be snoozed: nothing would bring it back, and hiding a condition that is still true would say it had paused.
  • Mark addressed / Reopen — says someone has dealt with this.
There is no Delete. The history is the record of what your team saw and acted on, and an addressed row drops out of the working list anyway.

Email notifications

When a flag is raised, Zudo emails the resolved recipient using this fallback chain:
  1. The account’s assigned CSM (see CSM assignment).
  2. The CSM of its parent account, if the account has no CSM of its own.
  3. The org’s fallback CSM if neither is set.
There is no fourth step. If none of those resolve to a person, the flag is still raised — you will see it on the Flags screen — but it is left unassigned and no email goes out.
Set a fallback CSM under Settings → Organization → Team so nothing is raised with nobody to act on it. Every account having a CSM works too; the fallback is the cheaper guarantee.
The email goes out once, when the flag first opens. While it stays open it is refreshed quietly rather than re-sent. If the condition clears and later comes back, that is a new flag and a new email. The navigation sidebar shows the count of everything active in the list, and refreshes every 60 seconds.

Configuring unreplied thresholds

The number of business hours before an unreplied thread raises a flag is set per organization, by an admin, under Settings → Organization → Email. Only time inside your business hours counts toward it. It applies to every account in the organization, including accounts added by hand or imported from a CSV.