Broadcast read tracking and 90-day trends

What this is

Every text broadcast you send to the network carries one number back to you: how many operators have read it. Broadcast → Announcements is where that number lives, both as a running total on each broadcast's tile and, once a broadcast has been out long enough, as a trend you can read against where reads stood 30 days earlier. Click any broadcast and a detail overlay slides in showing its full, untruncated message alongside that same read count and trend line.

This is a reach signal, not a surveillance tool. Verinode counts unique reads per broadcast (each operator's first interaction with it, once, no matter how many times they reopen it later), and that single running total is the only thing HQ ever sees. There is no roster anywhere in Broadcast → Announcements of which named franchisee has or hasn't read a given message. The count tells you whether the network is engaging with what you send, not who specifically did.

Where to find it

Open Broadcast from the HQ sidebar at hq.verinode.ai/broadcast. A pill strip sits just under the page header with five tabs: Announcements, Initiatives, Surveys, Polls, and Consent. Announcements is the default landing tab, it's what loads at the bare /broadcast URL with no tab selected, and it's the tab this article covers: plain-text messages pushed into every active operator's IQ feed.

If you have send permission (an HQ admin role), a Send broadcast button sits in the page header. Clicking it opens a compose modal: a Subject field, a Body textarea (plain text only, the helper text under it reads "Plain text only. The broadcast lands in every active operator's IQ feed; read receipts roll back up to your Broadcasts tab."), and a Send to network button that stays disabled until both fields have content. On send, the modal reports "Sent, delivered to N operators" (N being the number of active operators the message fanned out to), then closes itself and the page refreshes. See Broadcasting to your network for the full compose and delivery flow. If you don't have send permission, the button doesn't render at all, you still see every hero number and tile below.

The hero panel

At the top of Announcements sits a hero panel labeled Text announcements. What it shows:

• Headline number: broadcasts sent in the last 30 days.
• Pill next to it: reads "N sent 30d" when at least one broadcast went out in that window, or "Nothing sent recently" when none did.
• Description line: if you have never sent a broadcast, this reads "Send a broadcast to push a text message into every active operator's IQ feed. Receipts post back as read counts." Once you've sent at least one, it switches to a running count, "N total broadcasts authored," followed by "last sent [X ago]" when a most-recent send exists.

Below that, three secondary figures:

• Operator reads 30d: the sum of read receipts across every broadcast sent in the last 30 days (sub-label: "Sum of read receipts in window"). This is a straight addition of each broadcast's read count, not a count of distinct operators, so one operator who reads three different broadcasts contributes three to this total.
• All-time broadcasts: the total number of broadcasts you've ever authored, with "Last sent [X ago]" underneath, or "None sent yet" if you haven't sent one.
• Avg reads / broadcast: total 30-day reads divided by the number of broadcasts sent in that window, rounded to the nearest whole read. Reads 0 when no broadcasts went out in the last 30 days (there's nothing to divide by).

Recent broadcasts

Under the hero, a row of tiles lists up to twelve broadcasts, newest first, each showing:

• Label: the read count, "N read" for exactly one, "N reads" otherwise.
• Headline: the broadcast's subject line.
• Sub-line: the first 80 characters of the body, truncated with an ellipsis if the message runs longer. Read the full message by opening the tile.
• Meta line: "Sent [X ago]" (today, a day count, a month count depending on how long ago it went out). When Verinode has captured at least two daily read snapshots for that broadcast, a short delta appends after it, for example "Sent 12 days ago, +6 reads vs Jul 2." That delta compares the broadcast's most recent snapshot to whichever snapshot sits closest to 7 days before it, and it only appears when the two differ (a flat week shows no delta at all).

If you haven't authored any broadcasts yet, this row reads: "No broadcasts authored yet. Use the Send broadcast button to push a text update into every active operator's IQ feed."

Click any tile to open its detail overlay.

Opening a broadcast: the detail overlay

Clicking a tile slides in a large modal titled with the broadcast's subject line. Inside:

Meta chips, top of the panel: a pill with the read count ("N read" / "N reads"), then "Sent [X ago]" using its own relative phrasing ("Today" for anything under a day old, then day counts up to a week, week counts up to five weeks, month counts beyond that), then the exact send date and time (for example "Jul 10, 2026, 3:45 PM").

Read trend, only when Verinode has at least two daily snapshots for the broadcast and the read count has actually moved: a bordered line reading the change in reads against a point roughly 30 days earlier, for example "+18 reads vs Jun 12 (44 reads)." A gain prints in green, a drop prints in red. Because the comparison always reaches for whichever snapshot sits closest to 30 days back rather than requiring an exact match, this line can appear well before a broadcast has been live for a full 90 days, as soon as there's a snapshot old enough to compare against. If the read count hasn't moved at all against that point, this block is simply omitted rather than showing "+0."

Message, the broadcast's full body, unlike the 80-character preview on the tile, with line breaks preserved exactly as written.

Footer note: "Per-franchisee receipt breakdown + resend / clone actions arrive with the broadcast lifecycle redesign. Today this view is read-only." That line is the plain statement of what this overlay does not do yet: no per-operator list, no resend, no clone, no edit. It's a read of what already went out and how the network responded in aggregate.

Close the overlay with the X in the header, the Escape key, or by clicking outside the card.

How the read count and trend are built

read_count on a broadcast is a single running total, not a log of individual reads. It increments once per operator, the first time that operator interacts with the broadcast card in their IQ feed, later re-opens by the same operator don't add to it. Once a day, Verinode snapshots that running total for every broadcast into a dated record, which is what turns a single live number into the trend lines you see on the tile and in the overlay. A brand-new broadcast won't have a trend yet, because a trend needs at least two of those daily snapshots to exist; give it a day or two after sending before expecting a delta line to appear.

That daily snapshot only ever stores a date and a count. It never stores which operators contributed to that count, so there is no way, in this view or anywhere else in Broadcast → Announcements, to look up whether a specific franchisee has read a specific message. What you get is exactly what the hero, the tiles, and the overlay all show: how many, and whether that number is moving.

Empty states

• No broadcasts sent yet: the hero reads "Send a broadcast to push a text message into every active operator's IQ feed. Receipts post back as read counts.", the pill reads "Nothing sent recently," and the Recent broadcasts row reads "No broadcasts authored yet. Use the Send broadcast button to push a text update into every active operator's IQ feed."
• Broadcasts exist but none in the last 30 days: the headline count and pill still reflect zero for the 30-day window, but the description line switches to the all-time count and last-sent date instead of the never-sent copy. Avg reads / broadcast reads 0 rather than dividing by zero.
• A broadcast with no read-trend data yet: the tile shows only "Sent [X ago]" with no delta, and the overlay shows the meta chips and full message with no Read trend block. This is normal for anything sent very recently, before at least two daily snapshots have accumulated, not a broken state.

How to use it

1. 1Open hq.verinode.ai/broadcast, staying on the default Announcements tab.
2. 2Read the hero: how many broadcasts went out in the last 30 days, total reads across that window, and the average reads per broadcast.
3. 3Scan the Recent broadcasts row for any tile carrying a delta, that's a broadcast whose reads have visibly moved in the last week.
4. 4Click a tile to open the full message, the exact send timestamp, and, once enough days have passed, the 30-day read trend.
5. 5Read the trend as a reach signal: a broadcast trending up is still gaining attention days after sending; a flat or falling one has likely already reached everyone it's going to reach.
6. 6If engagement across several recent broadcasts looks consistently low, that's a cue to shorten the message, send at a different cadence, or reserve broadcast for updates that genuinely need network-wide reach, not to look for who isn't reading, that isn't something this view can tell you.

Related reading

• Broadcasting to your network
• What HQ sees

Data sources