> For the complete documentation index, see [llms.txt](https://help.flycode.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.flycode.com/ai-payment-recovery/email-behavior-and-deliverability.md). # Email Behavior & Deliverability When FlyCode emails customers about failed payments (not after every attempt, and never immediately after a soft decline) and how it keeps deliverability high with transactional infrastructure, SPF an Recovery emails only work if they are sent at the right moment and actually reach the inbox. FlyCode is deliberate about both. ## Will FlyCode send emails to customers after every failed payment? No. FlyCode avoids unnecessary emails, especially after soft declines, because telling a customer about a failure that a retry is about to fix creates friction and pushes some customers to cancel. Emails are sent only when they are likely to help: after silent recovery has been exhausted on a soft decline, or promptly on a hard decline where the customer has to act. Each send is timed to the customer's location and past engagement patterns, so messages arrive during waking hours rather than at 2 a.m. This is the opposite of processor defaults such as Stripe's, which can email at every retry and reach eight emails per invoice. ## How do you keep email deliverability high? By treating recovery emails as transactional mail, not marketing. FlyCode sends through transactional infrastructure rather than a marketing email platform, enforces SPF and DKIM alignment on your sending domain, optimizes sender domain configuration, and delivers from high-reputation IPs. Templates are plain and short, which avoids promotional filtering. The typical sender score is 95 or higher, and emails carry your brand and domain, so customers see you rather than FlyCode. If you prefer to keep messaging in your own email tool, FlyCode can run retries only and leave sends to your system. ## Related * [Failed Payment Outreach](https://help.flycode.com/failed-payment-outreach) * [Coordinating Messaging with Recovery](https://help.flycode.com/handling-failed-payments/coordinating-messaging-with-recovery) --- # 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://help.flycode.com/ai-payment-recovery/email-behavior-and-deliverability.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.