> For the complete documentation index, see [llms.txt](https://docs.anedot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.anedot.com/action-pages/page-builder/future-pledges.md).

# Future Pledges

Let donors schedule a future gift from your Action Page. Set a Future pledge date and message in Finance > Giving of the Page Builder.

A **future pledge** lets a donor schedule a gift for a later date from your Action Page. You set it up in the Page Builder under **Finance > Giving > Future pledge**. This article covers how to turn it on, change the date, and take it off the page.

{% hint style="info" %}
Future pledges are available on Donation Pages. On Event Pages, Future pledge shows only when **Accept donations for all ticket purchase types** is on.
{% endhint %}

## Add a Future Pledge

To add a future pledge to your page:

1. Go to **Action Pages > Pages**.
2. Hover over the page you want to edit.
3. Click **⋮ > Edit**.
4. Select **Finance > Giving**.
5. Under **Future pledge**, enter a **Future pledge date**.
6. Enter a **Future pledge message** to invite donors to schedule their gift.
7. Click **Save**.

Donors can schedule their gift for that date on the public page.

## Change or Remove the Date

The hint under **Future pledge date** tells you the current state:

* **Date ahead:** Donors can schedule their gift for this date.
* **Date passed:** The date no longer schedules a gift. Pick a new date or clear it.
* **No date:** The future pledge doesn't show on the page.

To take the future pledge off your page, click **Clear date**, then click **Save**.

## Related Articles

* [Giving Amounts and Frequencies](/action-pages/page-builder/giving-amounts-and-frequencies.md)
* [Page Builder Overview](/action-pages/page-builder.md)


---

# 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.anedot.com/action-pages/page-builder/future-pledges.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.