An agency tests a voice workflow in one GoHighLevel subaccount and copies the configuration to another client. A hidden contact or calendar identifier still points to the first account.
Subaccount separation needs an explicit mapping of identities, configuration, credentials, and data paths. Branding the receptionist with the new client's name does not establish isolation.
Inventory every account-specific reference
List calendars, custom fields, pipelines, owners, phone destinations, knowledge sources, and connected credentials used by the workflow.
| Reference | Migration or isolation check |
|---|---|
| Calendar | Belongs to the authorised client and service |
| Custom field | Correct local identifier and meaning |
| Follow-up owner | Active staff member in the intended account |
| Credential | Correct account and allowed capability |
| External webhook | Receives a trustworthy client context |
Do not assume identical display names imply interchangeable identifiers.
Resolve client context from trusted configuration
The integration should authenticate the source and determine which client it represents. A model-provided account ID or caller-supplied business name should not grant access to another client's records.
Keep shared template logic separate from client-specific values. A versioned configuration map can make copied references visible, but it still needs validation against the actual destination account.
Verify current supported account and integration behaviour with HighLevel's documentation. A template export alone does not prove that every connected secret or external resource migrated safely.
Carry isolation into logs and background work
Client context should follow queued operations, result storage, recordings, report exports, and support views. A correctly scoped live API call can still leak data through a shared cache or unfiltered export.
The agency client-isolation guide covers those wider surfaces.
Test with two deliberately different clients
Create fictional client configurations with distinct calendars, field values, and staff destinations. Run the same enquiry through each and inspect the final records.
Then supply a mismatched identifier and verify denial without changes to either account. Include a delayed result from one client while the other is active.
Keep production and staging references separate too. A test run should not reach a real client's on-call employee simply because a copied number remained in a template.
Shared infrastructure can reduce maintenance, but it makes account-boundary tests essential. Separate deployments can reduce some shared-state risks while adding operational cost. Choose with evidence rather than a default preference.
Subaccount questions
Is a new client label enough to reuse a workflow?
No. Validate every account-specific reference and secret.
Can the AI select the tenant from its own interpretation?
Derive authority from trusted configuration and authentication.
What should handover include?
Provide the scoped resource inventory and two-client test results in the agency delivery pack.