Five agents.
One controlled handoff.
Reception, recall, no-show recovery, collections and eligibility work as bounded routes inside one operating layer. Each route starts with a real practice signal, keeps context attached and makes the next state visible.
Agent control plane
Route signal to
Reception
Routine follow-up
Scheduled
- Trigger
- Front-desk demand
- Context
- Patient / Appointment / Consent
- Action
- Schedule reminders and routine follow-up.
- Review
- The team can see the handoff and take over.
- Next state
- Scheduled
Conceptual orchestration model
Five different jobs. One legible operating model.
Choose an agent to see the trigger, context, approved action, control point and next state together. The workflow changes; the governance model does not.
Reception
Front-desk demand
Schedule reminders and routine follow-up.
- Trigger
- Front-desk demand
- Context
- Patient · Appointment · Consent
- Action
- Schedule reminders and routine follow-up.
- Review
- The team can see the handoff and take over.
- Next state
- Scheduled
Shared state vocabulary
Automation stops where judgment begins.
Collections makes the control model explicit: cadence rules and text-to-pay can work the aging buckets, but escalation remains behind a human review gate. The trace keeps that decision visible.
Control is part of the route, not a footnote.
Signals, context and scheduled actions remain inspectable. The team can see when work is ready, when it is waiting and when a human decision is required.
Conceptual collections trace
Controlled escalation
Signal received
An aging balance enters the workflow.
Context ready
Patient, balance and aging bucket stay together.
Action scheduled
Cadence rules prepare text-to-pay follow-up.
Human review
Escalation waits for a visible team decision.
Continue
Return to the approved cadence.
Escalate
Proceed after human review.
The agents do not start from an empty prompt.
Strictly brings patients, appointments, claims and balances into one operating surface. The agent routes use that shared practice context instead of creating another disconnected queue.
Existing PMS context
Strictly context layer
One operating context.
The five agents work around the patient, appointment, claim and payment context already moving through the practice.
Coordinated routes
Put recurring work on a controlled route.
See your own schedule, claims and balances running inside Strictly in a 20-minute walkthrough.