A small home health agency can roll out a messaging app without an IT team by creating individual accounts, inviting a small pilot group, installing the apps, organizing conversations, testing everyday workflows, and then expanding to everyone. With Brosix, an owner or administrator can manage the agency’s private network through a web-based control panel without installing a server. Clear onboarding instructions and hands-on testing matter more than a large technical project, but privacy rules and communication expectations still need planning.
Set a few ground rules before inviting staff
Choose one person to manage accounts and answer setup questions. Start with a narrow purpose, such as internal staffing coordination and office-to-field communication, rather than trying to move every agency process into chat.
Write down what belongs in the app, who should have access, and which situations require a phone call instead. Keep required clinical documentation in the agency’s designated record system; a chat message should not become a substitute for it.
If staff will exchange protected health information, review the intended use, access rules, device practices, and retention requirements before doing so. Brosix can support HIPAA-compliant use, and a Business Associate Agreement is available on request, but the app alone does not make an agency’s workflow compliant. Use fictitious information during initial testing.
1. Create individual user accounts
Use the Brosix web-based admin control panel to create and manage the team’s private network and user accounts. Normal setup and administration do not require dedicated IT staff.
Give each employee a separate account with a recognizable name. Keep sign-in instructions simple, but do not confuse simple credentials with weak passwords: use a consistent username format and strong, unique passwords rather than a shared office login.
Review user permissions, managed contact lists, and feature controls so staff have access appropriate to their roles. Decide how you will update access when someone changes responsibilities or leaves the agency.
2. Invite a small, representative pilot group
Start with a scheduler, a field clinician, and an office administrator, for example. Include someone who is less comfortable with new software; their experience can reveal instructions that need clarification.
Send each participant a short onboarding note with:
- The app name and which device they should use.
- Their individual sign-in details, delivered through an appropriate secure method.
- The purpose of the pilot and what information must stay out of test messages.
- The person to contact if installation or sign-in fails.
A one-page instruction sheet is usually more useful at this stage than a long training manual.
3. Install the mobile and desktop apps
Help field staff install the appropriate iOS or Android app on agency-approved devices. Office staff can use the native Windows, macOS, or Linux applications; Brosix also has a web version. The browser-based admin panel is separate from the apps employees use to communicate.
Walk each pilot participant through signing in, finding a coworker, sending a message, and checking notification settings. If personal phones are allowed, explain the agency’s expectations for device locking, message previews, lost-device reporting, and off-duty availability.
4. Define a simple conversation structure
Create only a few clearly named groups or chat rooms at first. For example:
- Agency updates: General internal announcements without patient details.
- Staffing coordination: Availability and coverage discussions among the appropriate staff.
- Pilot feedback: Setup questions and problems found during testing.
Use one-to-one messages for questions that only involve one coworker. Restrict conversations containing sensitive information to authorized participants rather than placing everyone in every group.
Set an acknowledgment rule for requests that need action. A read receipt can show that a message was seen, but it does not confirm that someone accepted a task.
5. Test a complete workflow
Run a realistic exercise using fictitious details. Have the scheduler send a mock coverage request, a field employee acknowledge it from a phone, and the office confirm the outcome from a desktop.
Check whether everyone can find the right conversation, receive notifications, understand who should respond, and follow the fallback procedure if a message goes unanswered. Test in the environments where staff normally work, including places with unreliable connectivity.
Fix confusing group names, missed notifications, and unclear instructions before adding more people. Keep urgent communication on the agency’s established escalation path rather than relying on chat alone.
6. Expand in manageable batches
Once the pilot works, add the remaining staff in groups small enough that you can help each person sign in and complete a test exchange. Reuse the corrected onboarding sheet and ask pilot participants to help coworkers with basic questions.
Set a clear date when the app becomes the standard channel for the agreed routine messages. After launch, review membership, remove access promptly when staff leave, and check whether conversations are being used as intended. The rollout is complete when staff can reliably follow the workflow—not merely when everyone has an account.