PATIENT RETENTION / AGENT 004

Recare Agent

Keep overdue patients from disappearing into a report.

BUILDConnected build
CONTROLControlled PHI access
THE JOB

Every eligible overdue patient has a next action, an owner, or a documented stop reason.

Runs overdue reports, applies practice-approved segmentation, starts the correct outreach, and keeps every patient in a visible status.

AGENT ANATOMY

What it sees, decides, and does.

01 / TRIGGER

A patient becomes due or overdue according to the practice’s approved recare rules.

02 / CONTEXT
  • Recare due date
  • Patient status and communication preference
  • Prior outreach history
  • Practice-approved eligibility and exclusion rules
03 / DECISION
  • Eligible, excluded, already scheduled, or staff review
  • Appropriate outreach step
  • When to change channel
  • When to stop or escalate
04 / ACTION
  • Build the daily outreach queue
  • Send approved messages
  • Record replies and attempts
  • Create a staff booking task
HUMAN CONTROL

The agent knows when to stop.

These boundaries belong in the scope, tests, permissions, and operating log. They are not a disclaimer added after the build.

HUMAN GATE

A person reviews

  • Clinical questions
  • Requests to change recare interval
  • Patient complaints or dismissal issues
  • Unclear active or inactive status
EXCEPTION

The agent escalates

  • No valid contact method
  • Conflicting recare information
  • Patient under an active care restriction
  • Response requires clinical context
NEVER AUTONOMOUS

Outside the agent’s authority

  • Set a clinical recare interval
  • Present a reminder as a diagnosis
  • Ignore communication preferences
  • Remove a patient without an approved reason
DEFINED OUTCOME

Measure the job, not the novelty.

01Eligible patients contacted
02Appointments recovered
03Overdue list size and age
04Patients without a valid next action
AGENT OR PERSON?

The workflow may still need a virtual assistant.

AGENT

Use for the predictable path.

Monitoring, structured checks, approved messages, routing, logging, and repeated follow-up.

VIRTUAL ASSISTANT

Use for context and conversation.

Ambiguous responses, relationship work, judgment, persuasion, and exceptions that change from case to case.

HYBRID

Let the agent build the queue.

The agent handles the predictable path. A trained person receives a clean exception list with the context needed to finish the work.

EVIDENCE

Why this workflow matters.

Sources support the operating need and safety boundary. They do not prove that every practice should build this agent.

START WITH THE WORK

Bring us the recurring job.

We will map it, test the alternatives, and define what an agent should own only if an agent is the right answer.

Book a Free Consultation