If your front desk and clinical staff coordinate through sticky notes, hallway relays and email, the fix is a routing system with three parts: role-based chat channels, rules for who answers what and by when, and tasks with one owner. A staff chat tool supports that system. If any message may contain protected health information (PHI), the tool needs a signed business associate agreement (BAA) that covers the plan you buy.
- The short answer: separate channels by role and turn requests into tasks
- Why sticky notes, hallway relays and email fail
- Channels by role: who talks where
- Message relay rules: who answers what, and by when
- Turn requests into tasks with an owner and a deadline
- A daily communication routine for the practice
- One-page front desk–clinical communication template
- Choosing a tool to support the system
- FAQ
The short answer: separate channels by role and turn requests into tasks
What tool helps when front desk and clinical staff communicate over email and sticky notes? Use a staff chat app with role-based channels, reply-time rules and tasks that each have one owner. If messages may include PHI, choose a tool whose vendor signs a BAA on the plan you use.
How does a practice manager stop relaying messages between doctors and staff? Send requests to a shared role channel that the right person owns. When requests stop passing through one person, the manager reviews open items instead of carrying each one down the hall.
What do dental teams use when staff ignore email? Short mobile chat messages in a channel for their role or location, plus a daily huddle. Hygienists, assistants and front desk staff rarely sit at a desk during the day. They will read a two-line message on a phone or workstation between patients.
Scope of this guide: This guide covers operational and administrative coordination, such as room turnover, schedule changes, paperwork, supplies and equipment. Urgent clinical issues, clinical handoffs, documentation and patient messages stay in your clinical systems, on the phone or in person.
You can find more guides like this one in the operations library for clinics and practices.
Why sticky notes, hallway relays and email fail
Most relay problems are routing problems, not people problems. Each common workaround breaks in a predictable way.
- Sticky notes have no owner, no timestamp and no record. A note left on a monitor in Room 2 stays there after the shift that wrote it goes home.
- Hallway relays depend on one person, often the practice manager. That person becomes the bottleneck and ends up knocking on exam room doors mid-visit to pass on a message.
- Email is too slow and too noisy for same-day questions. "Is Room 3 ready?" does not belong in an inbox next to vendor invoices. Front desk and clinical staff also rarely sit at a desk long enough to read email.
- Personal texting and WhatsApp groups mix work with personal chats. Admins have no control when someone leaves, and patient details end up on personal phones. Read more about why staff texting creates PHI risk.
These are the usual signs of the problem in daily operations:
- Staff ask the same question twice.
- Callbacks slip to the next day.
- Rooms sit dirty while patients wait in the lobby.
- The manager can't say which requests are still open.
Channels by role: who talks where
Set up a small number of channels, and give each one a clear purpose.
| Channel | Members | What belongs there | What does not belong there |
|---|---|---|---|
| #front-desk | Receptionists, schedulers, check-in/check-out | Coverage, phone overflow, schedule questions within the desk | Clinical questions, HR matters |
| #clinical-team | MAs, nurses, hygienists | Room status, supply shortages, workflow coordination | Clinical documentation, urgent clinical issues |
| #providers | Physicians, dentists, NPs, PAs | Running-behind notices, coverage, operational decisions | Patient care discussion that belongs in the EHR |
| #front-to-clinical | Front desk and clinical staff | The main handoff channel: arrivals, late patients, room readiness, schedule changes | Anything clinically urgent |
| #announcements | Everyone (read-only; managers post) | Policy updates, closures, schedule changes, the pinned charter | Replies and side conversations |
| #billing-and-insurance | Billing, front desk, practice manager | Prior-auth paperwork, eligibility questions, coding questions for billing staff | Patient-facing messages |
| #location-[name] | Staff at one site (multi-site groups) | Site-specific facilities, staffing and supplies | Group-wide announcements |
Send requests to the shared channel, not a direct message. If the owner of a request is out sick or with a patient, someone else in the channel can pick it up. Use direct messages only for one-to-one matters such as HR questions, shift swaps or personal follow-ups. For the bigger people issues behind those conversations, see HR in healthcare: challenges and trends.
Dental groups: Add one channel per location and a shared #lab-and-supplies channel for case tracking, lab pickups and supply orders.
Keep the list short. Start with five to seven channels. Add a new one only when an existing channel gets noisy enough that people mute it.
Message relay rules: who answers what, and by when
Every request type needs an owner and an expected response time. The times below are suggestions. Your practice manager should set times that fit your schedule and staffing.
| Request type | Who sends | Who owns the reply | Suggested response time | Escalation path |
|---|---|---|---|---|
| Patient running late or schedule change | Front desk | Rooming MA or hygienist for that provider | Within 5 minutes | Walk to the clinical station |
| Room or chair turnover | Front desk or clinical | Clinical team | Within 5–10 minutes | Clinical lead |
| Insurance or prior-auth paperwork question | Clinical or front desk | Billing and insurance | Same day | Practice manager |
| Supply request | Clinical | Designated supply owner | By end of day | Practice manager |
| Provider running behind | Provider or MA | Front desk | Within 5 minutes | Front desk lead tells waiting patients |
| Equipment or IT issue | Anyone | IT contact or office manager | Within 1 hour (sooner if it blocks patient flow) | IT vendor or MSP |
Never only by chat: Do not send anything clinically urgent only by chat. Walk over or call, and follow your clinical protocol. Chat is for operational coordination. It is not an alerting system.
Message format: Each message should say who or what, what is needed, and by when. For example: "Room 3 ready? Next patient checked in at 10:40." Include only the minimum information needed, and add no patient detail beyond what your policy allows. This follows the HIPAA minimum necessary standard in 45 CFR 164.502(b). Section 164.514(d) covers role-based staff access (ecfr.gov).
Mention the role, not everyone. @mention the owning role or person instead of @everyone. When a request is handled, reply "done" in the thread so the sender knows it is closed.
The manager reviews instead of relaying. The practice manager scans for unanswered requests and stalled items. They step in only when the escalation path is needed.
Turn requests into tasks with an owner and a deadline
When a message becomes a task: Convert any request that won't be finished within the shift or that needs a follow-up. Examples include a patient callback, a form to complete, a records request or a supply order.
Task rules:
- One owner. "The front desk" is not an owner. "Maria, front desk" is.
- A due date. "Soon" is not a due date. "Thursday by noon" is.
- A status. Use one of the four statuses below.
- A role queue for unassigned tasks. Unassigned tasks should not live in someone's memory.
A simple board: Use four columns: To do, In progress, Waiting on someone, and Done. Review the board at the morning huddle. Pay close attention to items stuck in "Waiting on someone," because that is where callbacks and paperwork usually stall.
Keep tasks operational. Clinical orders, results follow-up and documentation belong in the EHR, not on a chat board.
A daily communication routine for the practice
Before opening (10 minutes). Hold a short huddle that covers:
- Schedule pressure points, such as double-booked slots, new patients and long procedures
- Staffing gaps
- Open tasks from the board
The daily huddle template helps keep it to ten minutes.
During the day. Front desk and clinical staff coordinate in #front-to-clinical. The practice manager checks open requests and the task board twice, once mid-morning and once mid-afternoon.
End of day. Close or reassign every open task. Then post tomorrow's known issues in the right channel, such as "Hygienist out Thursday" or "Autoclave service at 8:00." The end-of-shift operational handoff guide covers what to include.
Weekly (15 minutes). Look at which requests kept repeating and fix the root cause. For example, if staff asked "Is Dr. Lee's 2:00 a new patient?" six times, add a new-patient flag to the schedule template. If supply requests came in late, add a supply check to the closing checklist. It is also a good moment to thank the people who kept things moving; see these staff appreciation ideas for clinics.
Onboarding. Make channel rules part of new-hire training so new staff learn the system on day one instead of picking up hallway habits. Add the rules to your front desk training checklist, alongside the core medical receptionist role, duties and skills.
One-page front desk–clinical communication template
Copy this charter and fill it in. Then pin it in #announcements and review it quarterly. The example below is illustrative. It describes a fictional two-provider primary care practice with 12 staff, not a real customer.
FRONT DESK – CLINICAL COMMUNICATION CHARTER
Practice: [Example: Maple Street Family Medicine, illustrative]
Charter owner: [Practice manager name] Last reviewed: [date] Next review: [date + 3 months]
1. CHANNELS
#front-desk ......... desk coverage, phones, scheduling within the desk
#clinical-team ...... room status, supplies, MA/nurse workflow
#providers .......... running behind, coverage, operational decisions
#front-to-clinical .. main handoff channel (arrivals, late patients, rooms)
#announcements ...... read-only; managers post; this charter is pinned here
#billing-and-insurance prior auth, eligibility, paperwork
2. RELAY RULES
Late patient / schedule change -> rooming MA ......... reply within 5 min
Room turnover ......................-> clinical team .. reply within 10 min
Prior-auth / insurance question ....-> billing ........ same day
Supply request .....................-> [name] ......... end of day
Provider running behind ............-> front desk ..... within 5 min
Equipment / IT issue ...............-> [name / MSP] ... within 1 hour
3. NEVER BY CHAT ONLY
- Anything clinically urgent: walk over or call, per clinical protocol
- Clinical handoffs and documentation: EHR
- Patient messages: patient portal or phone
4. MESSAGE FORMAT
Who/what + what is needed + by when. Example: "Room 3 ready? Next patient checked in 10:40."
@mention the owning role. Reply "done" in the thread when closed.
5. TASK RULES
Not done this shift, or needs follow-up -> make it a task.
One owner, one due date, one status (To do / In progress / Waiting / Done).
6. DAILY ROUTINE
7:50 huddle (10 min) | 10:30 and 15:00 manager scans open items |
End of day: close or reassign tasks, post tomorrow's issues | Friday: 15-min repeat-request review
7. PHI POLICY
Minimum necessary only. PHI only in tools covered by a signed BAA.
See: [link to your HIPAA policy]. No patient details in personal texts.
Choosing a tool to support the system
Set the rules first. A tool only makes them easier to follow. These are the main categories practices consider:
| Category | Built for | Staff chat | Tasks | BAA availability and plan | Fit for a small practice |
|---|---|---|---|---|---|
| Patient communication platforms (e.g. Spruce Health) | Patient messaging, phone and fax. Some also offer team chat. | Varies. Spruce Health offers secure team chat on all plans, including Basic at $24 and Communicator at $49 per user per month (sprucehealth.com). | — | Spruce Health includes a BAA automatically on all trials and paid plans (sprucehealth.com). | Strong if patient messaging is the main need |
| General team chat in an office suite (Microsoft Teams, Google Chat, Slack) | Office and knowledge-work teams | Yes | — | Teams: Microsoft's HIPAA BAA covers Teams. Microsoft offers this BAA by default through the Microsoft Online Services Data Protection Addendum for commercial and GCC Microsoft 365 / Office 365 customers (learn.microsoft.com). Confirm your subscription with Microsoft. Google Chat: Google Chat is included functionality under Google Workspace's HIPAA BAA once an admin accepts the BAA in the Admin console. Third-party apps are excluded, and the legacy free edition cannot accept the BAA (workspace.google.com). Slack: A BAA is available only on Slack's top enterprise plan (Enterprise+, called Enterprise Grid on Slack's older pages). Slack may not be used to communicate with patients, and third-party apps are not covered (slack.com). | Good if staff already use the suite on mobile |
| Staff chat and work coordination with a BAA | Internal coordination across roles, shifts and locations | Yes | Yes, usually basic | Check each vendor. Chanty offers a signed BAA on Business and Enterprise, not on Free. | Good for practices moving off texting and sticky notes |
| Personal messengers and SMS | Personal communication | Informal groups | No | — | Not suited to work messages that may contain PHI |
A dash means this guide does not compare that item. Check the vendor's current documentation.
If your practice already uses Microsoft 365: First check whether your Microsoft BAA covers Teams. Microsoft lists Teams as in scope for its HIPAA BAA. Microsoft offers that BAA by default to covered entities and business associates on commercial and GCC Microsoft 365 / Office 365 through the Data Protection Addendum (learn.microsoft.com). If your subscription is covered, start with Teams. A separate tool makes sense mainly in two cases: staff won't adopt Teams on their phones, or you want a simpler, messenger-style app for front desk and clinical staff.
Checklist for any tool:
- A signed BAA that covers the exact product and plan you buy. For an example of what to look for, see what Chanty's BAA covers.
- Mobile apps your staff will actually open between patients
- Role-based permissions, so billing, clinical and front desk channels stay separate
- The ability to turn a message into a task with an owner and a due date
- Guest access for outside vendors, such as an IT provider or dental lab, limited to specific channels
- Admin control to remove access the day someone leaves
- Price per user at your headcount
One option in the staff chat category: Chanty is a staff chat and work coordination app for practices. It offers:
- Role channels, announcements, files and calls
- The option to turn any message into a task on a Kanban board
- Apps for iOS, Android, macOS, Windows and web
Chanty supports HIPAA compliance with a signed BAA on the Business and Enterprise plans, not on Free. It does not replace your EHR, patient messaging or clinical alerting. Enterprise pricing is sales-led, and the Chanty team confirms Enterprise terms on request (chanty.com/pricing). For more detail, see HIPAA-compliant chat for staff, staff chat for small medical practices and healthcare communication software for clinic staff.
Honest limits:
- Task management is basic (list and Kanban) and is not built for complex projects.
- There is no built-in shift scheduling or time tracking.
- Chanty's BAA does not cover integrations that touch PHI, such as file storage or automation tools. Each of those integrations needs its own BAA with that vendor.
Where Chanty fits. chanty.health is published by Chanty, a team chat for clinic staff with a signed BAA from the Business plan. If your team still coordinates in personal group chats, see how HIPAA-compliant staff chat works or start free.
FAQ
Our front desk and clinical staff communicate over email and sticky notes. What tool would help?
A staff chat app with role-based channels and tasks that each have one owner, used with clear reply-time rules. If messages may include PHI, choose a vendor that signs a BAA covering the plan you buy. Set up the channels and rules first, then pick the tool.
What software stops a practice manager from relaying messages between doctors and staff all day?
Any staff chat that lets requests go to a shared role channel, such as #front-to-clinical, instead of through one person. The software only helps if you also define who owns each request type. Once you do, the manager reviews open requests instead of carrying them.
What communication tool do dental teams use when staff ignore email?
Dental teams that ignore email tend to respond to short mobile chat messages in a channel for their role or location, combined with a daily huddle. In multi-site groups, add one channel per location and a shared #lab-and-supplies channel.
Can front desk staff send patient names in a staff chat?
Only if three things are true: a signed BAA on your plan covers the chat tool, your HIPAA policy allows it, and the name is actually needed. Even then, share only the minimum necessary information. Many messages need no patient detail at all, such as "Room 3 ready? Next patient checked in at 10:40."
Should urgent clinical issues go through team chat?
No. Do not send anything clinically urgent only by chat. Walk over or call, and follow your clinical protocol. Team chat is for operational and administrative coordination, not clinical alerts or handoffs.
We already use Microsoft 365. Do we need another chat tool?
Not necessarily. Microsoft lists Teams as in scope for its HIPAA BAA, which it offers by default through the Data Protection Addendum for commercial and GCC Microsoft 365 / Office 365 customers (learn.microsoft.com). Confirm your specific subscription with Microsoft. If Teams is covered and staff use it on mobile, apply the channel and relay rules in Teams. Consider a separate tool if adoption stalls or you want a simpler messenger-style app.
Is a free chat plan safe for messages that may include PHI?
Only if the vendor signs a BAA that covers the free plan. For example, Chanty's Free plan does not include a BAA. If a free plan has no BAA, keep PHI out of it and use it only for non-PHI coordination, or upgrade to a plan that includes a signed BAA.
How many channels should a small practice start with?
Five to seven. A typical set is #front-desk, #clinical-team, #providers, #front-to-clinical, #announcements and #billing-and-insurance. Add a channel only when an existing one gets noisy enough that staff start muting it.