Creative uses for automations

Hi ​@brittany larson!

As a consulting team at Bonterra, we get to peek under the hood of a lot of programs. We see that some of the strongest programs treat automations as multi-channel micro-programs, email/SMS when it helps, plus Activist Codes, list moves, tasks, and staff routing that actually change outcomes. After polling my team, here’s a few that came to mind that they have seen in the recent past. It sounds like you’re very much on a good path for thinking about supporter journeys that lean on highlighting people’s accomplishments. 

1) Top Action Taker → Higher Bar (what you’re planning)

• Trigger: Top 5% actions in last 60–90 days or ≥4 actions/30 days
• Messages: Email recognition + optional SMS nudge with 3–4 “next step” buttons (organize, testify/LTE, host, start monthly)
• Back-end: Apply Top Advocate code; if click w/o conversion in 48h → auto create staff task; suppress other drips for 7 days

2) Petition → Sustainer Bridge

• Trigger: ≥2 actions in 30 days, never donated
• Messages: Email low-bar monthly ask ($5–$10)
• Back-end: Apply Philanthropy Prospect; create “Sustainer Outreach” task if no conversion in 72h

3) Event Momentum Engine

• Trigger: RSVP → attended/no-show
• Messages: Attended: same-day thank-you email + “one next thing”; No-show: SMS with recording + low-bar action
• Back-end: Apply Event VIP for priority guests; assign organizer/MGO debrief task; expire No-Show code after 14 days

4) Sustainer Save (non-email first)

• Trigger: Card expiring/failed
• Messages: SMS with secure updater link; fallback email if no update
• Back-end: Apply CC Update Needed; assign sustainer specialist task; escalate to MGO if ≥$25/mo after 5 days

5) Donor ↔ Advocate Crosswalk

• Trigger: Recent donor with zero actions (or vice versa)
• Messages: One-click action email/SMS for donors; soft monthly ask email for frequent advocates
• Back-end: Apply Policy Action Ready or Philanthropy Prospect Activist Code; move into the appropriate journey and exclude from the other for 7 days

6) Data Health + CX (to keep the machine humming)

• Trigger: Hard bounce, returned mail, or SMS opt-out/in
• Messages: Email to preference center or SMS confirm
• Back-end: Apply Needs Email/Address Update or Mobile Opt-In/Out; create verification task; auto-remove code on resolution

We use automations for a lot of tasks--especially for email outreach. We also have an automation set up to pull WealthEngine API data for new donors and apply activist codes if they have net worth above certain amounts. Development staff can then use CAL to pull lists of donors based on net worth.