# Use cases

Each use case takes a business from an empty account to an agent that works. It starts with what you achieve, who it is for and what you need, shows the flow, and then walks through the calls in order with the full prompt of the agent, the pipeline and its fields, the tools, the channel, the webhooks and a test conversation. Every page has cURL and TypeScript tabs, and the MCP tool name where it helps.

| Use case | You get |
| --- | --- |
| [Sell on WhatsApp with a catalog and a cart](/use-cases/whatsapp-sales-agent) | An agent that qualifies leads, shows catalog products, takes a cart, hands over to a person and runs a template campaign. |
| [Book, move and cancel meetings with an agent](/use-cases/meeting-scheduling) | An agent that offers real free times, books, moves and cancels, with a WhatsApp reminder and `meeting.*` events. |
| [Support with tools and human approval](/use-cases/support-with-approvals) | A support agent that looks up orders through your action and proposes refunds that a person approves. |
| [A copilot for your team with your own data](/use-cases/internal-copilot) | A data connector built with the SDK, checked with the CLI, and an internal copilot that reads it with masked data. |
| [Run Lelemon for your customers with subaccounts](/use-cases/platform-subaccounts) | One subaccount per customer, shared actions and MCP servers, budgets and one webhook for all. |
| [Give an agent a background job](/use-cases/background-runs) | A run that works on its own, asks a question, finishes with a summary and can be canceled. |

## Before you start

1. Create a key with the scopes the page lists ([API keys](/guides/api-keys)). The scripts create and delete data in your organization.
2. Install the SDK and read the key from the environment, as in the [Quickstart](/get-started/quickstart). For a first walk through the basics, see [Set up an account from zero](/get-started/setup-from-zero).
3. Where a step calls your backend (an action, a connector, an MCP server), the example runs a small local server. Your key must be allowed to call that site: an administrator adds it to `allowedActionOrigins`.

## Run the examples

Every use case has a runnable script in [`apps/docs/examples/use-cases`](https://github.com/Lelemon-studio/lelemon-app/tree/main/apps/docs/examples/use-cases). It creates what it needs in your organization, prints the result of each step and removes what it created.

```bash
cd apps/docs/examples/use-cases
npm install
export LELEMON_API_KEY=lel_live_...
npm run whatsapp-sales-agent
```

Each README says which scopes and ports the script needs. The TypeScript blocks of each page are taken from its script, and the results shown come from a real run.

## Use them with MCP

The [MCP server](/tools/mcp) exposes every operation as a tool named by its `operationId`, such as `pipelines.create`, `agents.tools.grant` or `runs.answer`. Give an MCP client the page and ask it to follow the steps with a key: the arguments are the same as in the cURL and TypeScript tabs.