Verinode
Open Verinode

Network broadcasts: sending messages and tracking reads

Network broadcasts are the one-way messaging tool HQ uses to push a short text update to every active membership in the network at once. You write a subject and a body, send it, and it lands in eac…

7 min read·Updated August 25, 2026
On this page

What it is

Network broadcasts are the one-way messaging tool HQ uses to push a short text update to every active membership in the network at once. You write a subject and a body, send it, and it lands in each operator's IQ feed and their next briefing. From that point on, Verinode tracks how many operators have read it and shows you that count, plus a trailing read trend, without ever telling you which specific franchisee did or did not open it.

Broadcasts are for network-wide announcements, not for a conversation. There is no reply channel back to HQ built into a broadcast, and there is no way to target a subset of locations. If you need a two-way exchange or a request that requires a response, use Surveys, Polls, or Consent requests instead (all reachable from the same tab strip described below).

Where to find it

Broadcast lives in the HQ sidebar as its own item, near the top of the nav alongside Feed, Decisions, Actions, and Playbooks. Selecting it opens hq.verinode.ai/broadcast, which loads to the Announcements tab by default. A rounded pill tab strip at the top of the page switches between the related outbound-communication surfaces: Announcements (broadcasts, this article), Initiatives, Surveys, Polls, and Consent.

If you land on an older Reports & Communication page instead, you're looking at a broadcasts list, but it is the earlier, being-retired home for this feature: it can still show you subjects, read counts, and full bodies, but it does not include the read-trend detail view described below. Broadcast (the sidebar item) is where new work is going and where every capability in this article lives.

Composing and sending a broadcast

Only HQ team members with the Admin role see the Send broadcast button and can use it. Everyone else on the Announcements tab can still see the hero numbers, the list of past broadcasts, and read counts, they just don't get the compose affordance.

  1. 1From the Announcements tab, select Send broadcast in the page header. A dialog titled "Send broadcast" opens.
  2. 2Enter a Subject: a short line describing what the message is about (for example, "Quarterly rollup ready").
  3. 3Enter the Body: plain text only, no formatting or attachments. The dialog reminds you: "Plain text only. The broadcast lands in every active operator's IQ feed; read receipts roll back up to your Broadcasts tab."
  4. 4Select Send to network. The button is disabled until both fields have content.
  5. 5The dialog confirms the send and reports how many operators it went out to (for example, delivered to 12 operators), then closes on its own a moment later and the page refreshes with the new broadcast in the list.

There's no draft state, no scheduling, and no undo: a broadcast is written and fanned out to every active location in the network as soon as you select Send to network. If you leave Subject or Body empty, the button stays disabled; if a send fails for any other reason, the dialog surfaces the error text in place of a success message.

Note

Every other HQ admin on your team also gets a notification the moment a broadcast goes out, naming the subject and how many members it reached. That's so two admins don't accidentally send overlapping messages the same day.

What the page shows you

The top of the Announcements tab is a hero panel:

  • Eyebrow: "Text announcements"
  • Headline number: how many broadcasts you've sent in the last 30 days
  • Pill: either "N sent 30d" or, if nothing has gone out recently, "Nothing sent recently"
  • Sub-line: before you've ever sent one, it reads "Send a broadcast to push a text message into every active operator's IQ feed. Receipts post back as read counts." After you have a history, it reads "N total broadcasts authored, last sent [relative time]."

Below the sub-line are three secondary figures:

| Metric | What it means | |---|---| | Operator reads 30d | The sum of read receipts across all broadcasts sent in the last 30 days | | All-time broadcasts | Total broadcasts you've ever sent, with the last-sent date | | Avg reads / broadcast | Total reads in the last 30 days divided by the number of broadcasts sent in that window |

Under the hero is the Recent broadcasts row: up to 12 tiles, newest first. Each tile shows the read count as its label ("N read" / "N reads"), the subject as its headline, the first 80 characters of the body as a preview (cut off with an ellipsis if it runs longer), and "Sent [relative time]" as its footer. If the broadcast has read history going back at least a week, the footer also adds a short delta, like "+4 reads vs Jul 3," a quick read on whether it's still picking up reads.

If you've never sent a broadcast, the row simply reads: "No broadcasts authored yet. Use the Send broadcast button to push a text update into every active operator's IQ feed."

Read counts and the 90-day read trend

A broadcast's read count only moves in one direction, up. It's incremented once per operator the first time they dismiss the broadcast in their IQ feed, not just because they scrolled past it, so the number reflects operators who actually acknowledged the message rather than everyone it was technically delivered to.

Selecting any broadcast tile opens a read-only detail view with everything about that send:

  • A pill showing the total read count ("N read" / "N reads")
  • "Sent [relative time]" (Today, a day count, a week count, or a month count depending on how long ago) alongside the exact send date and time
  • If Verinode has collected at least two daily read-count snapshots for that broadcast, a trend line comparing the latest count to the count from roughly a month earlier, formatted as a signed delta with the comparison point, for example "+7 reads vs Jun 14 (9 reads)." A positive delta is shown in green; a negative one (which can happen if a read gets corrected) is shown in red. If there isn't enough history yet, this line is simply omitted rather than shown empty.
  • The full, untruncated message body under a "Message" heading
  • A footer note: "Per-franchisee receipt breakdown + resend / clone actions arrive with the broadcast lifecycle redesign. Today this view is read-only."

That last line is literal: today you can only look, not resend, duplicate, or edit a broadcast from this view. If you need to say it again, compose a new one.

The trend data behind that delta comes from a nightly network rollup that snapshots each broadcast's read count once a day and keeps a trailing 90 days of history. A brand-new broadcast won't have a trend line yet; it appears once a couple of snapshots have accumulated.

Tip

Keep broadcasts short and plain. They're meant to be read in a feed card, not as a memo, so one idea per message reads and lands better than a long update with several asks buried in it.

The privacy boundary

Broadcasts flow one way: HQ writes, the network reads. What HQ sees back is strictly an aggregate.

Heads up

HQ never sees which specific franchisee has or hasn't read a broadcast, only the running total across the whole network. There is no per-membership receipt list on this page today, by design, in the same way HQ never sees an individual location's private business data elsewhere on the platform. If you need to confirm one particular location saw an update, follow up with them directly, don't rely on the read count to prove it.

How broadcast bodies are protected

When you send a broadcast, Verinode encrypts the subject and body under your network's own dedicated encryption key before it's written to storage, the same key used to protect other sensitive network-level communications. You never see or manage that key directly; it's handled entirely behind the scenes. When the Announcements tab, the detail view, or an operator's IQ feed displays a broadcast back to an authorized reader, it's decrypted automatically as part of loading the page. There's nothing you need to configure or turn on for this protection to apply, it's on for every broadcast you send.

Related help

Data sources

  1. 1.How Verinode protects network communications. Verinode Trust & Security.
Was this helpful?