> 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/re-engagement-campaigns.md).

# Re-engagement campaigns

Bringing back vendors who participated in your past events is one of the easiest ways to fill your roster. Re-engagement campaigns let you invite previous vendors to sign up for an upcoming event with just a few clicks.

***

## How It Works

A re-engagement campaign pulls the vendor list from a past event and sends each vendor a personalized invitation to apply or register for a new event. Vendors receive an email with your custom message and a direct link to get started.

***

## Creating a Campaign

1. Navigate to **Communication** in the sidebar.
2. Click the **Campaigns** tab.
3. Click **New Campaign**.
4. Configure the campaign using the settings below.
5. Preview the email to make sure everything looks right.
6. Choose to **Send Now** or **Schedule** for a future date.

***

## Campaign Settings

| Field             | Description                                                    |
| ----------------- | -------------------------------------------------------------- |
| **Campaign Name** | An internal label for your reference (vendors do not see this) |
| **Source Event**  | The past event whose vendor list you want to invite back       |
| **Target Event**  | The upcoming event you are inviting them to                    |
| **Subject Line**  | The email subject vendors will see in their inbox              |
| **Message Body**  | Your personalized invitation message                           |
| **Send Time**     | Immediately or scheduled for a specific date and time          |

***

## Writing an Effective Invitation

Your message should feel personal and give vendors a reason to come back. Here are a few things to include:

* **Mention the past event by name** so they remember the connection.
* **Highlight what is new or improved** about the upcoming event (bigger venue, more foot traffic, extended hours).
* **Include a clear call to action** such as "Reserve your booth" or "Apply before spots fill up."
* **Set a deadline** if space is limited to create a sense of urgency.

> **Tip:** Campaigns with a personal touch get significantly better responses. Even a simple "We loved having you at \[Event Name]" makes a difference.

***

## Previewing Before You Send

Before sending your campaign, click the **Preview** button to see exactly what vendors will receive. The preview shows:

* The email subject line
* Your message body with formatting
* The call-to-action button and where it links
* How the email looks on desktop and mobile

Take a moment to review the preview carefully. Once a campaign is sent, it cannot be recalled.

***

## Tracking Campaign Performance

After your campaign goes out, the Campaigns tab shows delivery stats for each campaign:

| Metric         | What It Means                                             |
| -------------- | --------------------------------------------------------- |
| **Sent**       | Total number of emails delivered                          |
| **Opened**     | How many vendors opened the email                         |
| **Clicked**    | How many vendors clicked the call-to-action link          |
| **Registered** | How many vendors completed registration for the new event |

Use these numbers to refine your messaging for future campaigns.

***

## Best Practices

* **Send campaigns 4 to 6 weeks before the event** to give vendors enough lead time to plan.
* **Segment your audience** if you have different booth types. A food vendor and a craft vendor may respond to different messaging.
* **Follow up** with a second campaign to vendors who did not open the first one, using a different subject line.
* **Keep it short.** Vendors are busy. Get to the point quickly and make it easy for them to take action.


---

# 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/re-engagement-campaigns.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.