Broadcasts
Broadcasts send a directive or an announcement to everyone in your organization — "get this done tomorrow", to the whole team, in one tap. Each teammate's app receives it, has their own Sage synthesize what it means for them, raises a notification, and waits for an explicit accept or decline — and you see who's in.
A broadcast lands as understanding, not a wall of text. Instead of a message everyone has to interpret, each recipient's Sage restates the ask, spells out what it means for them, lists first steps, and surfaces the deadline. Accepting files it into that person's memory, so their agents plan around it from then on.
❉ One tap to the org
A directive or announcement to your whole team from the Team hub or the composer.
❉ Synthesized per person
Each teammate's Sage translates it into what it means for them, with first steps.
❉ Explicit consent
Every recipient accepts or declines; accepting plans it into their memory.
❉ You see who's in
The Broadcasts tab shows who accepted, who declined, who hasn't answered.
/broadcast in the composer, or click the Open chip. Sage stages the broadcast as a card you review and send yourself — she can never broadcast on her own.What it is#
Broadcasts is one of the three surfaces of the Team hub — the encrypted layer connecting your org (with Signals and Team Asks). Where Signals shares status and Asks poses questions, a broadcast pushes action: the "everyone needs to do this" or "everyone should know this" message that would otherwise be an email nobody reads carefully. It rides the same end-to-end-encrypted machinery as the rest of the team layer, so the relay never reads the content.
Sending a broadcast#
Compose one in the Team hub or with /broadcast, and choose the kind:
Keep the text crisp and self-contained — a teammate reads it without your conversation's context — and put any deadline in the due field. Sage stages a card showing exactly what will go out; you review it and click send. She can't send it for you, and you should never assume it went until you clicked.
Each Sage synthesizes it#
Delivery is where a broadcast earns its keep. Each teammate's device receives the sealed message and their own Sage synthesizes it for them — the ask restated in plain terms, what it means for their work specifically, the first steps to take, and the deadline. So the same broadcast reaches a dozen people and each one gets a version aimed at their situation, not a generic blast.
Accept or decline#
A directive isn't done until the recipient answers. Each teammate explicitly accepts or declines — the same explicit-consent posture as the memory inbox. Accepting lands the directive in that teammate's memory, so their agents plan around it from then on; either answer travels back to you. Nothing is silently imposed on anyone: a broadcast asks, and each person decides.
Seeing who's in#
Your Team hub's Broadcasts tab shows the roll-up: who accepted, who declined, and who hasn't answered yet — so "did everyone get the freeze?" is a glance, not a round of pinging. Delivery is guaranteed even for teammates who were offline when you sent it: their device picks the broadcast up when it next comes online, and their answer flows back to the tab.