Client assets and responsibilities become mixed.
Work in the intended client workspace and document who owns each sender and asset.
For Agencies
Help clients prepare templates, campaigns, and response processes while keeping workspace access, business numbers, and responsibility explicit.
See how the workflow works
Is this your day-to-day?
Work in the intended client workspace and document who owns each sender and asset.
Agree the client's response owners before sending any messages.
Keep configured journeys, notes, and next steps available to authorised teammates.
How it works
Start with a focused journey, agree who owns each step, and test it before expanding.
Define the business owner, workspace, connected number, and team access.
Create the client's templates, audience plan, and response process in the right workspace.
Review content, permissions, sample variables, and ownership with the client.
Document next actions and review the workspace activity with authorised client teammates.
A customer example
See what your team collects, who takes responsibility, and how the next action stays connected.
“Can you help us launch a customer re-engagement campaign?”
Illustrative scenario, not a live customer conversation. Actions depend on your configuration.
The client confirms the audience, sender, access, and message purpose.
Templates and sample content are reviewed before the client approves launch.
The people answering replies know their ownership and follow-up process.
The outcome to aim for
Client-specific assets and response responsibilities remain in the correct workspace.
The tools behind the workflow
Use the correct client workspace for contacts, senders, templates, and campaign drafts. Access must be authorised for that workspace.
Explore workspace capabilitiesUse library drafts where appropriate, customise them for the client, and complete the applicable approval steps before sending.
Explore industry use casesDiscuss your client access, reporting, onboarding, and integration requirements. Do not assume white-labelling or cross-client access is included.
Discuss your agency setupBefore your first live conversation
Identify the client business owner and authorised users.
Confirm the correct workspace, business number, and billing responsibility.
Agree the approval, launch, and customer-response process.
Live messaging requires a connected WhatsApp Business Account and applicable Meta setup and approvals. Workspace subscriptions and Meta messaging charges are separate. Custom integrations and automation need configuration.
Questions, answered
Practical answers about the workflow, setup, and what is not automatic.
Do not mix unrelated client data just for convenience. Scope workspace boundaries and authorised access around each client's requirements.
This page does not promise a white-label portal or reseller billing. Discuss the specific commercial and technical requirements with the team.
Templates still need the applicable Meta review and approval for the relevant business account before they can be used as required.
Agree this with the client before launch. Give the authorised response team access to the right workspace and document ownership.
Another team involved in the journey?
Your next step
Bring your use case, source systems, and team requirements. We can walk through the setup and the next steps.