Staff side
ABA staff communication: your team has a group chat. Parents are not in it.
The internal channel usually exists and often works. The parent channel does not exist, and the internal one cannot be turned into it. That gap is the whole problem, and it does not get fixed by picking a better chat app.
At the clinic I work at we use Teams, in a group chat. As an internal tool it is fine. It is a real enterprise product, it is administered, and it is not somebody’s personal number. Staff can reach each other, which is more than a lot of clinics have.
Parents are still not kept in the loop. Not because anyone decided they should not be, but because there is nowhere for them to be. The day gets described once, to colleagues, in a thread no family can see, and then it is never described again.
Four problems that a better chat app does not fix.
These hold for Teams and Slack as much as for a group text, because they are properties of a thread rather than of a vendor. Compliance is a separate conversation and worth having with whoever owns it at your clinic.
A thread is ordered by time, not by child
What happened with one child is scattered through a channel in between shift swaps and lunch orders. There is no version of the day you can open and read start to finish.
You cannot scope it per family
A channel shows every child to every member. That is exactly why parents cannot be added to it, and it is why a chat tool can never double as your parent channel.
A sender name is not an audit trail
Knowing who typed a message is not the same as knowing who observed a behavior, when, and whether the entry was later edited.
It is unsearchable at the moment you need it
When a parent or a funder asks about the 14th, scrolling is the only option, and most of what you scroll past is scheduling.
If it is a personal-phone group text, add four more.
Plenty of clinics are here rather than on an administered tool. This field has turnover, and any system that assumes the same person keeps the same caseload fails on a predictable schedule.
The record belongs to the handset
Stored on a device you do not own and cannot reach.
Access cannot be revoked
There is no admin console on a personal messaging app.
Nothing transfers at turnover
The history of a child walks out with the phone.
Parents notice first
Consistency drops the week after someone leaves, and families read that as the clinic.
A secure thread is still a thread.
If your only problem is that staff are texting from personal numbers, then moving the team onto an administered tool solves it. Teams, Slack, or one of the compliant healthcare messaging products, some of which are good. Do that, and do it before you talk to us.
What none of them change is the shape of the information. A thread is a list of sentences in the order they were typed. What happened with a child is not a list of sentences; it is a set of events, each attached to one child, one session and one technician. Encrypting the thread makes it safer without making it retrievable, and you still end up recording the day twice: once to your colleagues, once to the parent.
One record, two audiences.
This is the part that is specific to Cliqit. The record your staff keep and the record parents see are the same record, filtered by role. A technician taps a child and taps what happened. The next technician sees it. Supervision sees it. The parent sees their own child’s version of it.
Logged once
No retelling the afternoon to a parent after telling the team.
Scoped by role
Parents reach their own child. Staff reach their caseload.
Owned by the clinic
History and audit trail stay when people leave.
The clearest case for that is the shift handoff, where the internal need and the parent-facing need are the same information three hours apart. The parent-facing half is covered in ABA daily notes for parents, and you can try the logging flow on the homepage without talking to anyone.
Questions about staff communication.
We already use Microsoft Teams. Is that not enough?
It is enough for staff to reach each other, and that is worth having. It does nothing for parents, because a channel shows every child to every member, so families cannot be added to it. You end up with a working internal channel, no parent channel, and the day described once to colleagues and never to the family.
What is wrong with a staff group text at an ABA clinic?
Operationally, it puts a record of patient care on devices the practice does not control, shows every child to every member of the thread, gives you no dependable audit trail, and disappears when a technician leaves. Whether the content itself is defensible under your policies is a separate question for your compliance lead, and worth asking.
How should RBTs and BCBAs communicate about a child instead?
Against the child’s own record, not in a thread. An entry logged on a child carries who logged it and when, is visible to the staff assigned to that child and to supervision, and is still there in three months when someone asks. The conversation and the documentation stop being two separate things.
Is Cliqit HIPAA compliant?
Cliqit is built for HIPAA compliance: encrypted in transit and at rest, role-based access, and an audit trail on every update. Our data infrastructure is covered by signed BAAs and we sign one with your clinic directly, before any child data goes in.
Is this just secure messaging with a different name?
No, and secure messaging on its own would not solve the problem. Encrypting a thread makes it safer but it is still a thread: unstructured, hard to search, and separate from the record of what actually happened with the child. Cliqit logs events against a child, and the messages and the record are the same thing.
Do parents see what staff log?
Parents see updates about their own child and the end-of-day summary, and nothing else: not other children, not other families, not your staffing. Internal notes stay internal, and access is scoped per role.
What happens to a technician’s history when they leave?
It stays with the clinic, because it was never on their phone. You revoke their access, their replacement opens the child and reads the same history, and the audit trail still shows who logged what.
Fifteen minutes with Abdihafid.
He is a behavior technician, so this is a conversation about the floor rather than a product walkthrough. Bring whatever your team uses today.