Template
Final WhatsApp message sent at day 14 alongside the final email. Goal: reach the last bucket of non-responders with the channel they are most likely to read.
Hey {{first_name}}, last check-in on this. Your {{product_name}} account is being paused today because of the failed payment.
Your data is safe for 90 days. If you want to come back, just update the card: {{short_update_link}}
If you are done with us, no worries - I appreciate the time you gave us. Reply with a one-liner on what went wrong if you have a second, it really helps us improve.Variables in {{like_this}} should be replaced with your merge fields.
Matches the tone of the email final notice but adapted for the conversational medium. The "appreciate the time" close is warm without being manipulative. The feedback ask gets much higher response on WhatsApp than on email.
Yes - on WhatsApp it converts into replies more often than on email, and those replies are the single best data source for fixing churn drivers. Always end the dunning sequence with a path to communication.
Automate this with Rebounce
Rebounce detects payment failures via Stripe Connect, classifies them by decline code, and runs the optimal dunning sequence across email, SMS, WhatsApp, and in-app banners. The templates above are the exact patterns Rebounce uses out of the box - you can adapt the copy to your brand voice and Rebounce handles delivery, timing, and sequence cancellation when a retry succeeds.
Start free trialWhatsApp message sent on day 3-5 for customers with a WhatsApp-linked phone number. Goal: use the highest-open-rate channel available (90%+ in most markets) for maximum reach.
Sent on day 14 after all retries and prior emails have failed. The grace period is over. Goal: close cleanly, preserve goodwill, and leave the door open for reactivation. A well-done final notice is often the best win-back hook you have.
Sent 30-60 days after a subscription was cancelled due to failed payments. The customer has had time to decide whether they want to come back. Goal: re-engage with a specific reason (new feature, usage-relevant improvement) and remove friction to reactivate.