Buzz · Connect

Buzz, inside your AI.

Your clinicians already use AI. BuzzWave connects their favorite assistant to Buzz, bringing trusted answers into the conversation and sending messages back to the care team. No starting over.

Out and back. One conversation. No app switch.

BuzzWave ↔ BuzzLightning + BuzzBrain answers out · BuzzSpace collaboration in · Claude · ChatGPT · Grok

Kestrel Hollow · demonstration agency
Your AI · Claude

Pick a moment below.

Buzz · your groups

Answers come from here. Messages land here.

Three moments from a field day. Pick one.

Illustration on a demonstration agency. Exchanges are written for this page and call no live service. Titles cited are real entries in Skyscape's licensed library.

How it works

Connect once. Then every question can make the round trip.

Your clinician keeps the assistant they already like. Buzz does the knowing and the delivering.

1 · Connect

Buzz joins the assistant

Your administrator turns BuzzWave on. Each clinician links their own AI assistant to their own Buzz account, once.

2 · Answers out

From Buzz, with the source

Clinical questions draw on BuzzLightning's licensed references. Policy questions draw on your agency's shelf in BuzzBrain. Unread messages and mentions come from your own Buzz inbox.

3 · Collaboration in

Back to the team, in Buzz

"Post that to the field team." The message lands in the right Buzz group, with push notifications, as if they had typed it there.

Two directions

Other AI tools write the note. BuzzWave connects the answer to the team.

Scribes and BuzzWave do different jobs, and an agency can run both.

AI → chartAn AI scribeListens to the visit and writes the note. Valuable for the record.
Buzz ↔ your AI ↔ teamBuzzWaveBrings answers to the clinician and carries the conversation back to the care team.

Governance

Their AI. Buzz's rules.

The assistant is the clinician's choice. Who can see what, and who can say what to whom, stays exactly where it is today.

Bring your own

No new AI to buy

Claude, ChatGPT or Grok, whichever your organization approves. You do not standardize on our model, because we do not ship one.

Same permissions

One identity, everywhere

Every request runs as the signed-in clinician. Groups they cannot open in Buzz stay closed in their assistant, and sources they cannot read stay unread.

Same audit

The sender is the clinician

Messages arrive under the clinician's name, in groups they belong to, recorded in Buzz like any message they typed themselves.

BuzzWave runs on Buzz, under HIPAA with a business associate agreement. Skyscape holds a SOC 2 Type 2 attestation covering the Security trust services criteria. Data in Buzz is encrypted in transit and at rest.

Sixty seconds

The open-tab check

Three questions about how AI already shows up in your agency's day.

How many of your clinicians keep an AI assistant open during the workday?

When one of them finds a useful answer there, how does the rest of the team hear about it?

Has your organization chosen which AI assistants are approved for work?

Questions agencies ask

Which AI assistants does it work with?

Claude, ChatGPT and Grok, on plans that allow custom connectors. BuzzWave uses the open Model Context Protocol, so other assistants that support it can connect too.

Can the assistant see everything in Buzz?

No. It sees what the clinician asks for, as that clinician. If they cannot open a group or a source in Buzz, their assistant cannot either.

What about HIPAA?

Buzz runs under HIPAA with a business associate agreement, and BuzzWave works inside Buzz's permissions. What a clinician types into an assistant is governed by that assistant's own terms, which is why your organization picks the approved assistants and turns BuzzWave on.

Who decides when a message goes out?

The clinician. Messages go out under their name, to groups they belong to, when they ask for them to be sent, and Buzz records each one.

Is this an AI scribe?

No. A scribe writes the visit note. BuzzWave connects the clinician's assistant to Buzz answers and the Buzz team conversation. Plenty of agencies will want both.

Do we need our EHR connected?

No. BuzzWave connects to Buzz. If you want records flowing into Buzz channels, that is BuzzStreams, a separate decision.

How do we start a pilot?

Book a pilot scoping call and bring the assistant your clinicians already use. We connect it to a demonstration Buzz on the call so you see the round trip live, then agree which group and clinicians the pilot covers.

We don't use Buzz yet. Can we still pilot BuzzWave?

BuzzWave works inside Buzz, because Buzz groups are where its answers come from and its messages land. Agencies new to Buzz start with a Buzz group for the pilot, and the scoping call covers setup.

What does it cost?

Per user, per month, at about the price of a venti latte at the airport. Book a demo and we will put a number against your headcount on the call.

Start small

Start with one group and a few clinicians

A pilot needs one Buzz group, a few clinicians who already use Claude, ChatGPT or Grok, and an administrator who turns BuzzWave on. No EHR connection is needed to start. Bring your own AI to the scoping call and we run the round trip live.