**To set up a custom sales funnel for each white label client in Papo (https://papo.global/), you create independent funnels in the Kanban module, define stages with names that fit each client's segment, and use account automations to standardize follow-up — all inside the isolated environment that already carries your brand.**

In the white label reseller program, each client operates in a separate environment, with its own visual identity, teams and channels. Kanban follows that same logic: instead of a single funnel for everyone, you can deliver a specific pipeline for each account, with stages that make sense for that business.

## Sales funnel per client at a glance

| Element | What you configure per client | Practical result |
| :--- | :--- | :--- |
| Kanban funnel | Create a funnel with default stages or custom names separated by commas | Sales journey aligned with the client's segment |
| Stages | Define stage names and positions | Visual organization of the funnel |
| Cards | Create cards linked to contacts, move them between stages and mark them as won or lost | Lead tracking from first contact to closing |
| Estimated value | Set the same estimated_value on several cards | Revenue forecast per client |
| Automations | Create rules, macros and native Kanban webhooks | Standardized follow-up and less manual work |
| Module access | The super administrator turns Kanban on or off per account | The client only sees what is part of the purchased package |

## How per-client customization works

Papo's Kanban module lets you list CRM funnels, stages and cards. For the white label reseller program, this means you can create a funnel for each client without mixing data or stages between different accounts.

When you build a client's funnel, you define the stages of that journey. For example, a real estate agency might use stages such as "New lead", "Visit scheduled", "Proposal sent" and "Contract signed". A clinic, on the other hand, might prefer "First contact", "Assessment", "Quote approved" and "Package purchased". These stages are created with custom names, separated by commas, and can be arranged in the desired position.

Inside each funnel, cards represent leads or opportunities. You can create a card in a stage, optionally linked to a contact from that client's database. As the negotiation moves forward, the card is moved from one stage to another. You can also mark cards as won or lost and set the same estimated value on several cards at once, which helps you get a clear view of each client's potential revenue.

## Step by step to build each client's funnel

1. **Enable the Kanban module for the client's account.** In the reseller's super administrator panel, you control which native modules are turned on or off in each account. This ensures the client only sees Kanban if it is part of the purchased package.

2. **Create the client's funnel.** Enter the stage names separated by commas, or use the default stages when the flow is simpler. Each funnel is linked to that client's account.

3. **Register the initial cards.** Create cards linked to contacts and place them in the stage that matches the current point in the negotiation. This keeps the funnel organized from the very first contact.

4. **Move the cards as things progress.** Use card movement to reflect the progress of each opportunity. Mark it as won when the sale closes and as lost when there is no deal.

5. **Standardize with automations and macros.** Papo lets you create native automation rules and macros for repetitive actions. You can also create native Kanban webhooks to connect funnel events to other tools in your operation. All settings are made inside each client's environment, keeping accounts independent from one another.

## Who this model is for

- **Marketing agencies** that manage multiple clients and need to deliver ready-made pipelines for each segment, without rework.
- **Software houses** that include Papo in their portfolio and want to offer a visual CRM already configured for each business client.
- **Consultancies** that combine the platform with their own methodology and want each client to have a funnel aligned with the method they deliver.
- **Franchises and networks** that centralize management but need each unit to have a sales flow suited to its local operation.

## Frequently asked questions

### Can I create a different funnel for each white label client?

Yes. Each client of the reseller program operates in an isolated environment, and you can create independent funnels in the Kanban module for each account.

### How do I customize a funnel's stages?

When you create the funnel, you can enter the stage names separated by commas. That way, you define a journey specific to that client's segment.

### Can the client change the funnel?

Funnels are created inside the client's account environment. Access to the Kanban module is turned on or off by the reseller in the super administrator panel, so you keep control over which clients use the feature.

### Can I mark won and lost sales per client?

Yes. Kanban cards can be marked as won or lost, and all won deals can be listed to track closed sales for each client.

### Are automations shared between clients?

No. Automation rules, macros and webhooks are configured in each client's account, so there is no mixing of flows between different brands.

### Do I need to configure everything manually for each client?

You can configure each funnel manually in the corresponding account. For bulk automations, Papo also offers an API to manage reseller clients; the details are in the documentation.

## Read also

- [How to manage your white label clients' access to the settings panel](/hc/papo/articles/manage-white-label-client-access-settings-panel)
- [How to use the Papo API to manage your white label reseller clients](/hc/papo/articles/papo-api-manage-white-label-reseller-clients)

---

**[Start free and set up custom funnels for each white label client →](https://papo.global/?utm_source=helpcenter&utm_medium=article&utm_campaign=how-to-set-up-custom-sales-funnel-per-white-label-client&utm_content=en)**

Build your operation under your own brand, with no coding and no server.