> For the complete documentation index, see [llms.txt](https://vendorspace.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vendorspace.gitbook.io/docs/communication/payment-reminders.md).

# Payment reminders

Nobody likes chasing down payments. Vendor Space lets you set up automated reminders so vendors get a friendly nudge without you having to send individual follow-ups.

***

## Creating a Reminder

1. Navigate to **Communication** in the sidebar.
2. Click the **Reminders** tab.
3. Click **New Reminder**.
4. Fill in the reminder details (see the table below).
5. Click **Save** to activate.

***

## Reminder Settings

| Field          | Description                                                                      |
| -------------- | -------------------------------------------------------------------------------- |
| **Type**       | Choose from: Payment Reminder, Onboarding Reminder, Document Reminder, or Custom |
| **Event**      | Select which event this reminder applies to                                      |
| **Recipients** | All unpaid vendors, specific vendors, or a filtered group                        |
| **Message**    | Write your reminder text (a default template is provided)                        |
| **Schedule**   | One-time on a specific date, or recurring at a set interval                      |

***

## Reminder Types

### Payment Reminder

Sent to vendors who have not yet completed their booth payment. The email includes a direct link to their payment page so they can pay immediately.

### Onboarding Reminder

Nudges vendors who have paid but have not completed their onboarding form. Useful for collecting setup requirements, insurance documents, and other pre-event details.

### Document Reminder

Targets vendors with outstanding documents -- contracts that need signing, permits that need uploading, or insurance certificates that are missing.

### Custom

A free-form reminder for anything else. Write your own subject and body, and send it to whichever vendors you choose.

***

## Scheduling Options

You have two ways to schedule reminders:

### One-Time

Pick a specific date and time. The reminder sends once and is marked as completed.

### Recurring

Set an interval (for example, every 3 days or every week). The reminder continues sending until the vendor completes the required action or you manually stop it.

> **Tip:** A good rhythm for payment reminders is to send the first one 7 days before the event, then follow up every 3 days. This gives vendors enough notice without feeling overly persistent.

***

## Managing Active Reminders

From the Reminders tab, you can see all your active and past reminders at a glance.

| Column         | What It Shows                    |
| -------------- | -------------------------------- |
| **Type**       | The reminder category            |
| **Event**      | Which event it belongs to        |
| **Recipients** | How many vendors will receive it |
| **Schedule**   | When it sends next               |
| **Status**     | Active, Paused, or Completed     |

* **Pause** a reminder to temporarily stop it without deleting it.
* **Edit** a reminder to change the message, recipients, or schedule.
* **Delete** a reminder to remove it entirely.

> **Tip:** Check the reminder status after your event date passes. Any reminders tied to past events should be paused or deleted to keep your communication clean.


---

# 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://vendorspace.gitbook.io/docs/communication/payment-reminders.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.