> For the complete documentation index, see [llms.txt](https://answeringservicecare.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://answeringservicecare.com/docs/api-reference/user-portal-apis/to-dos.md).

# To Dos

The **To Dos** API schedules work for Answering Service Care to execute on your behalf, outbound calls, SMS messages, recurring text campaigns, and transactional emails. Once created, a To Do is durable and owned by Answering Service Care until it runs.

#### What you can do

* **List** every To Do for the authenticated user, filtered by date range and page size.
* **Create** a To Do with `delivery_type` (`sms`, `email`, or `call`). The body is flat (no `to_do` wrapper) and carries `account_number`, `contact`, `message_text`, and a `schedule`.
* Use the **variant endpoints**, `/ai-call`, `/sms`, `/sms/recurring`, and `/email`, to skip channel-specific boilerplate.

#### Scheduling

The `schedule` object accepts `rule` (`immediately`, `today`, or `recurring`), `frequency` (`daily`, `weekly`, `monthly`, `yearly`), `times` (one or more `HH:MM AM/PM` strings), and optional `interval` and `days`.

#### Per-channel fields

* **SMS / call**: `contact` is a phone number.
* **Email**: `contact` is an email address; also supply `sender_name`, `from_email`, and `subject`.
* **Call**: additionally supply `instructions` describing what the AI agent should say.

#### Common use cases

* Automating appointment reminders from an external scheduler.
* Triggering outbound calls when a high-priority lead hits your CRM.
* Running a weekly check-in SMS cadence for enrolled customers.
* Sending follow-up emails after a support interaction closes.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://answeringservicecare.com/docs/api-reference/user-portal-apis/to-dos.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.