Back to features

Feature area

Communications

Sapling brings fundraising email, lists, subscribers, templates, merge fields, receipt language, event follow-up, and donor communication history closer to the donor record.

Why it matters

One connected place for this work.

Nonprofit communication is not just sending. It is knowing who should hear what, what they already received, what gift, event, receipt, list, or relationship it connects to, and what the team should do next. Sapling is built so communications can become part of the donor story instead of another disconnected campaign tool.

Communications preview

Messages should know the donor record they came from.

Sapling keeps email, lists, templates, receipts, events, and donor history close so outreach feels coordinated instead of rebuilt from scattered exports.

Campaign email

Appeals, newsletters, stewardship, and follow-up with donor context.

Lists and subscribers

Audience kinds, opt-outs, suppression, and list-unsubscribe handling.

Templates and merge fields

Reusable copy with personalization and fallback fields.

Receipts and notices

Receipt emails, cover copy, refund notices, and transaction language.

Campaign workbench

Demo audiences
Major donors128Spring cultivation noteDraft ready
Event attendees342Post-gala follow-upScheduled
Recurring donors89Monthly impact updateSent
Receipt queue37Gift acknowledgmentNeeds review

Campaign email belongs near the CRM

Appeals, newsletters, event follow-ups, stewardship updates, and segmented fundraising messages should draw from the same donor context the team uses for relationship work.

  • Fundraising appeals
  • Newsletters
  • Stewardship updates
  • Event follow-up
  • Campaign-linked outreach

Lists and audiences stay explainable

A list is more useful when staff can understand why someone is on it, what kind of list it is, and whether they should receive the message.

  • List kinds
  • Subscribers
  • Segments
  • Suppression rules
  • Unsubscribe context

Templates and merge fields reduce repeat work

Reusable copy helps teams send consistent messages without starting from a blank page. Merge fields and fallbacks keep personalization useful even when a record is incomplete.

  • Email templates
  • Reusable content
  • Merge fields
  • Fallback text
  • Saved receipt copy

Receipts and notices are communications too

Receipt cover emails, refund notices, confirmation messages, payout messages, failed-payment notices, and card-update reminders are part of the donor experience.

  • Receipt cover emails
  • Refund notices
  • Confirmation language
  • Failed-payment notices
  • Card-update reminders

History should follow the donor

Staff should be able to understand recent touchpoints from the donor record instead of checking an email tool, a receipt queue, an event export, and a notes field separately.

  • Email activity
  • Gift context
  • Event context
  • Tasks and next steps
  • Donor timeline context

Deliverability and consent matter

Fundraising email still needs practical controls: opt-outs, list-unsubscribe headers, suppression, permissions, and review habits before anything goes donor-facing.

  • List-unsubscribe headers
  • Opt-outs
  • Suppression
  • Email settings
  • Permission-aware sending