Engage

---
name: engage
description: Manage participant relationships - thank-yous, updates, re-engagement, and advocacy asks
allowed-tools: Read, Write
argument-hint: "[optional: what you want to do - thank donors, post update, re-engage, etc.]"
---

Manage participant engagement for your campaign: $ARGUMENTS

Build lasting participant relationships across all campaign types. Engaged participants share, re-engage, and recruit, giving organizers a massive competitive advantage.

## The Participant Lifecycle

```
FIRST ACTION -> THANK YOU -> UPDATE -> RE-ENGAGE -> ADVOCATE
(donation/registration/payment)  (<1 hr)  (regular)  (milestone)  (ongoing)
```

## Workflow

1. **Identify the Action**: Use the campaign-context skill to establish campaign type, then determine what the organizer wants to do:
   - **Thank participants** (donors, attendees, members who paid)
   - **Post a campaign update** (milestone, story update, impact report)
   - **Re-engage lapsed participants** (bring back dormant donors, reach non-attendees, follow up with unpaid members)
   - **Send payment reminders** (group campaigns: cadence-based collection messages)
   - **Ask for shares** (turn participants into advocates)

2. **Gather What's Needed**: Ask the organizer for the information you need:
   - For thank-yous: How many people? Do you have names and amounts? What channel (email, text, social, in-campaign post)?
   - For updates: What milestone or news? What's the current progress?
   - For re-engagement: How long since last activity? What's the situation now?
   - For reminders: How many people in the group? How many have paid? What's the deadline?
   - For share asks: Who are you asking (donors, attendees, or members)?

3. **Generate Messages**: Follow the guidance below for each action type.

4. **Multi-Channel Versions**: For each message, provide versions appropriate for the channel(s) the organizer is using (email, text/WhatsApp, DM, social post, in-campaign update).

5. **Save the Engagement Package**: Write all generated messages to `[campaign-title]-engagement-[date].md` in the workspace, organized by recipient or action type.

---

## Thank-You Messages

### Timing Rules
- **Within 1 hour**: Personalized thank-you (highest impact window)
- **Within 24 hours**: Public acknowledgment (social post or campaign update)
- **Within 1 week**: Impact update showing how their support is being put to work

### Personalization Tiers (Fundraisers)

| Tier | Range | Style | Length |
|------|-------|-------|--------|
| Micro | $1-$25 | Warm, "every dollar matters" | 2-3 sentences |
| Standard | $26-$100 | Personal, specific impact of their amount | 3-4 sentences |
| Major | $101-$500 | Deeply personal, name how their gift moves the needle | 4-5 sentences |
| Anchor | $500+ | Full personal letter, reference relationship if known | Full letter |

### Equivalents for Other Types
- **Event attendees**: Thank for registering. Match enthusiasm to ticket price paid.
- **Members who paid**: Thank for paying on time, frame as contributing to a shared goal.

### Thank-You Framework (All Types)
1. **Name them**: First name always. Never "Dear Supporter."
2. **Acknowledge the action**: "Your donation of $X..." / "Your registration for [Event]..." / "Your payment of $X..."
3. **Show impact**: Tie their specific action to a tangible outcome
4. **Humanize**: A brief update, emotional moment, or what happens next
5. **Extend**: Fundraisers: ask for a share (optional). Events: ask them to bring a friend. Groups: celebrate they're in.

### Public Gratitude Posts
- Name participants by first name (with permission) or anonymously ("A generous friend just donated $50!")
- Show progress bar movement: "Thanks to 12 amazing people, we're now at 35%!"
- Keep it authentic. Performative gratitude backfires.

See `references/thank-you-templates.md` for full templates by tier, relationship type, and channel.

---

## Campaign Updates

### Update Cadence by Type

**Fundraiser milestones:**

| Milestone | Update type | Channel |
|-----------|------------|---------|
| 25% of goal | Progress + renewed ask | Campaign page + social |
| 50% of goal | Halfway + impact story | Campaign page + email |
| 75% of goal | "So close" + share request | All channels |
| Goal reached | Victory + deep gratitude | All channels + personal messages |
| Post-campaign | Impact report | Email + campaign page |

**Event milestones:**

| Milestone | Update type | Channel |
|-----------|------------|---------|
| 25% capacity | Social proof post | Social + email |
| Early bird closing | Urgency + last chance | All channels |
| 50% sold | Momentum post | Social + email |
| Last 20 tickets | Scarcity messaging | All channels |
| 1 week out | Attendee logistics | Email to attendees |
| Post-event | Thank you + highlights | Email + social |

**Group milestones:**

| Milestone | Update type | Channel |
|-----------|------------|---------|
| 25% paid | Progress + encourage | Group channel |
| 50% paid | "Over halfway!" | Group channel |
| 75% paid | Urgency + gratitude | Group channel |
| Deadline approaching | Final nudge | Group channel + private to unpaid |
| Goal reached | Celebration + what happens next | Group channel |

### Update Content Framework
1. **Progress metric**: Current status (amount raised, tickets sold, payments received, % of goal)
2. **Emotional beat**: A new detail, quote, behind-the-scenes moment
3. **Fund/resource usage**: How support has or will be allocated
4. **Forward look**: What happens next, what's still needed
5. **CTA**: Donate/buy/pay more, share, or celebrate

See `references/update-templates.md` for full templates by milestone and situation type.

---

## Re-Engagement Strategies

### Re-engagement Triggers
- Fundraiser stalled for 3+ days with no new donations
- Event registration velocity dropped below 5%/week
- Group past midpoint with less than 50% paid
- Milestone approaching (within 10% of 25/50/75/100%)
- New development (court date, event lineup reveal, booking update)

### Re-engagement Message Types
1. **Milestone nudge**: "We're just $200 away from 50%. Can you help us get there?"
2. **Story update**: "Here's what's happened since you registered / donated..."
3. **Share request**: "Would you share with one friend? Here's a pre-written post."
4. **Urgency trigger**: "The court date is in 5 days / The event is in 2 weeks / Deadline is Friday"
5. **Gratitude loop**: "Because of you, [person/group] was able to [outcome]"

### Lapsed-Donor Cadence (Fundraisers)
- **Day 3-5 after stall**: Story update to past donors with a share request (not a re-ask for money)
- **Day 7-10**: Milestone nudge if close to a threshold, or a new development update
- **Day 14+**: Gentle ask for a share or co-organizer invitation. Maximum 2-3 re-engagement touches.

### Event Re-Engagement
- **Opened-but-didn't-register**: Follow up with urgency (early bird ending, limited spots)
- **Registered attendees**: Ask them to bring a friend when spots are still available

---

## Payment Reminders (Group Campaigns)

Follow the "Friendly Collector" principles for all group payment follow-ups:

- **Lead with gratitude and progress**: "We're at 70%!" before "Please pay"
- **Never single out unpaid members publicly**: Private follow-ups only
- **Celebrate milestones**: Public recognition drives the remaining group to act
- **Frame reminders as progress**, never accusations
- **Maximum 5-6 messages** to the full group over the collection period

### Recommended Cadence

| Message | Timing | Focus |
|---------|--------|-------|
| 1 - Launch | Day 0 | Share the link, amount, deadline, and purpose |
| 2 - Progress | Day 3 | Celebrate early payers, share % complete |
| 3 - Midpoint | Day 7 or halfway | "Over halfway!" momentum push |
| 4 - Urgency | 3 days before deadline | Real constraint reason, remaining count |
| 5 - Deadline | Deadline day | Final push, specific number still needed |
| 6 - Straggler | Post-deadline | Private 1:1 only, friendly and flexible |

See `references/reminder-templates.md` for full templates by channel (text, email, Slack) and celebration messages.

---

## Participant-to-Advocate Conversion

### Conversion Tactics
1. **Post-action share prompt**: Immediately after donating/registering/paying, suggest pre-written share content
2. **Personalized share content**: Generate custom posts they can copy-paste
3. **Co-organizer invitation**: Top donors and enthusiastic attendees make great co-organizers (3x success rate)
4. **Challenges**: "If 5 friends register by Friday, we'll reveal the surprise guest"
5. **Thank-and-tag**: Public thank-yous that tag the participant (with permission)

---

## Standalone vs. MCP-connected mode

This skill works in either mode. See `campaign-context` for the full operating-modes overview.

- **Standalone (default):** ask the organizer for participant names, amounts, and payment status, then generate messages they can copy into email, text, or the campaign page directly.
- **MCP-connected:** pull live participant data and persist generated thank-yous / updates back to the campaign so they show up in the organizer's dashboard.

If MCP tools aren't available in the session, use the standalone flow without comment. Do not prompt the organizer to authenticate.

## If the PayIt2 MCP server is connected

When MCP tools are available, use them to pull real participant data instead of asking the organizer. This makes messages more accurate and saves the organizer time.

**Data gathering (use before generating messages):**
- Call `search_participants(query, campaignId?)` to look up specific participants by name or email, or to list contributors for a campaign (pass an empty/broad query plus the `campaignId` for batch thank-yous).
- Call `get_participant_insights(campaignId)` for top contributors, averages, and engagement metrics.
- Call `get_payment_summary(campaignId)` for current totals, average payment size, and payout status (powers updates and re-engagement messaging).
- Call `get_campaign_health(campaignId)` for pace and momentum, useful for milestone-driven re-engagement triggers.

**Persisting generated content:**
- Call `save_thank_you(campaignId, content)` to record a generated thank-you against the campaign. The organizer still sends it through their preferred channel (email, text, social).
- Call `save_update_post(campaignId, content)` to publish a campaign update directly to the campaign feed — this is visible to all existing participants.

These MCP tools are optional enhancements. The skill generates the same quality content in standalone mode by asking the organizer for participant details directly.