Failed recurring donation follow-up should explain that a scheduled contribution did not complete, provide a trusted way to review payment details, and make help easy to reach. Keep the message factual and avoid assuming why the payment failed.
A declined or interrupted payment is not a reliable signal that someone stopped caring about the cause. Treat recovery as a service conversation, with a clear stopping point and respect for the supporter’s preferences.
Confirm the status before contacting the supporter
Check that the payment is actually unsuccessful rather than pending, refunded, or already resolved. Identify the relevant contribution, the approved recovery path, and any scheduled retry behavior in your configured payment system. Do not improvise additional retries or promise a timing your team has not verified.
donr. handles recurring giving and other payment streams in CauseFi., while trak. connects payment-related activity to the supporter record. Use both the financial status and the relationship context before choosing the next action.
Use a clear, low-pressure first message
Subject: Please review your recurring gift to [organization]
Hello [name],
Your scheduled contribution to [organization] did not complete. If you would like to continue, please sign in through [verified account link] to review your payment details and giving settings.
If you have already updated them, thank you. If you need help or would like to discuss your support, contact [trusted support channel]. Please do not send card or bank details by reply.
Use the wording only when it matches the actual status and account options. Include an amount or scheduled date only when the recipient and transaction have been correctly identified.
Keep recovery inside a trusted account flow
Use the approved secure destination, with a recognizable organization name and a clear explanation of the task. Give supporters the option to navigate through the known website themselves. Staff should never request a full card number, security code, password, or banking credentials in a message thread.
If someone reports a suspicious message, route them to your established support process instead of asking them to prove their identity by sending sensitive information. The aim is to restore confidence as well as a payment method.
Define the follow-up and stop conditions
- Assign one owner for unresolved recovery questions.
- Check for a completed update before sending another reminder.
- Stop the sequence when the issue resolves or the supporter asks to stop.
- Route requests to pause or change giving through the appropriate account or support process.
- Review repeated failures individually instead of sending an indefinite sequence.
txt. supports recovery messaging and two-way conversations. Use only the channels and audience permissions appropriate to the relationship. A shorter sequence with clear help can be more respectful than repeated urgency.
Distinguish recovery from a new fundraising appeal
A payment-service message should not quietly become a larger ask. Resolve the existing issue first. If the supporter wants a different arrangement, explain the choices without pressure; the guide to round-ups and monthly donations can help clarify how the commitments differ.
What should the team measure?
Track confirmed failed payments, resolved cases, support requests, cancellations, and unresolved aging cases as separate categories. Do not count a message click as recovered revenue or a payment-method update as a completed contribution. Review the final transaction status before reporting funds recovered.
A good recovery process leaves the supporter informed and in control, even when their decision is to pause. That is a relationship worth protecting.