> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/journeys-and-pages/journey-settings/journey-purpose.md). # Purpose A journey's **Purpose** declares the function it serves — for example **Change Plan** or **Cancellation**. Purpose is how PeakCommerce decides *which* journey to run when a customer or CSR triggers an action from a portal. ## Why purpose matters The portal and CSR **Change Plan** and **Cancel Plan** entry points resolve the journey to run by its **type and purpose** (and the customer's cohort) — **not by its name**. You can rename a journey freely without breaking the link: a journey named "Win-Back 2026" carrying the **Cancellation** purpose still powers the Cancel Plan button. > This replaces the older approach of naming a journey exactly (for example "Customer Cancellation") so the portal could find it — set the **Purpose** instead. A legacy name match is still honored as a fallback, but purpose is the durable binding. ## Purposes Common purposes include: * **Change Plan** — powers the portal and CSR **Change Plan** flow. * **Cancellation** — powers the **Cancel Plan** and retention flow (see [Customer Retention Journey](/product/customer-self-service/subscription-management/customer-retention-journey.md)). ## Choosing among several journeys When more than one active journey shares the same type and purpose, PeakCommerce uses [profile assignments](/product/journeys-and-pages/journey-settings/profile-assignments.md) to target cohorts — so different customer segments, or the CSR portal versus the customer portal, can run different journeys for the same purpose. --- # 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.peakcommerce.com/product/journeys-and-pages/journey-settings/journey-purpose.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.