> For the complete documentation index, see [llms.txt](https://guide.mymodone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.mymodone.com/common-features/call-to-action.md).

# Call to Action

A call to action (CTA) indicates an action that the recipient must take for active content to be set to confirmed status for that recipient.  A CTA can be set for Alerts and Scheduled Content.

**Setting a Call to Action**

1. Choose the (CTA) Type. There are two types of CTAs: 1) Confirmation Question (yes/no question) and 2) Signature (captures the recipient's signature as confirmation that they completed the CTA)
2. Add a brief (up to 100 characters) question or statement about what responding to the CTA means. For example, a CTA Type of Confirmation Question might include the question, "Did you review and understand this content?". A CTA type of Signature might include the question, "By signing, I confirm that I reviewed and understood this content".
3. Set the CTA Begin Date. This date most often coincides with the scheduled/send date. For timing purposes, the CTA Begin date begins at midnight of the chosen date.
4. Set the CTA Due Date (sometimes referred to as the Expiration Date). The date by which the recipient must respond to the CTA. For timing purposes, the due date is at 11:59 pm of the chosen date.

The date range in the calendar view (the horizontal bar) begins with the scheduled date and ends with the CTA Due Date.


---

# 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://guide.mymodone.com/common-features/call-to-action.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.