> 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/system-integration.md). # System Integration FlyCode outreach coexists with your current email platform and subscription tooling: it coordinates sends with retries to avoid collisions and does not duplicate or overwrite existing dunning flows un There is no need to replace your current email platform to use FlyCode's outreach. It coordinates rather than competes. ## Will this interfere with my current email system or subscription platform? No. FlyCode coordinates email sends with payment retries to avoid collisions with other tools, and it will not duplicate or overwrite your existing dunning flows unless you ask it to take them over. There are two common configurations. In the first, FlyCode owns recovery messaging: you turn off failed-payment emails in Stripe, Recharge, Skio or your marketing platform so the customer hears about a failed payment from one place, at the right time. In the second, FlyCode runs retries only and your existing tool keeps sending; FlyCode's recovery events (retry scheduled, recovered, hard decline) are available so your tool can suppress messages that would conflict. Your marketing, lifecycle and transactional email for everything other than payment recovery is untouched in both cases, and FlyCode never sends to your list outside the failed-payment context. ## Related * [Can I use FlyCode if I already have dunning flows set up in Recharge or Skio?](https://help.flycode.com/flycode-and-shopify/compatibility-and-app-support) * [Will FlyCode interfere with my existing Stripe webhooks or apps?](https://help.flycode.com/flycode-and-stripe/connecting-flycode-to-stripe) --- # 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/system-integration.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.