> ## Documentation Index
> Fetch the complete documentation index at: https://docs.roserx.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflows

> Route patients to the right care with the Appointment Finder sub-agent, telehealth and in-person pathways, and intake questions.

Workflows let patient-facing agents go beyond answering questions — they can guide a patient to the right care. Configure an **Appointment Finder** sub-agent that activates mid-conversation, asks your intake questions, and routes the patient to a telehealth or in-person appointment pathway.

<Info>
  Workflows are configured per agent. Open your agent and select the **Workflows** tab. Workflows are designed for patient-facing agents such as Patient Navigator and Medication Navigator.
</Info>

## Sub-Agent

Sub-agents are specialized AI assistants that activate mid-conversation to handle a specific task. When triggered, the sub-agent takes over temporarily, collects the information it needs, and hands back a structured result — such as a care pathway decision — before returning control to the main agent.

Choose a sub-agent from the **Sub-agent** dropdown:

| Option                 | Behavior                                                                                  |
| ---------------------- | ----------------------------------------------------------------------------------------- |
| **None**               | No sub-agent runs; the agent handles all messages itself                                  |
| **Appointment Finder** | Activates when a patient asks to see a doctor, then guides them to the right care pathway |

When the Appointment Finder is selected, you can configure:

* **Triggers** — The Appointment Finder activates automatically when a patient uses one of the built-in trigger phrases (for example, asking to talk to a doctor). The trigger list is fixed and shown on the page for reference.
* **Introductory message** — The opening message the Appointment Finder sends before asking its first question.
* **Additional instructions** — An optional toggle to customize the Appointment Finder's behavior with extra instructions.

<Tip>
  You can also add a **Talk to a Doctor** button to your widget that launches the Appointment Finder directly. See [Creating a Widget](/guides/widgets/creating-a-widget).
</Tip>

## Care Workflows

Care Workflows define which care pathways are available to patients. The Appointment Finder only routes to the pathways you enable.

### Telehealth

Enable the Telehealth pathway to offer patients an online consultation. When a patient qualifies, the agent presents a consultation card with a booking link.

| Setting                  | Description                                                                                                                               |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **Booking URL**          | The link patients are sent to when they choose telehealth                                                                                 |
| **Eligibility criteria** | Plain-language rules the Appointment Finder uses to check whether a patient qualifies (e.g. "Has Medicare card", "No emergency symptoms") |
| **Title**                | The consultation card heading (e.g. "Online GP consultation")                                                                             |
| **Description**          | A short summary (e.g. "Speak with a doctor from home, same day")                                                                          |
| **Provider**             | The telehealth provider's name                                                                                                            |
| **Price**                | Displayed pricing (e.g. "From \$45")                                                                                                      |
| **Button label**         | The card's call-to-action text (e.g. "Book an appointment")                                                                               |

### In-Person Appointment

Enable the In-Person pathway to direct patients toward a face-to-face appointment. You can set a **preferred professional** (e.g. GP, cardiologist) that the agent recommends. A patient who mentions their regular doctor during intake is handled within the in-person pathway.

## Intake Questions

Intake Questions are what the Appointment Finder asks to determine the appropriate care pathway. Questions are asked **one at a time, in order** — add, edit, and reorder them from this section.

<Tip>
  Keep intake questions short and specific. Each answer helps the Appointment Finder decide between the telehealth and in-person pathways, so ask only what's needed to route the patient.
</Tip>

## Emergency

Configure the **emergency services phone number** shown to patients if they report a medical emergency during intake. If you don't set one, the agent uses your region's default — **000** for Australia or **911** for the United States.

<Warning>
  The Appointment Finder is a routing tool, not a triage service. If a patient describes emergency symptoms, the agent immediately directs them to emergency services rather than continuing the intake flow.
</Warning>

## Next steps

<CardGroup cols={2}>
  <Card title="Creating a Widget" icon="window" href="/guides/widgets/creating-a-widget">
    Add a Talk to a Doctor button to your widget that launches the Appointment Finder.
  </Card>

  <Card title="Guidance & Guardrails" icon="shield-check" href="/guides/agents/guidance-and-guardrails">
    Control how your agent handles patient queries and escalations.
  </Card>

  <Card title="Conversations" icon="messages" href="/guides/monitoring/conversations">
    Review how patients move through your care workflows in real conversations.
  </Card>

  <Card title="General Settings" icon="gear" href="/guides/agents/general-settings">
    Configure your agent's model, tone, and response length.
  </Card>
</CardGroup>
