> For the complete documentation index, see [llms.txt](https://docs.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.distro.so/workflows/sequence-outcomes.md). # Handle sequence enrollment outcomes Sequence steps can succeed, find an existing enrollment, skip a prospect or fail. Design follow-up around the outcome the step actually returns. ## Configure the action Choose the provider, sequence/cadence/campaign and sender or mailbox where required. Map a usable prospect identity. Gong uses a CRM prospect ID; HubSpot uses a contact returned by an earlier HubSpot step; other providers expose their own person mappings. See the guide for [Apollo](/integrations/apollo-sequences.md), [HubSpot](/integrations/hubspot-sequences.md), [Outreach](/integrations/outreach.md), [Salesloft](/integrations/salesloft.md), [Amplemarket](/integrations/amplemarket-sequences.md), [Gong](/integrations/gong.md) or [Smartlead](/integrations/smartlead.md). ## Interpret the result Read the action's status and skip reason. Existing enrollment or a provider exclusion may be an expected outcome rather than a failed call. An enrollment accepted by the provider does not prove that the first message was delivered. Review delivery in the engagement tool. ## Retry carefully Inspect Logs and the destination enrollment before restarting a failed journey. A prospect may already have been created or enrolled before a later operation failed. Simulation confirms mappings and branches with sample output. A controlled live enrollment confirms provider access and behavior for that case. Keep explicit No match, missing sender and provider failure paths. A failed provider call should not be treated as successful follow-up. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.distro.so/workflows/sequence-outcomes.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 `build a script that syncs our docs to a CMS` 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.