Documentation

Account and billing

Multiple branches

Run several locations under one business account with shared billing, per-branch workspaces, branch members and roles, and a merged inbox.

Last updated: 2026-09-29

A business account groups several branch workspaces for a business with more than one location. Each branch keeps its own channels, conversations, contacts and settings. One branch pays for everything, and the plan allowances are pooled across the account.

How it works#

  • Every branch is its own workspace with its own data. Nothing is copied or merged into one database.
  • One branch is the billing anchor, the payer. Its plan, AI plan credits, AI wallet, storage and automation counters are shared by all branches. Branch staff see a reduced view of the plan without prices.
  • The WhatsApp wallet is not shared. It stays with the branch that owns the number.
  • A branch never gets its own subscription, Sandbox plan, free trial or referral binding.

Pricing and limits#

Each branch costs the plan price and brings the full plan allowances. Prices are on Plans and billing.

Example: 3 branches of OperationsResult
Price3 x $39 = $117 per month
Included seats15 (extra seats are still $5 each)
Storage150 GB
Automation runs15,000 per month
Active automations30
AI creditsA separate pooled add-on, not multiplied by branches
LimitValue
Branches, self-serveUp to 20
Branches on a trialUp to 2
Branches on Sandbox1
Branches on EnterpriseBy contract
Team size to switch a workspace to multi-branch200 members or fewer

Annual billing charges the platform price for 11 months, as for any workspace.

Set up multiple branches#

New workspace

  1. In the setup wizard, under "How is your business organized?", choose Multiple branches.
  2. Optionally type the name of your first branch.
  3. Finish onboarding. You land on the account's Branches page, where you add the other branches.

Existing workspace

  1. Sign in as an owner or admin.
  2. Open Settings, then Workspace setup, and find the Business structure card.
  3. Review the preview of who becomes what, then confirm. This cannot be undone.

The switch is refused if you are not an owner or admin, the workspace is already in an account, the subscription is not active, the team is above 200 members, or the plan has fewer seats than current members.

When you switch, your workspace becomes the billing anchor and keeps its data, channels, subscription and wallets. You become the account owner, other workspace admins become account admins, and everyone else keeps their role in that branch.

Add branches and pay for them#

  1. Open Plan & usage in the paying workspace (or the account's Billing page).
  2. Raise the Branches stepper and complete payment. Mid-cycle additions are prorated.
  3. Open the account's Branches page and create the branch.

A purchased slot is reserved when you request a branch, and the branch workspace is created shortly after. Archiving a branch frees its slot, but you do not get a refund for it. Reactivating an archived branch needs a free slot. The billing anchor cannot be archived.

Reducing the number of branches is scheduled for renewal and is refused while more branches are set up than you are choosing. Cancelling to Sandbox keeps existing branches readable but adds none.

Account pages#

Members of an account see a branch switcher in the sidebar. The account area has these pages:

PagePurpose
Account chooserPick which account to open
OverviewAccount-level summary
InboxOne merged inbox across the branches you can read
BranchesCreate, archive and reactivate branches
MembersManage people and their branch access
BillingSubscription and purchases for the account
AuditA log of account actions and their outcomes

Roles across branches#

There are two layers of roles.

Account roles

RoleCan do
OwnerEverything at account level: members, branches, billing, audit, export and offboarding
AdminRead, manage members and branches, read billing and audit, export. Manages billing only if the owner allows it.
Billing adminRead the account and manage billing
MemberRead the account

Branch roles. A person can be granted a role in each branch: branch admin, manager, agent, designer, finance or viewer. Owners and admins appear in a branch through their account role. A branch admin has all workspace permissions except exporting or offboarding the workspace and managing billing, and can grant only roles below their own. The role definitions match Team, roles and permissions.

Branch members and seats#

  • A seat is one person per account, shared across all their branches.
  • Invitations reserve a seat before the email goes out.
  • In a branch, the Team page cannot invite, remove or re-role people. Team changes are made from the account's Members page.
  • Revoking a branch grant takes effect on the person's next request.

Gotchas#

  • Switching to multi-branch is one-way.
  • Extra seats are pooled, but per-branch usage caps do not exist. One branch can use up the shared storage or automation runs.
  • A WhatsApp number, Messenger page or Instagram account active in one branch cannot be activated in another workspace.
  • A branch in read-only or archived state keeps its history but accepts no new changes from staff.
Multiple branches | Sela docs | Sela