BREATHR + LENZABA

Add an AI assistant layer without fragmenting the clinic.

Breathr is an independent add-on product that connects to LenzABA. LenzABA runs the clinic workflows. Breathr helps with communication, intake, reminders, and operational visibility on top.

HIPAA-compliant workflowsPlatform-connected contextOps-friendly visibility
Live threads
Parent update
Schedule change + home note
Intake lead
Insurance verified, callback due
Ops briefing
3 staffing alerts ready
Review before send
Parent communication draft

Breathr drafts from platform context. Staff still review the outbound message.

Channel
SMS + email
Draft

Hi Jordan, Milo's Tuesday session moved to 4:00 PM because your BCBA overlap was extended. Wednesday and Friday stay unchanged.

Breathr pulled the change from Scheduling and included the BCBA handoff note from today's session summary.

Operator briefing
2 same-day callouts
1 intake callback due by 2 PM
4 parent messages awaiting review
Connected context
Sessions activity synced
Docs review state available
Scheduling changes pulled in

How Breathr fits

Not another core module. A connected assistant layer.

Use Breathr when the clinic needs help keeping up with communication, intake, and daily coordination. It reduces the admin drag around the workflows already running in LenzABA, but it stays packaged separately from the core module stack.

Breathr handles the messages, nudges, and briefings that usually end up scattered across inboxes, phone calls, and Slack threads.

The point is not to create one more destination. The point is to help the clinic keep up with what the platform already knows.

How it works

From connected to useful in four steps.

Breathr reads the LenzABA platform and turns operational context into communication your clinic would otherwise handle manually.

1

Connect Breathr to your LenzABA workspace

Breathr plugs into your existing LenzABA environment. It reads the context from Sessions, Docs, and Scheduling so it knows what is happening in the clinic.

2

Configure the channels your clinic uses

Set up parent messaging, intake forms, daily operator briefings, and admin reminders. Pick the channels that match how your clinic already communicates.

  • Web, email, SMS, and voice channels
  • Intake qualification forms with auto-routing
  • Morning briefing templates for operators
3

Breathr handles the coordination

The assistant reads platform context and drafts communication. Parent updates reference real session data. Intake calls get qualified before they reach your clinical team.

4

Staff gets time back. Families stay informed.

The clinic spends less time on admin messaging and more time on clinical work. Families hear from the clinic consistently, not just when someone remembers.

What it helps with

Where the assistant layer earns its keep.

Breathr is best when the clinic has recurring communication and coordination work that keeps pulling staff out of higher-value roles.

Parent Communication

Handle reminders, updates, and outreach across web, voice, email, and messaging without pulling staff out of clinical work.

Intake Coordination

Capture leads, qualify families, and keep intake moving with less manual back and forth from the clinic team.

Operational Briefings

Surface the changes that matter each day so owners and operators can see the situation without chasing three different tools.

Admin Assistant Layer

Use Breathr on top of LenzABA when the clinic needs help with reminders, coordination, and lightweight ops support.

What sets Breathr apart

Not a chatbot. Not a portal. A clinical communication layer.

Sends from your channels, not a new inbox.

Parent messages, intake responses, and operator briefings go out through the email, SMS, and web channels families and staff already use. No new app to install, no new login for families to create.

Reads the platform. Not a blank prompt.

When Breathr drafts a parent update, it references real session data from that week. When it sends a morning briefing, it pulls from actual coverage changes and open alerts. The context comes from the platform, not from someone typing instructions.

Clinician-approved before anything goes out.

Every outbound message passes through a review step. The assistant drafts based on platform context, the clinician reviews and edits, then it sends. The clinic stays in control of what families see and when they see it.

See it in context

How Breathr looks inside the clinic workflow.

Live threads
Parent update
Schedule change + home note
Intake lead
Insurance verified, callback due
Ops briefing
3 staffing alerts ready
Review before send
Parent communication draft

Breathr drafts from platform context. Staff still review the outbound message.

Channel
SMS + email
Draft

Hi Jordan, Milo's Tuesday session moved to 4:00 PM because your BCBA overlap was extended. Wednesday and Friday stay unchanged.

Breathr pulled the change from Scheduling and included the BCBA handoff note from today's session summary.

Operator briefing
2 same-day callouts
1 intake callback due by 2 PM
4 parent messages awaiting review
Connected context
Sessions activity synced
Docs review state available
Scheduling changes pulled in

Common questions

Questions about how Breathr fits in?

See whether Breathr belongs in your clinic stack.

We can walk through where the communication and coordination drag is showing up, then decide whether Breathr should sit alongside the LenzABA platform as a separate add-on for your team.