Escalate: handing critical signals to a regional manager

What it is

The Escalate button is a fast hand-off tool for the critical-severity network signals sitting on your Feed. Rather than asking you to re-type each critical signal into a separate email, it drafts the whole batch for you: every critical signal's title, its affected-to-total location count, and its body text, pre-loaded into one email your own mail client sends. Two clicks (open the composer, hit Compose escalation email) gets a full, readable brief in front of a regional manager, a peer on your leadership team, or anyone else who owns that part of the network.

It is a hand-off, not a delegation tool with tracking. Verinode does not follow the email after it leaves your outbox, and it does not (yet) know which regional manager owns which cluster of locations, so you choose the recipient every time you use it.

Where to find it

Open Feed from the HQ sidebar, at hq.verinode.ai/feed. The button only appears when your network currently has one or more open critical-severity signals. There is no separate page or settings toggle for it: it is a floating affordance layered on top of the Feed itself.

• It sits fixed to the top of the page, right-aligned, so it stays visible no matter how far you scroll through the stream.
• If you have the AI agent side panel open, the button shifts left to make room for it. It never sits underneath the panel or gets clipped by it.
• It reads Escalate N critical, where N is the exact count of critical signals currently open on your network. That count updates as signals get resolved or new ones surface; if your network drops to zero open critical signals, the button disappears entirely until the next one fires.

When it does not appear

If your network has no critical-severity signals open right now, the button simply is not rendered. There is no placeholder, no grayed-out state, and no message explaining its absence: an empty top-right corner on the Feed means your network currently has nothing at critical severity, not that something is broken. The moment a network signal writes at critical severity (see Network signal cards for how a signal is detected and scored), the button appears on your next page load.

Opening the composer

Clicking Escalate N critical opens a modal titled Escalate critical signals. It has three parts: a short explanation, an editable email frame, and the list of signals that will ride along.

The modal opens with this note: Verinode does not yet store a regional-manager assignment per network, so you type in the recipient who owns this cluster of locations. Everything below it is editable before you send.

Recipient email

A plain email field, placeholder text regional.manager@example.com. This is required: the Compose escalation email button at the bottom stays disabled until you have typed something into this field. Verinode does not validate that the address is real or that it belongs to anyone in particular, it is a free-form field, because there is no stored directory of regional managers to pick from yet.

Intro

An editable text block, pre-filled with a default message:

Flagging the following critical network signals for your attention this week. Please loop in the affected franchisees as appropriate and report back end-of-week.

You can rewrite this entirely, shorten it, add urgency, or point to a specific meeting, before you send. Whatever is in this box at the moment you click Compose becomes the opening paragraph of the email.

The signal list

Below the intro sits a heading reading N critical signal(s) to include, followed by a scrollable list (it caps its height and scrolls once there are more than a handful of rows) with one row per critical signal. Each row shows:

• The signal's title, in bold.
• Underneath it, when the underlying signal carries both counts, an "X of Y locations" line, the same affected-to-total framing used on the signal card itself in the Feed (see Network signal cards for how that ratio is built). If a signal does not carry both an affected count and a total count, this line is simply left off that row: no placeholder, no zero.

The list follows the same order the signals already have in your Feed: critical signals are pinned above everything else there, and within the critical group they are ordered by your network's focus-area weighting and then recency, so the signal at the top of this list is the one that would also be at the top of your stream.

Sending it

Two buttons sit at the bottom of the modal:

• Cancel closes the modal without sending anything and without saving any edits you made to the recipient or intro fields.
• Compose escalation email builds the email and hands it to your device's default mail application through a standard mailto: link, then closes the modal immediately. Verinode does not send this email itself, host a copy of it, or confirm delivery. Your mail client takes over from that point exactly as it would for any other message you compose by hand.

The button is grayed out and unclickable until the Recipient email field has something in it.

What the drafted email looks like

The subject line is built automatically: it starts with the word "Escalation," followed by the count and word "critical signal" (pluralized correctly for more than one), and closes with your network's name in parentheses. For example, three critical signals at a network called Acme Restoration Group would produce a subject reading "Escalation, 3 critical signals (Acme Restoration Group)."

The body is built in three parts, in order:

1. Whatever is currently in the Intro field.
2. One bullet per critical signal in the list, in the same order shown in the modal. Each bullet is the signal's title, followed by its "X of Y locations" count in parentheses when both numbers are available, followed on the next line by the signal's own body text if it has one.
3. A closing signature line naming your network followed by "HQ."

Nothing here requires you to retype a single signal by hand. If a bullet reads oddly or you want to trim the list before sending, the fastest fix is to cancel, adjust your Feed's time window or filters so a different set of signals is showing as critical, and reopen the composer, since the modal always reflects whatever is critical and open at the moment you click the button.

Why this exists

A restoration franchise HQ team is often thin at the top: one or two people watching the whole network, and the people who actually need to chase down a critical pattern, a regional manager, an ops lead, a compliance officer, sit one level below. The Escalate button exists to close that gap without a project-management tool in between. It turns "I need to tell Regional a few things are on fire" into a single, complete email instead of five separate copy-paste jobs out of the Feed.

It deliberately stays this simple. There is no calendar integration, no ticket creation, and no read-receipt tracking on the email once it is sent, this is a hand-off through the universal mailto link, not a workflow system. If your network eventually wants tracked, assigned escalations with follow-up state, that is a different tool than this button: this one is built to get the list in front of the right person in two clicks and get out of the way.

The privacy boundary, in practice

Everything that rides into the escalation email is exactly what was already on the signal card: a title, an affected-to-total location count, and the plain-language body Verinode wrote for that pattern. No franchisee name, job number, or client detail is ever part of a critical signal in the first place (see Network signal cards for why that boundary is structural rather than a display choice), so there is nothing to leak by including it in this email. You are handing a regional manager the same network-level read you have, at the same level of aggregation, just addressed to someone else.

Related articles

• The HQ feed: how the Feed is built, ordered, and filtered.
• Network signal cards: how a critical signal is detected, scored, and what its "X of Y" count means.
• Consent responses on the feed: the other feed card type built around a franchisee's own action.
• HQ overview: how the Feed and Escalate fit into HQ's navigation.
• HQ compliance: a common source of critical-severity signals.
• Broadcasting to your network: the other outbound-communication tool in HQ, for reaching your whole network rather than one recipient.