The non-profit playbook. Built in the builder, decided by your donor system.
Ten journeys, each drawn below as it runs. The decision comes from your donor CRM, your payment gateway, your programme system or criteria you set; the journey carries it. Aims are targets to agree in the pilot, not results.
Ask for the monthly gift after the third one-off.
A third one-off gift in twelve months asks your donor system whether the donor is already monthly, then sends one WhatsApp with Make it monthly or Not now; a tap goes to your payment system to set it up.
- Decides
- your donor system and the count you set.
- Aim
- monthly givers without a phone campaign.
Recover the monthly gift that failed.
A failed collection reported by your gateway sends one WhatsApp with the update-card link, waits for the retry from your system, stops when it collects, and escalates to SMS and then a call if it does not.
- Decides
- your gateway's failure reason and retry.
- Aim
- monthly gifts kept when the card changes.
Finish the donation that stopped at the amount step.
A session with the amount step opened and no payment sends one WhatsApp with a link back to the step and the closing date from your appeal, reminds once before it closes, and stops when they give.
- Decides
- a rule you set, and the closing date your system holds.
- Aim
- more gifts finished before the appeal closes.
Ask for the second gift before the first is forgotten.
A donor with a first gift and no second in ninety days enters a segment, gets a Story of what the first gift did, and one ask on their channel when they finish it; silence for thirty days ends the journey without a second message.
- Decides
- your segment definition and the window you set.
- Aim
- more first-time donors giving a second time.
Bring back last Ramadan's donor before this Ramadan.
A donor who gave in last year's window and not since waits until the date on your calendar, then gets one WhatsApp at a sensible hour in their own time zone with the Zakat calculator and a tap to give; a gift stops the journey, and silence gets one reminder in the last ten nights.
- Decides
- your calendar and the segment you define.
- Aim
- last year's donors back before the window closes.
Collect the pledge from the dinner.
A pledge recorded at the event waits thirty days from the date your CRM holds, sends the pay link by WhatsApp, stops when your CRM says paid, and escalates to SMS and then a call from a person, with the outcome written back.
- Decides
- your CRM's pledge date and paid status.
- Aim
- pledges collected without a chasing list.
Renew the sponsorship in month eleven.
A sponsorship entering its eleventh month asks your donor system whether it is active and renewal is open, sends a Story of the year, then one WhatsApp with Renew or Not now; a tap goes to your payment system to renew for a second year.
- Decides
- your donor system's sponsorship record.
- Aim
- sponsorships renewed before they lapse.
Fill tomorrow's volunteer shift.
A shift booked for tomorrow sends one WhatsApp with Confirm or Cannot make it; a confirmation is written back, a cancellation offers the slot to the waitlist the same hour, and silence gets one SMS at the hour you set.
- Decides
- your volunteer system's roster and waitlist.
- Aim
- fewer empty shifts on the day.
Tell the beneficiary the grant is ready, and confirm the pickup.
A grant marked ready in your programme system sends one SMS with the collection point and a code, calls with the same code if the SMS is not delivered, and writes the pickup back when the code is checked at the point.
- Decides
- your programme system; the code is checked at the point.
- Aim
- every grant collected by the person it was meant for.
Report the appeal with a Story, and learn what to fund next.
An appeal closed in your system sends every donor to it a Story of what it funded, page by page, with a poll on what the next appeal should fund; completion and the poll answer go on the record, and the answer builds the segment for the next appeal.
- Decides
- the event, and the poll answer.
- Aim
- an impact report that is read, and the next appeal aimed by the donors themselves.
Where a step says your system decides, the journey calls your system and branches on its answer. xNotify carries the journey; it does not become the donor database.