> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wegive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Create Your Default Triggered Messages 

> WeGive Help Center article: Create Your Default Triggered Messages 

Triggered messages send automatically when a specific event happens in your account — like a donation succeeding or a recurring gift being created. Setting up a baseline set of these before you go live makes sure every supporter gets a timely, on-brand confirmation without any manual work on your end.

This article walks you through creating the default triggered messages we recommend for launch.

## What are triggered messages?

A triggered message is an email (or SMS) that fires when its trigger event occurs. Each trigger can have one or more messages attached to it, and a message stays inactive until you set its status to **Live**.

Triggered messages should typically be set as **transactional**. Transactional messages are tied to a specific action a donor took (like making a gift or updating a payment method), so donors cannot opt out of them — which ensures critical confirmations and account notices always reach them. Reserve opt-out (marketing) messaging for newsletters, appeals, and other non-essential communications.

## The recommended baseline before going live

At minimum, we recommend setting up the following triggered messages so your supporters are covered for the most common giving scenarios:

| Trigger | Why you need it |
| - | - |
| **Payment Success** | Sends a receipt/confirmation as soon as a gift goes through. This is the most important one to have live. |
| **Payment Failure** | Lets a donor know their payment didn't process so they can try again. |
| **Payment Processing** | Reassures donors that their gift is being processed (useful for slower payment methods like ACH/bank). |
| **Recurring Donation Created** | Confirms a new recurring gift and sets expectations for future installments. |
| **Tribute Made** | Acknowledges a gift made in honor or memory of someone. |

Once these are live, you can layer in additional triggers (recurring installment failures, pledge reminders, P2P, event registration, and more) as needed.

## Before you start

Make sure you have:

* A verified send-from email address. Email triggered messages require you to choose an address to send from, so confirm at least one is set up.
* Your branding and key message copy ready (logo, colors, signature, tone).

## How to create a default triggered message

You'll repeat these steps for each trigger in the recommended list above.

1. **Open the Triggers section.** From the Dashboard v2 left-hand navigation, go to **Triggers** (under your messaging/automation area).
2. **Select a trigger.** Click into the trigger you want to set up first — for example, **Payment Success**. This opens the trigger's detail page, which shows the trigger's existing messages (if any) and a button to add a new one.
3. **Create the message.** Click **Create Message**. The trigger is automatically pre-selected for you, so the new message will fire on this event.
4. **Choose your delivery method.** Select **Email** (most common for receipts and confirmations) or **SMS**.
5. **Select your send-from email address.** For email messages, you must choose which verified address the message sends from. The message can't go live without this.
6. **Write your content.**

   * **Subject line** — clear and recognizable (e.g., "Thank you for your gift!").
   * **Preheader** — the preview text shown in the inbox (100 character limit).
   * **Body** — your message copy. Use personalization variables (such as donor first name, gift amount, and designation) so each message feels tailored.
7. **Set your audience or filters (optional).** Most default triggered messages should go to everyone who hits the trigger, so you can leave the filters open. Add filters only if you want to narrow who receives the message.
8. **Preview the message.** Use the preview to confirm the layout, copy, and variables render correctly before activating.
9. **Set the status to Live.** A triggered message only sends when its status is **Live**. Save it as a **Draft** if you're not ready, then come back and set it to **Live** when you want it to start firing.
10. **Repeat for the remaining triggers** in the recommended list until all of your default messages are live.

## Tips

* **Start with Payment Success.** If you only get one live before launch, make it this one — every successful donor should receive a confirmation.
* **Keep them transactional.** Because these messages confirm donor actions and account activity, set them as transactional so donors can't opt out and always receive them.
* **Use personalization variables** rather than generic copy so messages feel personal at scale.
* **Send yourself a test** by previewing and, where possible, running a small test transaction to confirm the message fires as expected.
* **Draft vs. Live:** drafts never send. Double-check the status reads **Live** for anything you intend to be active at launch.

## After launch

Once your baseline is live, consider adding triggered messages for:

* Recurring Installment Failed (#1–#4) and Recurring Donation Activated
* Payment Method Expiring Soon — proactively reminds recurring donors to update their card or bank details before it expires, preventing failed installments and lapsed gifts.
* Pledge Created, Due, and Missed reminders
* Peer-to-peer (P2P Created, Goal Met, Donation Notification)
* Event Registration Success / Status Updated
* Donor Profile Created and other engagement triggers

***

*Need help? Reach out to the WeGive support team and we'll walk through it with you.*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.