> ## Documentation Index
> Fetch the complete documentation index at: https://help.lobyco.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Cases

> Goal-framed worked examples — pick a real scenario and follow it end to end.

Worked examples, framed by what you are trying to achieve rather than by which screen you are on. This is the **#2 entry point on purpose**: people work trial-and-error rather than read-then-do, so examples belong early, not buried mid-list.

Every page here states the goal, draws the canvas as a diagram, lists the segment attributes involved, and ends with the variations that would otherwise have become separate pages.

## Build an audience

<Columns cols={2}>
  <Card title="By product bought" href="/business-documentation/use-cases/find-customers-who-bought-a-specific-product">
    Everyone who bought a given product in a recent window.
  </Card>

  <Card title="By spend in a chain" href="/business-documentation/use-cases/find-customers-by-spend-in-a-chain">
    Customers over a spend threshold in one chain.
  </Card>

  <Card title="By purchase volume" href="/business-documentation/use-cases/find-customers-by-purchase-volume-in-a-store">
    How many items, in one store, over a period.
  </Card>

  <Card title="By profile and frequency" href="/business-documentation/use-cases/find-customers-by-profile-and-purchase-frequency">
    A profile attribute combined with how often someone shops.
  </Card>
</Columns>

## Shape the result

<Columns cols={2}>
  <Card title="Add extra customer data" href="/business-documentation/use-cases/add-extra-customer-data-to-your-results">
    Attach attributes to the output with the Enrich block.
  </Card>

  <Card title="Split into groups" href="/business-documentation/use-cases/split-a-segment-into-groups">
    Divide one audience so each group gets its own treatment.
  </Card>
</Columns>

## Feed and run a campaign

<Columns cols={2}>
  <Card title="Reuse a saved segment" href="/business-documentation/use-cases/reuse-a-saved-segment-across-campaigns">
    Define an audience once, select it in any campaign.
  </Card>

  <Card title="Use an imported customer list" href="/business-documentation/use-cases/use-an-imported-customer-list-instead-of-a-segment">
    Seed the campaign from a file of customer IDs.
  </Card>

  <Card title="Reuse a previous result" href="/business-documentation/use-cases/reuse-a-previous-campaigns-results">
    Chain one campaign's output into the next.
  </Card>

  <Card title="Schedule and check results" href="/business-documentation/use-cases/schedule-a-campaign-and-check-its-results">
    Put it on a schedule, then read Execution History.
  </Card>
</Columns>

## Offers

<Columns cols={1}>
  <Card title="What you can build" href="/business-documentation/use-cases/offer-examples-what-you-can-build">
    Every discount shape the promotion platform supports, with an example of each.
  </Card>
</Columns>

<Info>
  **Where this content came from.** Eleven pages migrated from the current wiki: ten from `Segmentation > User exercises` and one from `Offers > Offer examples`. The twelve source exercise pages became ten — three chain-specific pages collapsed into [Find customers by spend in a chain](/business-documentation/use-cases/find-customers-by-spend-in-a-chain), since they differed only in the chain name.
</Info>

<Warning>
  **Still to do in this section.**

  * **Two planned pages are not written** — multi-game priority and attempts interaction, and lapsed-customer win-back. Neither exists in the current wiki, so there was nothing to migrate; both were asked for in client feedback.
  * **Orchestration examples are missing.** Use Cases was scoped to campaign setup; it needs to widen to orchestration, which is where the sharpest client complaint landed.
  * **Screenshots have not been carried over.** The source pages leaned on screenshots of the segment builder and the finished canvas. The canvas is redrawn as a diagram on each page; the segment-builder settings are now written out as attribute tables. Neither is a like-for-like replacement for an annotated screenshot.
  * **A consolidation call is open.** The four "build an audience" pages are the same recipe with different attributes. They could become one page with a variations table. Kept separate here because the gallery needs entries, but it is worth deciding deliberately.
</Warning>