> For the complete documentation index, see [llms.txt](https://support.pears.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pears.io/updates/community-events-2026/unique-confirmation-messages.md).

# Unique Confirmation Messages

As of **January 28, 2026**, community event confirmation messages can be customized for each registration type. Previously, all registrants received the same confirmation message regardless of their registration type.

## What Changed

### Previous Behavior

A single confirmation message was configured for the entire event. All registrants — attendees, sponsors, volunteers, and others — received the same message via email and on the registration summary page.

### Updated Behavior

You can now add a unique confirmation message for each registration type (e.g., Attendee, Sponsor, Volunteer). This is optional — if a registration type does not have a custom message, the overall event confirmation message is used as the default.

![Screenshot: The confirmation message editor showing options to customize messages per registration type](/files/M3icgHF2tm7CyccSrf0m)

{% hint style="info" %}
**TIP:** Use registration type-specific messages to include relevant details like sponsor benefits, volunteer instructions, or session-specific information that only applies to certain registrant groups.
{% endhint %}

## Related Documentation

* [Confirmations](/plan/community-events/confirmations.md) — Create confirmation messages using dynamic tokens
* [Registration Types](/plan/community-events/registration-types.md) — Configure registration types for events


---

# 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://support.pears.io/updates/community-events-2026/unique-confirmation-messages.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.