> For the complete documentation index, see [llms.txt](https://docs.welkinhealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.welkinhealth.com/designer/automations/create-automated-appointment-reminders.md).

# Create Automated Appointment Reminders

Automating appointment reminders is a straightforward process, but requires two things before building:

* **Encounter type(s)** that will be associated with the reminders
* **Message template** to be sent as the reminder (including a reference to the Encounter date/time fields)

## Steps

Once you have the above ready, navigate to **Automations** from the vertical menu bar in Designer, and click **+New** in the upper right corner.

Enter or make the following selections:

* **Automation Title**
* **Automation Label** (optional)
* **Trigger Type:** Scheduled
* **Relative time** — set how far in advance the reminder should send (e.g., 1 hour before)
* **Encounter template** — choose a specific encounter type if the reminder applies to only one. If no encounter type is selected, the automation will trigger for all encounter types

In the **Conditions and Actions** area on the right:

* Add any conditional logic desired (optional)
* Select **SMS Patient**, **Chat Patient**, or **Email Patient** as the Action type, depending on the communication channel
* Choose the **Message Template** to send

Once configured, publish the automation.

***

More Questions? Contact <csm@welkinhealth.com> or your Implementation/CSM directly.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.welkinhealth.com/designer/automations/create-automated-appointment-reminders.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.