> 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.md).

# Failed Payment Outreach

How FlyCode's failed payment outreach works: your brand and domain, dynamic templates by decline reason, local-time delivery, compliant sending, and coordination with retries and your existing email t

FlyCode's outreach product sends the emails and SMS that recover the payments retries cannot. It runs in the background under your brand, times every message to the retry cycle and the customer's local hours, adapts the content to the decline reason, and coexists with your existing email platform. This collection covers customization, delivery strategy and system integration.

{% hint style="info" %}
**Quick answer:** emails are sent from your domain with your branding, use dynamic templates that change by decline reason and retry status, go out in the customer's local time, follow CAN-SPAM and GDPR, and are never sent immediately after a soft decline. Typical deliverability is a 95-plus sender score.
{% endhint %}

## In this section

* [Messaging Customization](https://help.flycode.com/failed-payment-outreach/messaging-customization): your own brand and domain, and how templates adapt by decline reason, segment and retry status.
* [Delivery Strategy](https://help.flycode.com/failed-payment-outreach/delivery-strategy): local-time delivery, hard-decline cadence, compliance, how it differs from Stripe and ProfitWell emails, and deliverability.
* [System Integration](https://help.flycode.com/failed-payment-outreach/system-integration): coexisting with your current email system and subscription platform.

## Related

* [Dunning management 2026 guide](https://docs.flycode.com/docs/dunning-management-2026-guide) (dunning email best practices)
* [Coordinating Messaging with Recovery](https://help.flycode.com/handling-failed-payments/coordinating-messaging-with-recovery)
* [Email Behavior & Deliverability](https://help.flycode.com/ai-payment-recovery/email-behavior-and-deliverability)


---

# 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.md?ask=<question>&goal=<user_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.