Patient Scheduling and Outreach

End-to-end patient scheduling and outbound outreach workflow, from clinical data loading through interaction completion and policy-gated external updates.

This guide walks through a common healthcare workflow: an AI agent handles appointment scheduling and outbound patient outreach across voice and text channels, from data ingestion through interaction completion and configured external updates.

The Workflow

A health system needs to contact patients who are due for follow-up appointments. Today, care coordinators manually review lists, make calls, navigate scheduling systems, and document outcomes. The process is time-consuming, and many patients never get contacted.

With Amigo, teams can automate selected parts of this workflow while keeping clinical standards, consent, external-system confirmation, and exception handling explicit.

Step-by-Step Flow

1. Connector Runner Loads Patient Data

A configured connector can ingest supported patient data from an EHR or another source system. A separate query, trigger, or customer workflow identifies patients who are due for follow-up based on criteria such as time since last visit, care-plan milestones, or provider orders.

An example workflow may ingest or retrieve:

• Demographics and contact preferences
• Relevant clinical context (reason for follow-up, last visit summary)
• Scheduling constraints (provider availability, location preferences)
• Prior interaction history with the platform

Source records must carry a stable patient association or be reconciled through a supported customer workflow. The active pipeline does not create new cross-source same_as merges, so do not rely on automatic identity matching across unrelated systems.

2. Outbound Dispatch Initiates Contact

An explicit workflow can start an outbound SMS or iMessage conversation, place a direct voice call, or create a scheduled outbound voice task. Scheduled voice tasks support a business-hours window, timezone, priority, attempt limit, and retry backoff. The platform does not automatically choose a channel or fall back from an unanswered call to SMS or voicemail; configure those decisions in a Context Graph, trigger, or external workflow.

3. Agent Greets the Patient

When the patient answers a call or receives the first text message, the agent introduces itself and states the purpose of the interaction. If identity resolution and authorized context are available, the greeting can use that context without disclosing unverified identity information.

For example, the agent might say: "Hello, this is the follow-up team at City Medical Center. I am calling because Dr. Patel asked us to check in with you after your visit last week and help you get your next appointment scheduled."

The agent version, channel configuration, and authored guidance shape tone, pacing, and vocabulary. Do not infer communication needs from age alone; use explicit preferences, accessibility needs, and tested workflow guidance.

4. Agent Reads Context from the World Model

During the conversation, authorized tools can retrieve relevant projected information. Projection and tool latency vary, so the workflow must handle missing or stale context:

• Appointment context: What type of follow-up is needed, how soon, and with which provider
• Patient history: Prior no-shows, scheduling preferences, transportation barriers
• Clinical notes: Any instructions from the care team about urgency or special requirements

This context can support a more relevant conversation. If the patient says "I had trouble getting there last time," an authored workflow can consult current transportation options or record the new barrier rather than assume an earlier observation is still correct.

5. Agent Uses a Scheduling Integration

Once the patient agrees to schedule, an eligible scheduling tool can query current availability from the configured integration. The agent can present returned options and apply supported filters such as provider, location, appointment type, or time window. If no option satisfies the request, it should explain the returned alternatives or use the authored fallback rather than invent availability.

The workflow can incorporate scheduling constraints such as:

• Multiple providers or locations
• Insurance verification requirements
• Pre-appointment instructions (fasting, medication holds)
• Follow-up reminders and confirmation preferences

When the patient selects a slot, the agent requests the booking through the configured scheduling tool and confirms it only when the tool result supports that claim.

6. Outcomes and External Updates

During or after the interaction, supported tools can record structured outcome events in the world model. Depending on the tool and destination policy, eligible payloads can be delivered to a configured scheduling or clinical system. Outcome data may include:

• Interaction outcome (scheduled, declined, no answer, callback requested)
• Appointment details if scheduled
• Any patient concerns raised during the conversation
• Escalation notes if the patient reported symptoms or issues requiring clinical attention

Recording an outcome event does not itself prove that an external system accepted it. Connector delivery reports its own result, and care coordinators can use destination records or supported read-back evidence when confirmation matters.

Handling Edge Cases

The agent and Context Graph should define boundaries for situations that require human involvement:

• Patient reports new symptoms: The workflow should prohibit unsupported clinical advice, record the concern when permitted, and use the authored care-team escalation path.
• Patient requests a provider change: The agent can offer available alternatives but escalates complex situations (such as insurance or referral issues) to a coordinator.
• Patient expresses distress or confusion: The agent adjusts its approach and, if needed, offers to connect the patient with a live staff member.
• Language barriers: The workflow uses the configured language capability and an authored fallback or transfer path when the interaction cannot be supported safely.

What This Looks Like in Production

At scale, this pattern can increase routine outreach capacity when channel delivery, scheduling integrations, and exception handling perform as expected. Care coordinators can then focus on interactions that need complex coordination or clinical judgment, while retaining a fallback for automation failures.

Teams can define metrics over recorded outcomes, such as scheduling rates and escalation frequency. No-show comparison requires a reliable join to later appointment outcomes from the authoritative scheduling system. Use equivalent definitions and populations when comparing simulation and production, and investigate modality or evidence differences before drawing conclusions.