Features
The AI Layer

Direct an agent across your whole system.

Ask in plain language and SoberLab's agent does the work — running workflows, finding what you need, and making updates across every module. Always within each user's permissions. Always in the audit trail.

Move Marcus T. to bed 4B and set his level of care to OutpatientRun
Who has a drug screen due this week?Start a discharge for room 12Draft this month's SPARS outcomes
SoberLab AgentPERMISSION-AWARE
DANA · HOUSE MANAGER
Move Marcus T. to bed 4B at Maple, set his level of care to Outpatient, and book an intake follow-up for Thursday.
AGENT · COMPLETED IN 4 STEPS · 3.2s
Found Marcus T. — currently Arsenal, bed 2ARESIDENTS
Reassigned to Maple · bed 4BCENSUS & BEDS
Level of care updated → OutpatientCLINICAL
Intake follow-up booked → Thu 2:00 pmSCHEDULING
All four changes written to the audit trail · consent checked before each
Three ways to direct it

One agent. Three kinds of work.

01 — RUN WORKFLOWS

Kick off a whole process

Admissions, discharges, step-downs — the agent works each step in order and pauses for staff wherever a signature or judgment call is required.

Discharge workflow · room 12
Final drug screen recorded
Balance settled & statement sent
Discharge summaryneeds your signature
02 — FIND INFORMATION

Ask your live data anything

No report to run, no filter to build. The agent reads across modules and answers instantly — respecting exactly what the person asking is allowed to see.

Who has a drug screen due this week?
6 residents are due before Friday:
Marcus T. · WedJ. Rivera · WedA. Cole · Thu+3 more
03 — MAKE UPDATES

Change the record, safely

Reassign a bed, update a level of care, reschedule a session. Every change shows you exactly what it did — and lands in the audit trail with your name on it.

Change preview · Marcus T.
BedArsenal 2AMaple 4B
Level of careResidentialOutpatient
ApplyDiscard
What it can reach

One agent, wired into every module.

Because SoberLab runs on one shared record, the agent isn't bolted on — it operates the same modules your staff do, under the same permissions.

Built with guardrails

It can only do what you can do.

The agent inherits the signed-in user's role and consents. It can't see a record they can't see, and it can't make a disclosure their permissions don't allow. Every action is logged, attributable, and reversible.

Scoped to the user's role & consents
Every action written to the audit trail
Previews & reversible changes, not silent edits
DISCLOSURE ATTEMPT · BLOCKED
"Send Marcus's attendance to his probation officer."
Stopped before disclosure

No current consent on file names criminal-justice disclosure. The agent can request one — it can't send without it.

42 CFR §2.35 · logged · no data left the record

Questions, answered.

Does the agent act on its own?

No. It responds to a person's request and pauses for approval on anything consequential — signatures, disclosures, discharges. You stay in the loop, with a preview before changes apply.

Can it see records a staff member can't?

Never. The agent runs as the signed-in user, inheriting their role and the resident consents in force. If a person can't open a record, neither can the agent on their behalf.

Is every action recorded?

Yes. Each step the agent takes is attributed to the requesting user and written to the same audit trail as manual actions — visible in Compliance, exportable for review.

Do we have to use it?

No. The agent is an accelerator, not a requirement. Every workflow it runs can be done by hand, and organizations can scope or disable it per role.

See the agent work.

Bring us a real task from your week. We'll show you the agent run it end to end — safely, in a live demo.