Who should be able to message families directly? Who needs to see every conversation? A practical permission framework for ABA practices — and what BloomText provides today.
Get started for freeSchedule a demo →ABA practices with distributed therapy teams face a specific communication governance problem: therapists need to communicate with families, but owners and supervisors need visibility into what is being said. The ideal setup is a permission matrix where owners see everything, BCBAs can message families and staff, and RBTs participate in supervised team conversations rather than initiating private family threads. BloomText provides admin visibility, team-based conversations, permission controls that restrict staff access to patient contact information and direct messaging, and admin-controlled access revocation.
An ABA practice with five therapists working in families' homes has five people who might text parents from personal phones. The owner has no visibility into those conversations. When staff leave, the messages go with them. When a parent files a complaint, the practice cannot produce a record.
The problem is not that therapists should never communicate with families. They should — parents need updates, therapists need to coordinate logistics, and the daily back-and-forth keeps therapy on track. The problem is that without a permission structure, any staff member can create a private channel with any family that no supervisor sees.
The most common approach is a blanket policy: "all parent communication goes through the front desk." This works for appointment scheduling and administrative matters. It does not work for a BCBA who needs to send a parent a quick update about today's session or coordinate a schedule change in the next 20 minutes.
The policy creates a bottleneck, staff work around it, and the practice ends up in the same position: therapists texting families from personal phones with no organizational visibility.
Different roles need different levels of communication access. Here is a practical framework:
Practice owners and organization admins should be able to see every conversation on the account — parent-facing and internal — without being individually added to each one. This is the oversight layer. BCBAs and supervisors should be able to message families directly, participate in team conversations, and communicate with staff. They are the primary parent-communication channel. RBTs and line therapists should participate in supervised team conversations where the BCBA and supervisor are present, rather than creating private direct conversations with families. Administrative and front-desk staff should handle scheduling, paperwork requests, and general announcements.
The goal is not to prevent RBTs from seeing family messages — it is to ensure that family communication happens in a context where supervisors have visibility.
BloomText gives practice owners and org admins visibility into every conversation on the account — no need to be added individually. Team conversations can be structured so that each family has a thread that includes the assigned BCBA, RBT, and supervisor. Staff access can be revoked the same day someone leaves, and the full conversation history stays with the practice. See supervised parent communication for ABA for how this works in practice.
BloomText also supports permission controls that restrict what staff can see and do — for example, preventing certain team members from viewing patient contact information or initiating direct conversations with families. Combined with team conversations where supervisors are present and admin visibility to monitor compliance, practices can enforce the permission structure that fits their clinical model.
This is a communication policy supported by team structure and admin oversight, rather than technical enforcement at the individual permission level. Per-role messaging controls are on the product roadmap, and BloomText has received this request from multiple ABA and home-care practices.
Step one: create a team conversation for each family that includes the BCBA, RBT, supervisor, and parent. All family communication happens in this thread. Step two: establish a written policy that staff do not create private direct conversations with families outside the team thread. Step three: use admin visibility to periodically review conversations and identify any private threads that were created outside the team structure.
When a violation is identified, admins can review the full conversation, request transcript exports for documentation, and take corrective action. See how ABA practices audit and export parent communication for the export process.