> For the complete documentation index, see [llms.txt](https://help.donary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.donary.com/overview/lists/donors/donor-card/add-a-reminder.md).

# Add a Reminder

A **reminder** can be used to follow up with a donor for a specific purpose, such as a pending pledge, a declined credit card or a planned outreach. It helps ensure timely communication and keeps important follow-ups from being overlooked, allowing you to manage donor interactions in an organized and consistent way.

## To add a reminder:

Click the [**Actions** ](/overview/lists/donors/donor-card.md#actions)button in the top-right corner of the donor card.

<figure><img src="https://1544041479-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSoguDpndtaX2tYuML2Gi%2Fuploads%2FicWf9NskOwiFKuyvKZ1q%2Fcreate%20button.png?alt=media&amp;token=c622384a-2b4d-407a-ace9-00418df9cf4f" alt=""><figcaption></figcaption></figure>

1. Add a **Title** to the reminder (e.g., “Call @ declined Credit Card”).
2. Assign the reminder to a user using the **Assignee** field.&#x20;

   The assigned user will see the reminder in their **Reminders** tab and can be notified via text or email, ensuring they stay informed and take action on it.&#x20;
3. The reminder will automatically be linked to the donor for whom it is being created.
4. Optionally, link the reminder to a specific payment or pledge.
5. Set the **Date** for the reminder to trigger.
6. Choose the **Occurrence** in the **repeat** field (e.g., daily, weekly etc.).&#x20;

   A new reminder is created each time according to the schedule, even if the previous reminder hasn’t been completed.
7. Select whether to receive the notification via **Text** or **Email**.
8. Click **Save** to create the reminder.

{% hint style="info" %}
**PLEASE NOTE**:&#x20;

* The reminder will be visible **only** to the designated assignee.
* Reminders are for **internal** use only and do not notify the donor.
  {% endhint %}

The reminder will now appear in the **Reminders** tab within the donor card, where it can be easily viewed and managed.

<figure><img src="https://1544041479-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSoguDpndtaX2tYuML2Gi%2Fuploads%2F3VL42anxTCl3pBgbW0N1%2Freminder%20donor%20card.png?alt=media&amp;token=1fea6f9e-79bc-4f0b-a751-381c8b3793e3" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
If a reminder is linked to a specific payment or pledge, it will appear in the corresponding payment or pledge card.
{% endhint %}

## To manage a Reminder:

You can easily manage and update your reminders by following these steps:

* Click the **small arrow** on the far right of the reminder entry.
* A panel will open on the right side of the screen, showing the reminder's details.
* **Review** all reminder details.
* **Edit** the reminder as needed.
* **Update** the assignee, adjust the time or occurrence, and add a note or comment for additional context.
* **Delete** the reminder using the trash icon at the top of the window.
* To stop a reminder from recurring, select **End Recurring**.&#x20;
* Mark the reminder **Complete** once the issue is resolved and the reminder is no longer needed.&#x20;

{% embed url="<https://drive.google.com/file/d/14MoJ_D97LSiYTYPNy7adPMRDvDqAgeMV/view?usp=sharing>" %}
Add and manage a reminder in a donors card
{% endembed %}

{% hint style="success" %}
Reminders can also be managed in the **Notifications** category, under the **Reminders** tab.
{% endhint %}


---

# 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://help.donary.com/overview/lists/donors/donor-card/add-a-reminder.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.