> 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-basics/journey-use-cases.md). # What you can build Journeys are a **general-purpose engine for guided, multi-step transactions and workflows**. Because every step can **collect input**, **branch on logic**, and **trigger actions** — across your catalog, billing (Zuora), CRM (Salesforce), payments, and connected integrations — you can build far more than a checkout page. This page catalogs common and creative patterns. Most of them compose the same primitives (steps, shared context, actions, and branching); which specific actions are available depends on your configuration and connected integrations. ## Acquire new customers * **Self-service checkout & signup** — plan/offer selection → account → billing → confirmation, creating a real subscription at the end. * **Free trials & freemium** — start a trial, then a trial-to-paid or freemium upgrade flow. * **Usage-based signup** — sign customers up for metered or hybrid plans; sell credits or usage top-ups. * **Quote acceptance** — accept a sales quote, e-sign, and pay in one guided flow (sales-assisted close). * **Guided product configuration** — CPQ-style flows that build the right bundle before checkout. * **Pre-orders, waitlists & reservations**; **gift subscriptions** (purchase and redemption). * **Promo & coupon redemption** landing flows. ## Expand existing customers * **Plan changes** — upgrade, downgrade, or switch plans. * **Add-ons & quantity** — attach add-ons, add seats, or increase quantities. * **Renewals & re-contracting** — extend a term or move to a new contract. ## Retain & recover * **Cancellation with save-offers** — branch into pause, downgrade, or discount offers *before* a cancellation completes. * **Win-back / reactivation** — re-subscribe lapsed customers. * **Dunning recovery** — a "fix your failed payment" flow you link from a billing email. * **Pause / resume** a subscription. ## Self-service account operations * **Pay invoices** — settle outstanding invoices from a hosted payment page. * **Update billing details** — payment method, billing/contact info, tax-exemption upload. * **Consents & terms** — accept new Terms of Service, manage consents and acknowledgements, or run a preference center. * **Switch accounts** — move between multiple linked accounts. ## Onboard & qualify * **Onboarding wizards** — collect provisioning details and connect integrations after purchase. * **Eligibility / qualification quizzes** — ask a few questions and **route the customer to the right offer**. * **Verification-gated signup** — KYC or fraud-check (e.g. SEON) steps before an order is created. ## Assisted & partner-led * **CSR-assisted flows** — reps run change, cancel, or checkout on a customer's behalf. * **Partner-led ordering** — partners transact for the customers they manage. * **Partner onboarding & deal registration.** ## Beyond classic commerce Because actions are open-ended, journeys also work as general guided workflows: * **Surveys & data collection** that branch and trigger actions (open a case, tag the account, enroll the customer in an audience). * **Returns / RMA / refund requests**; **warranty registration**. * **Demo or appointment booking** that creates a lead or order. * **Referral-program enrollment**, **event registration**, **recurring donations**. * **Multi-step applications** (e.g. financing) with external checks and approval branching. ## Multipliers Any of the patterns above gets more powerful combined with the rest of the platform: | Capability | What it adds | | --------------------------- | ---------------------------------------------------------------------------------- | | **Branching (Flow)** | Personalize the path based on each answer | | **Audiences & Experiences** | Target who sees which journey or offer | | **Experiments** | A/B test journey variants | | **Market Locales** | Localized and per-currency variants | | **Embed** | Drop a journey into any website or app | | **Rules & Automation** | Guardrails — pricing ceilings, required steps, validation | | **Agent API** | An AI agent can drive a journey programmatically, or a journey can hand off to one | See also: [Journeys Overview](/product/journeys-and-pages/journey-basics/journeys-overview.md) · [Create a journey](/product/journeys-and-pages/journey-basics/adding-a-journey.md). --- # 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-basics/journey-use-cases.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.