> For the complete documentation index, see [llms.txt](https://docs.flycode.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flycode.com/docs/guides/recovery-sms-when-to-add-sms-to-failed-payment-outreach.md). # Recovery SMS: when to add SMS to failed payment outreach When SMS improves failed payment recovery, how to coordinate it with retries and email, consent and TCPA basics, timing, templates and expected results. {% hint style="info" %} **TL;DR:** SMS reaches customers who do not open billing emails, which makes it valuable for the failures that genuinely need the customer to act (a new card, an authentication step). It is not a replacement for silent recovery: send it only after retries and backup methods have had their chance, coordinate it with email so the customer gets one nudge on the channel they check, and treat consent as a hard requirement. FlyCode Recovery SMS runs inside the same coordinated recovery flow as retries and email. {% endhint %} *By the FlyCode team. Last reviewed September 2026.* {% hint style="success" %} **Key takeaways** * SMS belongs at the point where the network needs the customer: hard declines, authentication required, and soft declines that survived the retry window. * Coordination matters more than channel: a text about a payment that is about to be retried successfully creates confusion and cancellations. * Consent is not optional. Collect explicit opt-in for billing texts, honour STOP immediately, and send within local daytime hours. * Keep the message short, name your brand, say what happened and give one login-free link to fix it. {% endhint %} ## When SMS helps and when it does not | Situation | Use SMS? | Why | | ---------------------------------------------------------------------------------------------- | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | | Soft decline, first days after failure | No | Silent retries and backup methods recover most of these with zero customer effort. A text here trains customers to expect billing noise. | | Hard decline (closed account, replaced credentials, stolen or lost card) with no backup method | Yes | The customer must supply a new payment method; the sooner they see the request, the higher the recovery rate. | | Authentication required (3DS or SCA) | Yes | Only the customer can complete the challenge; a text with the link gets it done faster than email. | | Soft decline after the retry window | Yes, as a final step | Email has already gone out; SMS catches customers who did not open it. | | Customer has not opted in to texts | No | Consent first, always. | ## Coordinating SMS with retries and email The ordering in a coordinated recovery flow: 1. Retries and [backup payment methods](/docs/guides/backup-payment-methods-on-stripe-for-subscription-recovery.md) run first, silently. 2. If the decline requires the customer, an email goes out at local time with a login-free update link. 3. If the email is not acted on within the configured window, or the failure is time-critical (access about to lapse), an SMS follows on the same case with the same link. 4. All channels stop the moment the invoice is paid; a pending retry pauses outreach so nobody is asked to fix a charge that succeeds on its own. FlyCode Recovery SMS is built into this flow: texts are coordinated with your email sequence and retry schedule so customers get a single nudge on the channel they check most. ## Consent and compliance basics Rules vary by country; in the United States the Telephone Consumer Protection Act (TCPA) and carrier rules apply. Practical requirements shared across most jurisdictions: * **Explicit opt-in** for account and billing texts, collected with clear language at sign-up or in the account settings. Marketing consent does not automatically cover billing texts, and the reverse is also true. * **Identify the sender** in every message (your brand name). * **Honour opt-out** instantly: STOP, and the local equivalents, must end texts for that customer. * **Quiet hours.** Send within local daytime hours; FlyCode schedules by the customer's timezone. * **Keep records** of consent, message content and delivery. This is a summary, not legal advice; confirm requirements for your markets with counsel. ## What a good recovery text looks like Short, specific, one action: > Acme: your payment for the Pro plan did not go through. Update your card in 30 seconds to keep your workspace: acme.co/pay/x7k2 Reply STOP to opt out. Avoid discount offers in a recovery text (this is not a promotion), avoid alarm language, and never ask for card details by reply. ## What to expect Results depend on how much of your failure mix needs customer action. Businesses with a high share of hard declines or authentication failures, and consumer audiences who rarely open billing email, see the largest gains. Measure SMS on the incremental recoveries it produces after email had its chance, not on gross clicks; the [recovery metrics reference](/docs/read-more/recovery-metrics-and-reporting-reference.md) explains the funnel. ## FAQ ### Should I text customers as soon as a payment fails? No. Most failures recover silently within days. Text only once the decline is known to need the customer or the retry window has closed. ### Do I need separate consent for billing texts? In most jurisdictions yes: consent must cover the type of message being sent. Add billing and account notifications explicitly to your opt-in language. ### Does FlyCode send the SMS from my number? Messages are branded with your name and coordinated with your email and retries; sender configuration is set up during onboarding with your account manager. ## Related * [Dunning management 2026 guide](/docs/dunning-management-2026-guide.md) * [How FlyCode works](/docs/guides/how-flycode-works-architecture-of-the-recovery-engine.md) * [Priority recovery and dynamic recovery](/docs/guides/priority-recovery-and-dynamic-recovery-handling-high-value-failed-invoices.md) * [Failed payment outreach](https://help.flycode.com/failed-payment-outreach) in the Help Center * [Subscription compliance](https://help.flycode.com/subscription-compliance) in the Help Center --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.flycode.com/docs/guides/recovery-sms-when-to-add-sms-to-failed-payment-outreach.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.