> 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/failed-payment-outreach/messaging-customization.md). # Messaging Customization Customizing FlyCode recovery emails: send from your own domain with your branding, and adapt tone, call to action and structure by decline reason, customer segment and retry status. Customers should only ever see you. FlyCode's outreach is white-labelled and its templates are dynamic, so the message fits your brand and the specific failure. ## Can I use my own brand and domain for emails? Yes. All emails are sent from your domain and carry your branding, sender name and reply-to address. FlyCode runs behind the scenes and customers never see its name. Setup involves adding SPF and DKIM records for the sending subdomain so that mail authenticates as yours, which also protects deliverability. SMS, where enabled, is sent under your brand as well. The payment update link in each message goes to your processor's native payment page (for Stripe, the hosted page with all local payment methods enabled), so the customer completes the update in a familiar, fast interface. ## Can I customize the content or messaging? Yes. Templates are dynamic: tone, call to action and structure adjust automatically based on the decline reason (a request for a new card for a hard decline, a light notice that a retry is scheduled for a soft decline), the customer segment (for example plan tier or B2B versus consumer) and retry status (first notice, reminder, final notice before cancellation). On top of that you can add your own branding, wording and language, and set the cadence. FlyCode recommends keeping messages short and transactional, since that is what recovers payments and keeps sender reputation high; the [dunning email best practices](https://docs.flycode.com/docs/dunning-management-2026-guide) section of the dunning guide has examples. ## Related * [Delivery Strategy](https://help.flycode.com/failed-payment-outreach/delivery-strategy) * [Should I expose the raw decline code to customers?](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/failed-payment-outreach/messaging-customization.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.