Integrations / SMS
When the email lands in spam, the text still arrives
Failed-payment emails get ignored or filtered. ChurnGuard sends dunning SMS through your own Twilio account, so customers see the payment-update link on the device they actually check.
Last updated: August 2026
How SMS dunning works in ChurnGuard
A payment fails in Stripe → your dunning playbook sends a text with an update-payment link → retries and follow-ups continue on the schedule you set. You write the message once; ChurnGuard sends it at the right moment.
SMS and email work together
SMS doesn't replace your email dunning sequence — it reinforces it. Customers who ignore three emails often respond to one text. ChurnGuard runs both channels from the same playbook, so the customer gets a consistent message wherever they read it.
You can also pair SMS with Slack alerts so your team gets notified the moment a payment fails and a text goes out to the customer.
Your Twilio account, your number
Messages go out from your own Twilio phone number, and you control the content and cadence.
Best practice: only text customers you have an existing relationship with, keep messages about their own payment, and include a way to opt out.
Frequently asked questions
Do I need my own Twilio account?
Yes. ChurnGuard sends SMS through your Twilio account and phone number, so messages come from you and you control them.
Can I edit the SMS text?
Yes. You write and edit the message templates in your dunning playbook.
Is SMS dunning compliant?
Follow standard best practices: text only existing customers about their own payment, identify yourself in the message, and provide an opt-out. When in doubt, check the rules for the countries you text.
See how much failed payments are costing you
Run a free churn audit — no account required.