Needs a nurse tonight
UrgentBreathing changed since about eight. The family is asking whether to give the evening dose.
Acknowledged by the on-call RN at 9:44 PM.
The problem
Texting is easy. Being sure it was read is not.
Plenty of agencies never chose their messaging tool. It accumulated: a group text here, a personal number there, a paging arrangement nobody has reviewed in years.
- Consumer apps are not built for the way an agency is audited. The auditability and administrative control a healthcare team needs are not what a consumer messaging app is designed to provide, and what it keeps is not what a reviewer needs months later.
- The workarounds fail quietly. Teams have left other tools after crashes and dropped threads, after a free tier stopped delivering photos, and after someone noticed patient information sitting in a consumer app.
- Field clinicians work alone. Hours from the office, often out of reach, and holding the one piece of information the rest of the team needs.
The message that notified nobody
A BuzzChat message can send successfully and still notify nobody, because the mention inside it resolved to nobody. This is the failure nobody tests for. A delivery confirmation does not catch it: the message did arrive. It arrived addressed to no one in particular. There is no error state and nothing comes back, so the sender believes the page went out while the people who would have acted never learn they were expected to respond. It surfaces the way these things usually surface, when somebody notices later that the thing they asked for did not happen.
The failure an agency actually feels is a question that went unanswered, because nobody on the receiving end knew it was theirs to answer.
How it works
Start it. Mark it. Keep it.
Three things happen to every BuzzChat message, and the third is the reason an agency can still account for it a year later.
1 · Start it
A person opens the conversation
A BuzzChat conversation starts one-to-one with a clinician, staff member or approved partner, or as a group built for a patient, a team or a shift. A group can hold clinicians, administrators, patients, caregivers and approved outside partners.
2 · Mark it
Urgency travels with the message
Escalation and acknowledgement are built into a BuzzChat message rather than added by a second product. Any message can be marked STAT as you send it or afterward, and a STAT carries a red highlight for everyone in the group until it is cleared. A mention addressed to a role rather than to a named person keeps the escalation path intact through a shift change, PTO or a reassignment.
3 · Keep it
The thread is the record
Someone added to an ongoing conversation gets the prior messages, documents and discussion, not a blank screen. Activity is visible through audit trails, and conversations are archived.
One line of discussion, kept together
A clinical conversation is not a tidy exchange. A point made on Tuesday gets its answer on Friday, and in between sit two hundred messages from six people about four other things.
- Scrolling back is not the same as following it. Everything is still there. But before anyone can read that line of discussion they have to work out which messages belonged to it, and they have to do that work again the next time somebody asks.
- A thread is that work, done once and kept. One line of discussion inside a BuzzChat conversation can be held together as a thread, and a message belonging to one carries a thread marker where it sits in the conversation.
- Opening the thread shows that line and nothing else. The discussion comes out of everything that surrounded it, with the people who took part named and the span of dates it ran across.
A conversation that keeps everything is complete. Being able to pull one line of it back out, with the people and the dates attached, is what makes it usable.
Four ways to keep one message
Marking a BuzzChat message is about now. Keeping one is about later, and any message in a thread can be held in four different ways.
- Send the message to a Safe Memory Box. One touch, and the message is kept there.
- Pin the message. A pinned message is still in front of you when you come back to the conversation.
- Add the message as a Note. A note connected with this conversation, so the message keeps the context it arrived in.
- Create a Task out of the message. The message becomes the thing that has to get done, without anyone retyping it.
The difference
An unanswered BuzzChat message has somewhere to go, and a person sends it there.
Escalation is the line between messaging for work and messaging for care. In BuzzChat, delivery is where a message's job starts rather than where it ends.
Example escalation path
- Assigned clinicianThe person the message was for.
- On-call nurseWhoever is covering this evening.
- Clinical supervisorThe last rung before nobody.
Nothing sent yet.
Illustration, not a product screenshot.
Acknowledgement at any rung stops the climb.
An acknowledgement matters more than a read receipt. A read receipt says a screen lit up. An acknowledgement says a named person took it.
Escalation in BuzzChat is human-initiated: a person decides at every rung, and each rung is narrower and more private than the last.
- Who sets the path The sender sets it in the message itself. A mention can reach a named person, a role, or everyone in the group, and an administrator can switch the everyone case off. A role mention resolves only to the members of that role who are already in this conversation, so the page goes to the people already in the thread rather than to the whole role. Before it goes, a chip above the input counts the person and role mentions in the draft and flags the three ways a page goes wrong: somebody being paged twice, once individually and once through a role; a mention that resolves to nobody at all, a failure that normally raises no error state and that BuzzChat catches before you send; and a mention about to reach the entire group.
- What moves a message up a rung A person moves a BuzzChat message up a rung, every time: there is no interval, and nothing promotes an unacknowledged message or hands it to a backup on its own.
- What the thread records An acknowledgement and a mute record different things: handled, and seen. Acknowledging means the work is handled, and it clears the item for everyone in the group. Muting means you have seen it and it is not yours, and it clears only for you; mute applies to a STAT rather than to a mention alert, acknowledgement is still available afterward, and a mute follows you across devices, so clearing it on your phone clears it on the web. Without mute the only way to clear a red would be to acknowledge, which tells the group an item is handled when it is not, and every false acknowledgement costs a real one some of its meaning. If you were reached through a role mention, acknowledging asks whether you are answering for yourself or for the team, and any member of the team can answer for the team. That is the design: a team STAT is a call for a hand to go up, not an instruction to a named person. Shared work queue, not chain of command.
- What happens at the top The top of the ladder is a one-to-one, and you get there through the mention itself. A sent mention stays interactive: tap it for the fully resolved identity and two ways to follow through, a private one-to-one or a Nudge. The ladder runs from the mention, to a plain private Nudge, to a Nudge sent as STAT, to a one-to-one, so every rung is narrower and more private than the one before it.
Zen mode lets a supervisor hold full membership in a BuzzChat conversation at no ambient cost, so being in the conversation does not cost the ability to work. The recents inbox and the per-message notifications go quiet, while access to every message stays complete and available on demand. The mention is the doorbell. So a supervisor or an outside stakeholder can sit in a patient's conversation without drowning in it, and a mention or a STAT reaches them the moment they are actually needed. Together with team acknowledgement, that is what makes a task simple to get owned and closed.
What is in it
Everything a care team says to each other in a day.
BuzzChat carries the things an agency actually sends, in the forms it actually sends them.
Group messaging
Coordinate care teams in secure shared conversations, organized around patients, teams and care delivery.
Direct messaging
Communicate privately with clinicians, staff and approved partners.
Broadcasts
Share an update without starting an unnecessary reply chain. In a broadcast group, recipients cannot see the other members or reply.
Bulk messages and templates
Reach many recipients with one secure message, and standardize the updates your team retypes every week.
Shared documents
Care plans, reports and files stay connected to the conversation they belong to.
Joined midway, caught up
Add someone to an ongoing conversation and they get the prior messages, documents and discussion.
The groups agencies open first
- Home health teams
- Hospice care teams
- Behavioral health
- Case management
- Admissions
- Intake
- Clinical supervisors
- Referral partners
- Executive leadership
- Operations
- Patients and their families
“As we rolled out the BUZZ App and built it out per our process, the team started to see the power! The way our agency uses BUZZ is that we build out ‘patient channels’. Each patient channel (group) is titled with the patient’s name and DOB… In the end, a custom care coordination team has been built and ALL communication is shared with the appropriate team members so everyone has visibility of the play-by-play for that patient. This also provides a safety net with upper-level eyes on ALL channels and can step in and support or triage if necessary… I ask myself quite frequently how we ever survived without our beloved BUZZ!”
Wherever the clinician happens to be standing
- iOS, Android and the browser — including Windows PCs, Macs and Chromebooks.
- One account, several devices — conversations, documents and updates stay synchronized, so a clinician can change device without losing the thread.
- People outside your organization — approved external participants join when appropriate, and BuzzLink reaches people who are not on Buzz at all.
Safety and privacy
Where the information sits, and who can reach it.
These are the Buzz security and privacy facts an administrator can take into a compliance meeting. There is a fuller account of how Buzz handles message content.
Buzz is a HIPAA-secure platform with a SOC 2 Type 2 attestation for the Security Trust Services Criteria, a business associate agreement, encryption in transit and at rest, and one login per workforce member.
Getting started
Start with the team that is hardest to reach.
A BuzzChat rollout starts with one team rather than the whole agency: the shift, the branch or the on-call rotation where a missed message costs the most.
- Who The people who are hardest to reach on the worst evening: the field clinician out alone, the on-call nurse covering for her, the coordinator who took the family's call, and the supervisor who has to know it happened at all.
- How long A first rollout is counted in rotations rather than dates. One group carries its real urgent traffic until the people in it stop reaching for the old group text, and the next group comes across when it asks to. Nothing here waits on a cutover.
- Cost Terms are flexible: monthly, quarterly or annually, whichever suits the way your agency budgets. You are never locked in against your will, and the notice period is 60 days.
- What success looks like Success is fewer messages that reached nobody, acknowledgements that mean a named person took the work rather than that a screen lit up, and a supervisor who stays reachable without being buried.
Setting up an account on mobile or web takes under a minute, and people are invited by text or email. The hard part of a rollout is rarely the install; it is agreeing which conversations move first.
Every Buzz user has a one-to-one support chat, which is where most questions end. Above that sit two further levels, Support Plus and Concierge.
Questions agencies ask
How is BuzzChat different from BuzzSpace?
BuzzChat is the conversation a person starts; BuzzSpace is the one the organization owns and keeps. A BuzzChat thread is one-to-one, or a group somebody opens. A BuzzSpace is the larger plug-and-play space that other parts of the platform cross-pollinate into, and it outlives any single conversation. See BuzzSpace.
Do patients and families have to install the app?
No. BuzzLink reaches people who are not on Buzz, and a patient can join a video call from a link sent by text or email without installing anything.
Can people outside our organization take part?
Yes. Approved external partners can join a conversation when it is appropriate, alongside clinicians, administrators, patients and caregivers.
What happens when someone leaves the organization?
A person who leaves loses access to the organization's group and one-to-one messages, and is removed from the groups linked to the organization.
Can two people share a login?
No. Shared logins are not permitted, and each workforce member needs a unique user identifier.
Which devices does it run on?
iOS, Android and the browser, including Windows PCs, Macs and Chromebooks. One account works across several devices and stays synchronized.
What does escalation do if nobody answers?
In BuzzChat a person escalates, every time: a mention, then a plain private Nudge, then a Nudge sent as STAT, then a one-to-one. Nothing promotes an unacknowledged message after an interval, and nothing hands it to a backup. The ladder narrows. Paging systems typically escalate by broadening, waking more people and climbing the chain, which is how the alert storms behind alarm fatigue got started. BuzzChat goes the other way and gets more specific and more private with the one person who already owns the message. On a supported device, and where the required permissions are enabled, an urgent message can break past a silenced phone: on iOS through Critical Alerts, and on Android through the equivalent priority channel. Those entitlements need explicit platform approval, which Apple and Google grant sparingly and almost only to health and safety applications. A silenced phone is the most common reason an urgent clinical message goes unread.
What support do we get?
Email and phone support run Monday to Friday, 8 a.m. to 8 p.m. Eastern. The dedicated Buzz Concierge Group and Buzz Support Channel, both inside Buzz, are staffed 24/7, so the in-app channel is the one that does not stop at eight.
What about the EHR?
EHR integration is available through BuzzStreams, the module that bridges Buzz to the systems an agency already runs. There are methods for moving information both ways between the EHR and a variety of modules within Buzz, so what the team learns in a conversation does not have to stay there. BuzzChat itself is where the team talks; it is not a system of record, and it does not replace the chart.
The rest of the platform
A conversation is one surface. Buzz has several.
The other half of Reach
BuzzSpace
Where BuzzChat is the conversation a person starts, BuzzSpace is the one the organization owns and keeps — the plug-and-play space other modules feed into, outlasting any one thread.
See BuzzSpaceBuzzStreams
The bridge to the EHR and the other systems an agency runs.
See BuzzStreamsBuzzLightning
Clinical reference answers from a vetted medical library, at the bedside.
See BuzzLightningBuzzBrain
Cited answers from your policies, Medicare's rules and your state's.
See BuzzBrainBuzzFlow
E-signatures and document workflows, without a separate subscription.
See BuzzFlowStart here
Bring us the message your agency nearly missed.
One real conversation tells us more about your escalation path than any feature list will. Twenty minutes, your team, your worst evening.