A conversation ends. A space keeps going.

Where the 195 million comes from

Over the same period that organization sent 3.1 million messages and received 192 million. A received message is one delivery to one person, so 3.1 million sent and 192 million received is about 195 million deliveries through the network: the first number multiplied by how far each message traveled.

Which is where 61 comes from. Divide the deliveries by the messages and the average message reached 61 people. That is reach rather than readership: how many people a message got to, not how many read it or acted on it.

What 567 proves

Five hundred and sixty-seven people is not a large organization. It is one agency's clinical staff, and between them they stood up more than 102,000 spaces: roughly 180 each.

Nothing in these figures required a big agency. It required more than four years of a space per patient, and the patience to let them pile up instead of closing them.

The spaces accumulate at whatever rate you take patients on. The staff count barely moves.

The Buzz team puts three questions to a new organization before it goes live: should users be able to make groups at all, should groups be linked to the organization automatically, and should the administrator and managers be in them from the start.

Those three come first because they are the ones an agency cannot answer later. A group opened under the wrong policy is a private conversation containing clinical decisions, and it stays that way until somebody notices.

Zen mode suppresses two surfaces in a space and leaves the third alone.

• Recents inbox: suppressed. Belonging to the space does not put it in your inbox or push anything else out of it.
• Notifications: suppressed. No push for each message.
• Access to the messages: full. Every message in the space stays readable, at any time, on demand.

That third line is the whole point. Zen mode is not a quiet way of leaving a space. A supervisor in zen mode keeps complete retrospective visibility across the census and pays no attention tax until somebody addresses them. Mentions are the doorbell: a mention, individual or team, reaches a zen mode member immediately, and everything else stays quiet.

It can be assigned rather than merely chosen. A user can turn it on where the organization permits it, and a group admin can assign it. That is what makes it attention architecture the organization sets, rather than a preference each person is left to discover.

Zen mode is also what makes automatic inclusion tenable. Putting your admin and managers into every new space by default is a sane default only because zen mode exists. Without it, the same setting would bury the people it is meant to keep informed.

The trade. Zen mode exchanges ambient awareness for signal. A supervisor in zen mode will not stumble across a deteriorating situation in a space where nobody mentioned them, so the model carries a real dependency: if your staff do not mention the supervisor, the supervisor is not reached.

Onboarding teaches the set together rather than one setting at a time, and Concierge groups keep support live after go-live instead of ending at it.

Membership that follows the team

• Teams, not name lists. An organization team is a set of people with a common responsibility — a department, a role, a region — and a space can be associated with the team rather than with the individuals in it.
• It keeps up by itself. Membership reflects the team as it actually is, so when somebody joins, moves or leaves, the spaces they belong in follow without an administrator editing fifteen spaces.
• The team becomes the source of truth. Syncing a space to an organization team adds and removes members as the team changes, and it overrides any manual assignment on that space. That is the whole point of it, and it is also the part that surprises people, so it is a decision to make deliberately for each space rather than a box to tick everywhere.
• Combine the ways you are organized. Functional, departmental and geographic teams can be mixed, because real coverage is usually a cross section rather than a single org chart line.

Dynamic team membership is the mechanical half of the argument. A space outlives a person because its membership was never a list of people in the first place.

Finding things, and being found

• Categories are the luggage tags. Conversations are the suitcases. The organization standardizes the labels that matter to everyone, a team adds its own, and finding the right space stops being a scroll.
• Address the role, not the roster. A single @ names a person, @@ names a team, and @all names everyone in the space. A team mention resolves against the people on that team who are in this space, so an escalation survives a shift change or a reassignment and still cannot pull in somebody with no context on the patient. @all is the one an administrator can switch off, and at this scale that matters: one careless @all in a patient space reaches every member of it. Buzz shows you who a mention is about to reach before you send it, which is covered on the BuzzChat page.

A thread is one line of discussion held together inside a conversation that has moved on without it. Every standing space eventually has this problem, and has it worse than a chat does, because a space is the long-running case by definition: it carries a patient or a function for months, the people in it change, and the exchange somebody needs is a long way back.

A coordinator asks about a wound on Tuesday. The answer comes on Friday, from the on-call nurse who was not in the room on Tuesday. In between sit two hundred messages from six people about four other things. The exchange happened, all of it is still there, and it is not retrievable as an exchange.

This page has already argued that a space keeps going after the conversation that started it, and that the record is the point. Threading is what makes that record usable rather than merely complete. The scale sections make that argument about count; this is the same argument about depth. A space accumulating for a year is only an asset if one line of discussion inside it can still be lifted out whole.

A thread is a line of discussion that already exists as one, and the conversation carries a marker showing where it is.

What the thread view gives you

• The line is visible from inside the stream. A message that belongs to a thread carries a thread marker in the conversation, so the line announces itself where you are already reading rather than being something you have to remember exists.
• Opening it narrows the room to one discussion. The thread view shows that line and nothing else, lifted out of everything around it.
• It names who took part. In a space with six people feeding into four unrelated things at once, that is most of the work of reading an exchange back.
• It shows the span of dates it covers. Which in a long space is the fact you actually wanted: the Tuesday question and the Friday answer read as one exchange with four days inside it.
• Messages in the view can be selected, one at a time or all of them together.

STAT, and what clears it

• Urgency is a property of the message, not of the room. Any message can be sent as STAT with one tap in the composer, and a message already sent can be marked STAT afterward, so nobody has to decide in advance which space is the urgent one.
• A STAT is red for everyone in the space until it is cleared, so nobody has to guess whether somebody else already has it.
• It can break through a silenced phone. On mobile, STAT can come through Do Not Disturb, using Critical Alerts on iOS and the equivalent priority channel on Android. Those are not switches an application simply turns on for itself: Apple and Google approve them case by case, sparingly, and almost only for health and safety applications. A silenced phone is the most common reason an urgent clinical message goes unread.
• Acknowledge, or mute. Acknowledging means you have handled it, and it clears the red for everyone. Muting means you have seen it and it is not yours, and it clears only for you. Mute applies to STAT rather than to mention alerts, acknowledging stays available after you have muted, and a mute follows you across devices: clear it on your phone and it is cleared on the web.
• Why mute has to exist. Without it the only way to clear a red is to acknowledge, which tells everybody else an item is handled when it is not. Every false acknowledgement costs a real one some of its meaning.
• Acknowledging for a team. If a team mention reached you, acknowledging asks whether you are doing it for yourself or for the team, and any member of the team can do it for the team. A team STAT is a call for a hand to go up, not an instruction to a named person. A shared work queue, not a chain of command.
• All of it in one place. STAT messages across your threads roll up into a single read-only list, reached from the main menu, with a filter for the threads that still have unread urgent messages, and one counter in the header combines them with unacknowledged messages that name you. Mentions also keep a per-conversation view of their own, with one action to acknowledge all of them.

When it does not land

Escalation in Buzz is something a person does. A nudge happens because somebody decided to send one. No timer promotes an unacknowledged message and nothing routes it onward by itself.

Automatic escalation is how paging systems produce the alert storms that taught a generation of clinicians to stop trusting alarms.

The ladder a person climbs runs from a mention, to a plain nudge, to a nudge sent as STAT, to a one-to-one conversation. It narrows as it rises: pressure lands on fewer people rather than more, which is the opposite of how escalation usually works.

What the record keeps

A mention, a nudge, an escalation to STAT, an acknowledgement and a mute each carry who did it and when. That sits in the message's metadata rather than in its body, so the question a supervisor or a reviewer actually asks, whether the on-call was notified and when, can be answered without opening the clinical content of the message. Minimum necessary access follows from where the data sits, rather than from somebody remembering a rule.

Every rung below STAT exists to keep STAT rare. A signal that can wake somebody at three in the morning stays useful only for as long as people trust that it is used correctly, and the graded ladder underneath it is what protects that top rung.

Buzz treats the people around a patient as a circle that a clinician builds up over time rather than a fixed directory: peers across other organizations, consultants and specialists, referral sources, community partners. BuzzLink reaches the ones who are not on Buzz at all, and outreach to them is one of the four conversation domains in its own right.

Partners inside a space

A space can name the person it is about, and that person does not have to be on Buzz. A patient or client with no account at all can be the subject the space is organized around, which is how a standing space stays recognizable as theirs.

Ancillary, field and temporary staff come in on associate accounts, with the restricted reach described above. A space can also be bridged to the accounts that correspond to it in a BuzzStreams integration portal, an EHR platform or another enterprise system, so the space and the record point at each other.

A space can name secondary organizations whose members may also be included. Naming one establishes who is eligible, and it does not add anybody. Eligibility and membership stay two separate decisions.

If your team already runs on Buzz, the question is which of your standing groups is really a space in disguise — the one that keeps being rebuilt, or the one only one person can see into. If you are new to Buzz, start with BuzzChat and the conversations you have today.