Managing Sub-Accounts

Sub-accounts are the individual client accounts that run on your white label platform. You can create them manually, assign plans, log in as any client, and manage every aspect of their account from your dashboard.
Creating Sub-Accounts

There are two ways to create a sub-account:
- From the dashboard --- click the add button in the Sub-Accounts section and fill in the client details.
- From a contact page --- open any contact record and create a sub-account directly from there.
Accounts created through Signup Forms are generated automatically and also appear here.
Assigning Plans
When you create or edit a sub-account, assign it to one of your SaaS plans. This determines what services the client can access and how they are billed. You can change the assigned plan at any time.
Welcome Survey
When people sign in to a new sub-account, they see a short welcome survey, sometimes called the onboarding wizard, until one of them finishes it. You can turn it off so your clients go straight into the app.
- For every new account on a plan --- turn off the plan's Welcome survey switch. See SaaS Plans and Pricing.
- For one new sub-account --- in Settings > Sub-Accounts > Create Sub-Account, on the Package & Payment step, pick the plan, then turn off Show the welcome survey. The same switch is in the Purchase Product dialog on a contact who has no account yet, once a plan is selected; it applies when you click Complete Purchase. It starts from the chosen plan's setting. A sign-up link made with Generate Link follows the plan's setting instead.
- For a sub-account that already exists --- in Settings > Sub-Accounts, click Edit Sub-Account (the pencil) on its row, turn off Show the welcome survey and click Update Sub-Account. The switch is offered until someone on that account finishes the survey.
An account that skips the survey does not get its country, time zone and currency from it, and your workflows that use the Onboarding Completed trigger never run for it. You can give the company name when you create or edit the sub-account.
Accessing Client Accounts

- Login as --- instantly access any sub-account to configure it, troubleshoot issues, or set things up on behalf of your client. You see exactly what the client sees.
- Generate login link --- create a one-time login URL that you can send to a client. The link grants access without requiring the client to remember a password.
Managing Accounts

From the sub-accounts list, you can:
- Edit --- update client details, change the assigned plan, or modify account settings.
- Deactivate --- switch the sub-account off without losing anything. Nobody can sign in to it (or to its own sub-accounts), and its API keys and connected AI clients stop working. Its plan is not cancelled and nothing is deleted. Reactivate it at any time.
- Delete --- remove the sub-account and its owner contact (that contact is the sub-account's login, so it always goes with it). Its plan, its add-ons and any other subscription that contact pays you for are cancelled at once, with no refund, and its wallet balance is not refunded. Invoices and payment history are kept.
- Restore --- for 7 days after a delete, a person with the Owner or Admin role opens Activity > Audit Log, finds "Contact Deleted: [owner name]" and clicks Undo. That brings back the sub-account and its owner contact, but not the plan or any cancelled subscription, and the owner's API keys stay revoked. After 7 days it is permanent: phone numbers are released, and the websites' hosting and the custom domains are removed.
Billing and Contact View


Each sub-account also appears as a contact in your CRM. From the contact page, you can view:
- The Billing tab with subscription details and payment history.
- Current plan assignment and usage data.
- All communication history with that client.
Clean up test sign-ups with an AI assistant (MCP)
Three tools let AI, or any AI client you connect over MCP, do this work in chat instead of on this page.
| Tool | What it needs |
|---|---|
list_sub_accounts | Settings access. Lists your own sub-accounts, newest first, 25 a page, with the owner contact, the status and the plan. Optional search. |
set_sub_account_status | The Sub-Accounts Update permission, and the Owner or Admin role or a role granted "Manage sub-accounts". Deactivates or reactivates one sub-account. |
delete_sub_account | The Sub-Accounts Delete permission. Deletes one sub-account and its owner contact. |
Each of them names the sub-account through one argument, sub_account, which takes its name,
its company, its owner's email or its id. If several sub-accounts match, the tool lists the
matches with their ids instead of guessing. Only your own direct sub-accounts can match.
Two calls, always. Deactivating and deleting both need your own confirmation: the first call changes nothing and states exactly what would happen, and the assistant repeats that to you. Only when you say yes does it send the same call again with the confirmation, and AI also shows you an approval card first. Nothing happens on a question.
A delete can be refused. When any of these is true, nothing is deleted and the assistant tells you why, because a person has to sort it out first:
- the sub-account has sub-accounts of its own, which would keep running with nobody able to sign in;
- its owner contact also owns another account, which deleting the contact would cancel the plan of and schedule for deletion;
- its owner contact signs in to a different account, or is you;
- it is already being deleted.
In each of those cases, deactivating keeps everything and stops anyone using the account.
Example. "Delete the test sign-ups from yesterday" becomes:
list_sub_accountswith{"search": "test-delete"}, to find them;delete_sub_accountwith{"sub_account": "jane@example.com"}, which deletes nothing and lists what would go;- the same call with
"confirm": trueonce you have said yes (plus"cancel_other_subscriptions": truewhen the list named other subscriptions that contact pays you for and you agreed to cancel those too).
A test payment a card declined leaves a contact with no sub-account at all: nothing was
provisioned, so delete_contact removes it. A sub-account you just deleted needs no follow-up
on its owner contact, because that contact went with it.
Connecting your own AI client: MCP setup.
Next Steps
- Signup Forms --- set up self-serve checkout so clients can sign up without manual account creation
- Payment & Billing --- manage transactions, subscriptions, and revenue tracking