Start with the house account
A client sub-account should be a copy of something already proven, not the place where the agency figures the system out. The house account is that source. Pipelines, calendars, forms, and the first automations live there, named so a second person can open the account and see what each piece is for.
Before anything is copied, the house account needs a written order: what is shared, what stays private to the agency, and which assets are safe to push into a snapshot. If that list is only in someone’s head, the next setup will drift.
Point the domain before you invite a client
White-label only holds if the domain, the branded login, and the sending identity are finished before the first client sees the account. A login that still shows the platform name, or a form that sends from a default address, undoes the sale.
The guide we use is short on purpose. Buy or delegate the domain, point the records, confirm the branded link loads, then send a test from the address the client will actually see. Do not hand over a login while any of those steps are still pending.
Messaging has to be ready
Email, SMS, and the phone number are not decorations added after the snapshot. A missed-call text, a booking confirmation, and a follow-up all fail if the number is not approved and the sender is not verified. That work happens on the house account, then it is checked again inside the sub-account.
We do not copy a sub-account until a test message has gone out and a test booking has landed on the calendar. If either one fails, the setup is not finished.
What done looks like
A finished setup is a house account another teammate can open, a domain that loads under the agency brand, and messaging that sends. The client sub-account is created from that, not beside it.
If you want that order built with you on a call, start with a Fulcrum Discovery. We walk the account, name the gaps, and leave you with a setup you can repeat.
