Managing WhatsApp AI agents for fifteen or twenty clients means keeping each client’s numbers, documents and follow-up contacts straight. A change to one account should reach the right assistant and the right team.
The work becomes harder when account managers maintain settings in different places or cannot see who approved the latest update. A central dashboard helps, but your agency also needs a consistent record for each client.
Robofy’s white label WhatsApp AI agents can form part of that service. This guide focuses on day-to-day management across clients: how to organize accounts, review changes and keep follow-up working.
1. Keep a record of each client’s setup
Before adding more accounts, agree on what your team needs to record. Someone covering an absent account manager should be able to find the client’s number, current information and support contact without searching through old messages.
Use the same fields for every client, even when their industries differ.
| Record | What to include | Why the team needs it |
|---|---|---|
| Account and agent | Client workspace, assigned license and relevant agent | Find the correct configuration |
| WhatsApp connection | Business number and its associated account | Check where messages enter the service |
| Approved information | Sources, dates and the client employee responsible | Resolve an outdated or disputed answer |
| Follow-up route | Destination inbox or workflow and responsible person | Investigate a missed enquiry |
| Usage and service scope | Allowance, review schedule and included changes | Manage costs and support commitments |
Keep this record current when a number, staff contact or service changes. The dashboard and the onboarding record should describe the same setup.
2. Separate client workspaces and check access
Create a separate client environment rather than putting unrelated businesses into one knowledge source. Link only the documents and agent configuration intended for that client.
Then test access using the roles your agency and client will use. Check which documents, transcripts and enquiries each role can see. Do this before inviting client staff and repeat it when responsibilities change.
Central management and client separation serve different purposes. Your team needs to work across accounts; a client needs access appropriate to its own service. Confirm the available controls in the selected plan and test them with separate users.
Keep a record of the configuration, access tests and issues that need fixing. Repeat the checks when you change permissions or connect another system. Robofy’s Trust Center provides the published security and privacy information to review alongside the client setup.
3. Configure branding once, then allocate client licenses
Apply the agency branding supported by your reseller plan, including the logo, colors and custom domain. Check what a client sees when signing in and how they contact your team for support.
Preview the login page, dashboard, widget and client notifications before launch. Complete any sender-domain setup required for branded emails, and confirm which templates and design controls your selected plan supports.
Record which license belongs to each active client. When the client adds another business number or assistant, check whether that changes its license, agent or usage requirements.
This gives account managers a clear process for requesting capacity instead of creating new agents without checking the service agreement.
4. Maintain each client’s business information
Use an approved source for each important topic. An older brochure may disagree with the current website, so resolve that difference with the client before using both.
The delivery-policy example illustrates the problem. If a website says “Free delivery on orders over $50” and a PDF says “Delivery calculated at checkout,” the agency needs an approved answer. Uploading the two sources does not settle which policy applies.
Keep internal information separate from material used to answer public enquiries. Staff personal numbers, wholesale costs and internal margins do not belong in the public assistant’s knowledge sources.
For each update, record what changed, who approved it and which agent uses the source. Retest the affected questions after processing the new information. Check the updated answer in a conversation before closing the request.
For clients using an Action Agent, also record the connected system, permitted tasks and credentials used for that client. Keep access limited to the work the client has approved. Test both a permitted request and one the agent should decline or pass to the team.
Robofy’s API tool documentation distinguishes standard tools that work on WhatsApp from visitor approval cards and signed-in visitor authentication, which are web-widget-only. Check the channel requirements before copying a website workflow to WhatsApp.
5. Check enquiry and handoff destinations per client
Qualification fields and follow-up destinations belong to the client’s workflow. One business may need a postcode and service category; another may need project details before a callback.
Submit a test enquiry to each configured destination. Confirm that the receiving team can identify the customer, the request and the next action. Repeat the check when staff or destination settings change.
For human support, define when the assistant should offer a handoff and who checks the requests. Robofy’s human handoff guide explains that a request is created after the customer agrees. Test the shared request queue and any configured team email alert. Individual assignment or ticketing needs the relevant workflow.
Keep service commitments specific. Agree with each client on who responds and the time they can support. Have the receiving team confirm how it will contact the customer after an alert arrives.
6. Keep branch information tied to the right location
A client with several branches may have different hours, addresses, staff and booking arrangements at each location. Organize those differences before enabling answers about the whole business.
If one WhatsApp number serves several branches, establish how the conversation identifies the relevant location before giving a location-specific answer. If branches use separate numbers, check the number-to-agent mapping for each one.
Test questions where the branch is missing or ambiguous. Review what happens when a customer changes the requested location during the conversation.
Reuse the agency’s setup checklist across industries, while keeping the business information and follow-up process specific to each client. A hotel and an electrical contractor need different answers even if your team manages them from the same panel.
7. Review shared usage alongside client commitments
Robofy’s agency pricing distinguishes client licenses, agent allowances and shared AI credits. Track these against the services your agency has sold.
A seasonal increase in one client’s conversations can use more of the shared allowance. Review that usage with the cost of training, the other active clients and the process for approving top-ups.
Tell clients what their own allowance includes and what happens if their needs change. Record who can approve additional usage or integration work.
Check the current plan’s support entitlements and account for the work your own team will provide, including content updates, troubleshooting and integration maintenance.
8. Use the same acceptance record for the first five clients
Use the following suggested acceptance checks for each client and keep the results with its setup record.
| Check | Evidence to keep |
|---|---|
| Business scope and information | Client-approved topics, sources and escalation contact |
| Workspace and access | Correct content linked; agency and client roles checked |
| WhatsApp connection | Incoming question and outgoing reply checked on the intended number |
| Conversation quality | Known questions, follow-ups and missing-information cases reviewed |
| Enquiry delivery | Receiving team confirms the request and its next action |
| Changes after launch | Named reviewer, update history and unresolved issues |
Choose questions that cover the client’s main services, ambiguous requests and cases that need a person. Agree on a follow-up response time the client’s team can meet.
Review early live conversations on an agreed schedule and use them to correct information or routing problems. Keep those changes in the same account record so the next reviewer can see what happened.
Plan staff changes and client departures too. Remove access when a person’s role ends, update notification contacts and revoke credentials that are no longer needed. If a client leaves, agree how to transfer its number and records where supported, disconnect agency integrations and handle retained data under the service agreement.
Explore Robofy’s white label WhatsApp AI agents, review the account controls and run these checks on a test client before adding more accounts.