# Your brand. A client experience you can operate.

White labeling gets your name on the service. Account setup, billing and support determine whether it feels like your service every day.

Published: 2026-10-17

Reviewed: 2026-10-17

## What should agencies look for in a Synthflow white-label alternative?

Evaluate the branded domain and portal, client-account access, usage pricing, payment experience, templates and support ownership together. Synthflow still supports white labeling and subaccounts; its September 15 change removed in-product Stripe reselling. Assistable offers white labeling and usage rebilling on eligible agency plans, with new-account snapshots and configurable client access. Verify the exact client experience, rather than treating a custom logo as a complete resale workflow.

- Brand the client experience
- Set account defaults intentionally
- Separate access from billing

## Review the service from your client's seat.

The client may need to log in, review conversations, fund usage and find help. Define what they should see and what your agency should operate before configuring a portal.

| Client touchpoint | What Assistable documents | What your agency decides |
| --- | --- | --- |
| Identity | Custom logo, colors, favicon and browser title. | The brand and language used for the service. |
| Domain | A custom portal domain. | DNS ownership, cutover timing and recovery route. |
| Help | A link to your own documentation. | Who handles onboarding, billing questions and incidents. |
| Account access | Client members and configurable navigation visibility for non-admin users. | Which users need access and which role is appropriate. |
| Usage and payment | Client wallets and usage rebilling on eligible plans. | Approved client rates, payment setup and exception handling. |
| New-client setup | Snapshots for selected defaults and assistant cloning. | What is reusable and what must be authorized or tested for each client. |

- [White-label configuration](https://docs.assistable.ai/platform/white-labeling)
- [Client wallet and membership](https://docs.assistable.ai/platform/subaccount-wallet)

## A branded portal and a billing system solve different problems.

Synthflow's branding, custom domains and subaccounts remain documented. The missing piece for affected agencies is the former in-product commercial workflow. Moving a domain alone will not fix subscriptions or reconcile usage.

- Keep Synthflow if its client experience works and you want to own customer billing externally.
- Evaluate Assistable if you want branded client delivery and supported usage rebilling in your agency platform.
- Confirm Startup, Growth or Agency eligibility for white labeling and rebilling. Solo excludes these features.
- Review any recurring retainer or included-usage package separately from prepaid usage billing.

- [What Synthflow retained](https://docs.synthflow.ai/reselling-migration-guide)
- [Current Assistable agency plans](https://go.assistable.ai/pricing)
- [Compare billing models](https://www.assistable.ai/resources/synthflow/rebilling)

## Build a repeatable starting point for each client.

Assistable snapshots can apply feature visibility, resource limits, rebilling defaults and assistant templates to new accounts. That reduces repeated setup, but it does not replace a client-specific connection and acceptance check.

1. **Choose the reusable defaults** Set the intended features, resource allowances, billing defaults and assistant template for the service you sell.

2. **Create a test client account** Verify what the snapshot actually creates, including the client billing prompt and non-admin view.

3. **Finish the client-specific work** Add the correct knowledge, calendar, CRM authorization, phone routing and handoff destinations.

4. **Manage existing accounts deliberately** Snapshot changes apply to new accounts going forward. Review existing client accounts individually instead of assuming a template edit updates live deployments.

- [Snapshot scope and testing](https://docs.assistable.ai/platform/snapshots)

## Decide what clients can see, change and consume.

Give clients the controls they need to operate their service. Assistable supports navigation and feature visibility for non-admin users; admins retain visibility. Review user roles and sensitive actions separately from which tabs appear.

| Control | Use it for | Acceptance check |
| --- | --- | --- |
| Member role | Giving the right person access to the correct account. | Sign in as the intended user and inspect the account context. |
| Navigation visibility | Keeping the client interface focused. | Confirm the non-admin view and the separate admin experience. |
| Resource limits | Setting the allowed assistants, messages, numbers or supported resources. | Confirm the exact limit and behavior for the selected resource. |
| Account restriction | Controlling portal access during onboarding or an account review. | Test access behavior separately from whether live agents continue to run. |
| Wallet policy | Funding and charging usage. | Check client and agency balances independently; hiding a tab does not collect a payment. |

- [Permissions and visibility](https://docs.assistable.ai/platform/permissions)
- [Subaccount resource limits](https://docs.assistable.ai/platform/subaccount-limits)
- [Account restrictions](https://docs.assistable.ai/platform/restrictions)

## Make the handoff feel considered.

Bring your brand, a representative client role and the service you sell. Evaluate the portal alongside a real workflow and billing example before inviting the rest of your clients.

- Test the new domain before switching the public client link; retain a documented fallback.
- Provide clear sign-in and payment instructions without asking clients to send passwords by email.
- Show who to contact for billing, configuration and service incidents.
- Verify access with a normal client user, not only the agency administrator.
- Move client groups in stages and reconcile the first operating period before expanding.

- [Plan the complete agency migration](https://www.assistable.ai/resources/synthflow/migration)

## Common questions

### Did Synthflow remove custom domains or white labeling?

No. Its reselling removal notice explicitly retains branding, custom domains and subaccounts. It removed the in-product Stripe and custom-pricing workflow used to bill customers.

### Can Assistable run under my agency's brand?

Eligible plans support custom logo, colors, domain, favicon, page title and documentation link. Review the complete client login, account and payment experience in your pilot.

### Does changing a snapshot update all existing clients?

No. Assistable's snapshot documentation says changes apply to new accounts going forward. Existing accounts need a deliberate review and update process.

### Can I hide advanced tabs from clients?

Assistable documents per-account navigation visibility for non-admin users and defaults through snapshots. Admins still see the features. Test the intended client's view, then review roles and sensitive actions separately.

### Is white labeling the same as reseller billing?

No. White labeling controls the brand and client experience. Reseller billing controls prices, collection and reconciliation. Synthflow retains the former while its in-product Stripe reselling was removed; Assistable supports both branding and usage rebilling on eligible agency plans.

### Can I offer different client packages?

You can configure supported usage prices, account resource limits and client visibility. Scope monthly retainers, included-minute bundles, trials and subscription behavior separately instead of assuming a complete plan designer.

## Sources and review notes

Published by Assistable.ai. Confirm account-specific features, pricing and migration scope with each provider.

- [Synthflow: retained branding and agency capabilities](https://docs.synthflow.ai/reselling-migration-guide)
- [Synthflow: custom domains](https://docs.synthflow.ai/custom-domain)
- [Synthflow: subaccount permissions](https://docs.synthflow.ai/manage-subaccount-permissions)
- [Assistable: white labeling](https://docs.assistable.ai/platform/white-labeling)
- [Assistable: agency plan eligibility](https://go.assistable.ai/pricing)
- [Assistable: snapshots](https://docs.assistable.ai/platform/snapshots)
- [Assistable: permissions](https://docs.assistable.ai/platform/permissions)
- [Assistable: resource limits](https://docs.assistable.ai/platform/subaccount-limits)
- [Assistable: account restrictions](https://docs.assistable.ai/platform/restrictions)
- [Assistable: client billing and membership](https://docs.assistable.ai/platform/subaccount-wallet)

## Related resources

- [A Synthflow alternative built for your agency.](https://www.assistable.ai/compare/synthflow)
- [Keep client billing connected to the service you sell.](https://www.assistable.ai/resources/synthflow/rebilling)
- [Keep HighLevel. Move the AI workflow.](https://www.assistable.ai/resources/synthflow/gohighlevel)
- [Move your agency from Synthflow.](https://www.assistable.ai/resources/synthflow/migration)

[Talk to sales](https://www.assistable.ai/contact?booking_source=%2Fresources%2Fsynthflow%2Fwhite-label)

---
Source: https://www.assistable.ai/resources/synthflow/white-label