Managing many client accounts in one chat automation tool
Short answer: ManyChat (a chat automation tool for Instagram, Facebook Messenger, WhatsApp and other channels) describes separate workspaces for each client, reachable from your main account, with user roles for your team and for clients. The safe structure is one workspace per client, owned by the client, with you as an invited administrator, a naming rule, and a template workspace you copy from. Check two things before you quote: whether each workspace needs its own paid plan, and the fact that no white label option (where the tool shows only your own brand) is listed.
You run bots for several clients and you want one tidy way to keep them separate, keep them yours to manage and theirs to own, and hand them over cleanly if a client leaves.
I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.
Give each client their own workspace, named by a fixed rule, with the client as the owner of the account and your agency added as an administrator. Keep a template workspace with your standard flows and copy from it. Put billing and handover rules in your contract before the first flow goes live. This page covers how to set that up and what to confirm with ManyChat before you promise anything.
Here is what ManyChat itself says. Its own agency page says it offers separate workspaces per client that are easy to reach from your main account, user roles for team and clients, and a way to reuse flows for new clients. It lists no white label option. Check with ManyChat support whether each client workspace needs its own paid plan, as pricing rules change. Meta (the company behind Facebook, Instagram and WhatsApp) sets the platform rules the tool must follow.
This page may contain affiliate links from which Blur Studio earns commissions.
Account structure options
There are three ways agencies organize this. Only one is a good default.
| Structure | How it works | Problem |
|---|---|---|
| One workspace per client, client owns it | Client creates the account, adds you as administrator, you build | Needs a little setup from the client, but handover is easy |
| One workspace per client, agency owns it | You create and hold the account, and connect the client's Instagram and Page | Hard to hand over, and ManyChat's terms expect the business owner to be named as administrator |
| Many clients in one workspace | All client pages and bots live together | Contacts, tags and billing mix. Avoid it |
ManyChat's terms of service (effective 1 April 2026) say an agency must identify the business owner as an administrator on the account and on the connected Facebook, Instagram, WhatsApp and Telegram pages. The business owner is the account's representative. The agency keeps the rights in the flows and templates it built. On the end of the relationship, the business owner tells ManyChat and, once the account is transferred, is responsible for the fees. Read the current terms yourself, since they change, and this is information, not legal advice.
The first row is my default. It keeps data, billing and the relationship with the platform in the client's name, and it makes your exit simple.
The limits to know before you promise anything
- No white label option is listed. Do not tell a client the tool will carry only their branding or yours. On ManyChat's Free plan, ManyChat's own branding appears on messages, and removal starts on a paid plan, as of November 2026.
- Billing per workspace needs a check. ManyChat's older billing help said a paid plan was bought per account, not shared across accounts. For the current plans, ask ManyChat before you quote.
- Plans and prices change. As of November 2026, the pricing page showed five plans in US dollars, from Free (25 active contacts) to Advanced ($139 a month billed yearly for 25,000 active contacts). An active contact is a person who exchanges messages with the account in the month. The price depends on the billing country. Accounts created before 2 March 2026 may be on older pricing.
- Seats are capped by plan. Pro includes 3 users, Business 5, Advanced 10. Extra inbox seats were listed at $25 each on Pro and higher.
- Platform rules are Meta's. ManyChat says it cannot reverse a ban or restriction on an account. See avoiding account bans.
For the wider picture of what the tool offers agencies, read ManyChat for agencies.
Naming, templates and permissions
Naming
A fixed rule saves you every week. Use the same pattern in every workspace and in every flow: Client name, channel, purpose, version. For example, "Hollis Dental, IG, FAQ, v3". Tags follow the same logic: a short prefix such as "src-" for source (src-comment, src-story) and "st-" for status (st-hot, st-booked). Never rename in the middle of a campaign.
Templates
Keep one master workspace that belongs to you, and build your standard flows there: lead capture, FAQ, booking and a comment-to-DM flow. ManyChat's page describes copying existing flows for new clients. After a copy, check these before anything goes live:
- Client name, hours and links in every message.
- Triggers and keywords, so two clients never share one word on one account.
- Where lead details are saved, and who can see them.
- The handover message and the person it notifies.
Write a version note each time you change a master flow, and keep a log of which clients run which version. For the template side in more depth, see finishing a half-built chatbot or automation.
Permissions
- Give each of your staff the lowest role that lets them do the job, and remove them when they leave the project.
- Billing permission is a per-member setting, so keep it with the client's owner or admin.
- Give the client a role that lets them read conversations and leads, but not delete flows.
- Use a shared agency login for nobody. Named users only, so you can tell who changed a flow.
Billing and handover
Billing
The cleanest model is that the client holds the card and pays the tool, and you invoice your own fee separately. This is the pass-through model in how to price chatbot work for clients. If you hold the plan yourself, carry the risk of a busy month, because contacts above the included number cost extra, and ManyChat's pages list a fee per extra contact. See contacts count and billing surprises.
WhatsApp messages are charged separately from a Wallet (a prepaid balance inside ManyChat), and SMS (text messages) goes through the client's own Twilio account (an SMS provider), so tell the client both are outside your fee.
Handover
Write the exit rules at the start. A handover checklist:
- Confirm the client is the account owner and holds the billing permission.
- Export what the tool allows. ManyChat's help says there is no one-click export of all contacts. Routes include exporting data collection answers, sending contact rows to Google Sheets (an online spreadsheet), or sending full contact data to a server with an external request (a message from ManyChat to your own server, which needs some coding).
- Hand over a flow map: a one-page list of every flow, trigger, tag and what it does.
- Remove your staff and agree the last date you are responsible for changes.
- Check who owns the flows. Under ManyChat's terms, the agency keeps the rights in what it built, so agree in the contract whether the client gets to keep using them.
The contract points are covered in contracts for chatbot work.
A small example with made-up numbers
An agency runs 8 clients. Each client's workspace is on a plan the client pays. Client A is a dental clinic on Pro billed yearly at $29 a month, with 2,500 active contacts included. In a busy month 2,900 different people message it. The 400 extra contacts cost $0.038 each, about $15, so the clinic's bill is about $44. The agency's invoice is separate. Because the clinic holds the card, the agency does not carry the $15. The numbers are made up. Check ManyChat's pricing page for your plan.
Failure modes to plan for
- The wrong account. A flow is edited in client B's workspace while you think you are in client A's. A colour or a name prefix on each workspace helps, and so does a rule that nobody edits live flows without checking the name in the corner.
- The departed staff member. Someone leaves your agency and still has access to ten client accounts. Remove access the same day, and keep the access list in one sheet.
- The billing surprise. A client's post goes viral, active contacts pass the plan allowance, and the extra fee arrives on a card the client forgot about. Set up the usage notices that ManyChat's blog says it sends at 70, 90 and 100 percent of the allowance, and agree who pays.
- The shared keyword. Two flows react to the same word on one account. Keep a keyword list for each client.
- The silent trigger. A flow stops firing after a platform change and nobody notices for a week. The monthly test catches it. See the not-triggering fix checklist.
Monthly checklist
- Each client's active contact count against the plan, with an alert at 70 percent of the allowance.
- One test comment and one test DM per client, to confirm triggers still fire.
- Review who has access and remove old users.
- Note any Meta or ManyChat change that affects a client.
- Send the client's report. See a monthly report clients understand.
Who should skip this structure
If a client needs a bot under their own brand with no vendor name anywhere, ManyChat's listed options do not cover it, and a custom build is a better fit. If you manage 2 clients, a spreadsheet and a naming rule are enough and you do not need an elaborate system. If a client's main channel is WhatsApp with a team of agents, look at the tools in ManyChat alternatives.
How I'd approach this
I would start with one workspace per client, owned by the client, and a named list of who has access. I would build my master flows once, copy them, and log every version. Before I signed a second client, I would ask ManyChat in writing whether each workspace needs its own plan, and keep the answer with the contract.
When you are ready to try it, open a test workspace on a free ManyChat account and read ManyChat's agency page for the current wording. For how to sell the service itself, see adding DM automation as an agency service. If you would rather have a custom setup, Blur Studio builds the custom version: AI agents that use your business knowledge, CRM (customer record) and calendar connections, finishing a half-built flow, and ongoing care. See what that includes.
Questions people ask
Can I manage several client accounts from one ManyChat login?
ManyChat's agency page describes separate workspaces per client that are reachable from your main account, with user roles for your team and for clients. Check the current page, and ask support how billing works for each workspace. Meta, the company behind Facebook and Instagram, also sets rules the account must follow.
Does each client workspace need its own paid plan?
Check with ManyChat support in writing before you quote. ManyChat's older billing help said a paid plan was bought for each account separately, and the current plans may differ.
Is there a white label option?
No white label option is listed on ManyChat's pricing or agency pages. Do not promise a client their own branding. Branding removal on messages starts on a paid plan.
Who should own the client's account?
The client. ManyChat's terms say an agency must name the business owner as an administrator on the account and on the connected pages. That also makes handover simple. See contracts for chatbot work.
How do I hand a client's bot over if we part ways?
Make the client the owner, export what the tool allows, give them a one-page map of flows and tags, and remove your staff. There is no one-click export of all contacts, so plan the export early.
How do I stop one client's flow from breaking another's?
Keep one workspace per client, never share keywords across clients in one account, and copy from a master template with a version note. Test every client monthly. See the not-triggering fix checklist.
Is ManyChat the only option for agencies?
No. Chatfuel (a chatbot builder) has agency plans, and Respond.io and WATI (shared inbox tools for team chats) offer other models. Compare them in ManyChat alternatives.
More in this topic: ManyChat: for agencies (8 guides) →