Contracts for chatbot work: platform risk, who owns the flows and the Meta rules

By Ranjit Bhinge, founder of Blur Studio · Updated · 10 min read

Short answer: A contract for chatbot work needs six clauses beyond the usual scope and payment terms: a platform-risk clause (Meta, the company behind Instagram, Facebook and WhatsApp, can limit or close an account and you cannot stop it), who owns the flows and the contact data, who holds the admin login, consent and message rules, handover when the client leaves, and a limit on what you promise. This page gives plain-language wording to adapt and discuss with a lawyer. It is information, not legal advice. Sign online so the file is dated and stored.

Ranjit Bhinge

You are about to sell DM automation to a client, and you want a contract that covers what happens when Meta limits their account or they leave.

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.

The short answer: add a platform-risk clause, an ownership clause, an access clause, a consent clause, an exit clause and a no-guarantee clause. A normal marketing contract does not cover these, because chat automation depends on someone else's platform and on a list of contacts that belongs to the client.

Below is what each clause does, sample wording in plain English, and a checklist to run before you sign. Wording here is a starting point, not legal advice. Have a lawyer in your country review it, and check local law. A chatbot is a program that replies to messages. TikTok, the short-video app, also has business messaging and its own rules. A flow is the set of steps it follows. An opt-in is a person agreeing to receive your messages. A DM is a direct message.

This page may contain affiliate links from which Blur Studio earns commissions.

Why chatbot work needs its own clauses

Three facts make this work different from a normal retainer.

  • The platform can say no. Meta sets the rules for Instagram (the photo and video app), Messenger (Facebook's chat app) and WhatsApp (the messaging app), and tools built on top of them cannot override Meta. ManyChat, a tool that automates replies on these channels, says in its Help Center that it does not control Meta's rules, has no hotline to reinstate accounts, and cannot reverse bans or restrictions. It lists too many automated messages too quickly and aggressive copy-paste comment automation among the common triggers. Your contract has to say who carries that risk.
  • The tool has its own terms. ManyChat's terms of service (version effective 1 April 2026) say the customer is responsible for account activity, messages and consent law compliance, and that the tool may suspend or end an account. They also include a section on agencies, covered below.
  • The contacts belong to the client's customers. Names, phone numbers and chat history are personal data. Who stores them and who may use them has to be written down.

Clause 1: platform risk

Goal: the client understands that Meta, WhatsApp or TikTok can limit or close an account, and that following their rules lowers the risk but never removes it.

Plain-language wording to adapt:

The Client understands that Instagram, Facebook, WhatsApp and TikTok are run by other companies, which can change their rules, limit features, restrict messaging or close accounts at any time. The Agency will build flows to follow those companies' published rules as of the date of build, and will not use tactics the rules forbid. The Agency does not control these companies and does not promise that any account will stay free of limits. Fees remain payable if a platform limits or removes a feature for reasons outside the Agency's control, but the Agency will, at no extra charge for the first [2] hours, help prepare an appeal or a revised flow.

What backs this up in the rules: for Messenger and Instagram, Meta's policy says the standard messaging window is 24 hours after a person's action, bots must answer input within 30 seconds, and automated chats must say they are automated where the law requires it. WhatsApp's business policy says you may only contact people who opted in, and user blocks and reports can cap how many messages you send. A template is a pre-approved message format that WhatsApp requires for messages outside the 24-hour window. Its enforcement page lists warnings, then short sending blocks, then longer blocks, then locks. As of November 2026, check Meta's current rules, since they change. See the 24-hour messaging window and whether Instagram DM automation is allowed.

What not to write

  • "Your account will not be banned." You cannot know that.
  • A fixed number of messages per hour you call safe. Meta publishes no such figure for normal DMs, so any number would be invented.
  • "We are an official partner" unless you are, and can show it.

Clause 2: who owns the flows and the contacts

There are two things to split: the work you build and the data it collects.

ItemCommon arrangementWhat to decide in writing
Flows, templates and sequences you builtAgency keeps the rights to its reusable methods; client gets a licence to use what was built for them, or full ownership after paying in fullWhich of the two, and when it starts
Contact list and chat dataClient owns itWhere it is stored and who may export it
The tool accountClient-owned account or an account the agency runs for the clientWho is the account owner and who pays
The social accounts (Instagram, Page, WhatsApp number)Always the client'sThe client keeps admin rights at all times

Wording to adapt:

All customer contact details and message history collected through the flows belong to the Client. The Agency may use them only to deliver the services. The Agency retains ownership of its general methods, templates and know-how. On full payment, the Client receives a perpetual licence to use the flows built for it, and the Agency will provide a copy or export in a form the tool allows.

ManyChat's terms already point in this direction for agencies. As of its 1 April 2026 terms, an agency must name the business owner as an administrator on the account and on the connected social pages, the business owner is the account's representative, and the agency keeps its rights in the flows and templates it built. If the relationship ends, the business owner tells ManyChat and is responsible for fees after the account moves. Your contract should match that, so the two documents do not conflict. Read the current terms yourself before relying on this.

Do not promise a full export

ManyChat's Help Center says there is no one-click full export of all contacts. You can export collected responses, push rows to Google Sheets, or send contact data to a server through an external request. So write "an export in a form the tool allows", not "a full copy of everything". See cancelling ManyChat and exporting contacts.

Clause 3: access, billing and who pays the tool

Decide this before work starts, because it is where disputes begin.

  • Admin access. The client keeps owner or admin rights on the Instagram account, the Facebook Page and any WhatsApp business account. You work as an added user.
  • Tool subscription. Either the client pays the tool directly, or you pass the cost through at cost, or you bundle it into a fee. If you bundle it, say what happens when usage rises. ManyChat counts active contacts per billing month and charges per extra contact above the plan allowance, so a viral month can raise the bill. Prices and plans vary by billing country, so check ManyChat's pricing page. See billing surprises and the agency margin check.
  • Message fees. WhatsApp template messages are charged per delivered message by category and country, taken from a prepaid wallet. Say who tops it up.
  • Commission rule. ManyChat's partner terms bar agencies from earning commission on accounts the agency itself operates and pays for. If you are in a partner program, read its terms before you write any referral language into a client contract.

The client is the business that contacts people, so the client carries most of the duty to have permission. But you build the flows, so you share the work.

The Client is responsible for having lawful permission to message the people on its lists and for the accuracy of the offers and claims in its messages. The Agency will build opt-in and opt-out steps, an automated-service notice where required, and a clear route to a human. The Client will tell the Agency promptly about any complaint or opt-out request received outside the chat.
  • WhatsApp's policy says the business is responsible for its opt-in method and for meeting applicable laws, and that automated flows must offer a clear way to reach a human.
  • Meta's Messenger policy recommends telling people they are talking to an automated service, and requires it where the law does. It flags California and Germany as examples.
  • For texting (SMS), consent and quiet-hours rules vary by country and are changing in places. This is information, not legal advice. Check local law.

If the flows use AI to write replies, add a line that the client approves the topics the AI may answer and that a person handles sensitive matters. See AI replies in DMs and, for contract wording around AI work generally, the AI clause in an agency contract.

Clause 5: what happens when the client leaves

  1. Notice. State the notice period, such as 30 days.
  2. Handover list. Flow screenshots or documentation, the list of triggers and keywords, the tag list, the contact export route, and the login transfer steps.
  3. Account transfer. The client takes over the tool account, or sets up its own and you rebuild for a fixed fee.
  4. Cut-off. You remove your own access within a set number of days.
  5. Last bill. The client pays any tool fees that fall due after handover. A cancelled ManyChat plan stays active to the end of the billing period, and a bill already generated can still go through, so time the cancellation.

Clause 6: promises you must not make

  • No guaranteed leads, bookings, sales or follower numbers.
  • No guaranteed uptime of the platform. Meta or the tool can have outages. ManyChat's status page, for example, listed an open Instagram-related incident affecting the Follow to DM trigger as of November 2026.
  • No guarantee that AI replies are correct. ManyChat's AI terms say output may be inaccurate.
  • A cap on your liability, such as fees paid in the last three months. Ask a lawyer how to word this where you live.

Signing the contract online

Once the wording is settled, send it for signature online so you have a dated, stored copy. QuickSigner, an e-signature service where you upload a document, add signers and send a signing link, is one option. As of November 2026 its pricing page lists a free plan with 5 documents a month, a Business plan at $5 per user per month, and a Professional plan at $15, with signers not needing an account. Whether an electronic signature is valid for your contract depends on your country and the document type, so check local law. For a wider look, see QuickSigner pricing and limits and putting your own brand on client contracts. If you try its free plan first, test it on a dummy contract. Any e-signature tool that records who signed and when will do the job, so compare before you pay.

Checklist before you sign

  1. Scope lists channels, flows, number of changes per month and what is out of scope.
  2. Platform-risk clause is in, with no promise about bans.
  3. Ownership of flows, contacts and accounts is written down.
  4. The client keeps admin rights on every social account.
  5. Tool billing, overage and wallet top-ups have a named payer.
  6. Consent, opt-out and human-handoff duties are split between you and the client.
  7. Exit steps and a handover list are attached.
  8. No guarantees of results, and a liability cap.
  9. A lawyer in your country has read the final version.

A quick test

Give the contract to a colleague and ask three questions. If Meta limits the client's account in month two, who pays and what do we do? If the client leaves in month six, what do they get and when? Who owns the contact list? Pass: they find the answer in under a minute each. Fail: they have to guess. Edit until they stop guessing.

When you may not need all this

  • A one-off build with no ongoing care. You still need ownership and no-guarantee clauses, but exit terms can be short.
  • A client who runs the tool themselves. If they hold the account and you only train them, the access clause matters more than the platform-risk clause.
  • A large client with its own legal team. Use their paper and add the six clauses as a schedule.

How I'd approach this

I would keep one master agreement, one chatbot schedule with the six clauses, and one handover list. I would have a lawyer review it once, then reuse it. I would insist that the client owns the social accounts and holds admin rights, because that single rule prevents most exit fights. I would also read the tool's current terms before each new client, since they change: ManyChat's terms, acceptable use policy and AI terms were all updated in the past year.

If the contract is the easy part and the build is the problem, Blur Studio builds the custom version for clients: AI agents that use your business knowledge, CRM and calendar connections, finishing a half-built flow, and ongoing care. See what that includes. For a general freelancer and agency template, this contract template is a good base.

Questions people ask

Who owns a chatbot after the agency builds it?

That depends on your contract, so write it down. A common split is that the client owns the contact data and social accounts, while the agency keeps its general methods and gives the client a licence, or full ownership after payment, for the flows built for them. This is not legal advice, so have a lawyer review it.

Should the contract say what happens if Meta bans the account?

Yes. Say that platforms can limit or close accounts, that you follow their published rules but cannot control them, and what support you give for an appeal. Never promise an account will not be banned. Read safe automation practices for agencies.

Can I put the client's contacts in my own tool account?

You can, but it makes handover harder, and the client may expect the data to be theirs. Many agencies use a client-owned account with the agency added as a user. ManyChat's terms for agencies say the business owner should be named as an administrator. Check the current terms.

Do I need the client's consent to message their customers?

The client, as the business that contacts people, needs lawful permission, and the platforms require opt-in or a message from the person first. Rules differ by country and channel. Check local law and each platform's current rules.

Can I promise to export all contacts when the client leaves?

Be careful. ManyChat's Help Center says there is no one-click full export, and lists routes through collected data, Google Sheets or an external request. Promise an export in a form the tool allows.

Is an electronic signature enough for this contract?

Often yes, but it depends on the country and the type of document. Use a tool that records who signed and when, and check local law. QuickSigner pricing and limits shows one option.

Who should pay for the chatbot tool subscription?

Either works if it is written down. Paying directly keeps the account in the client's name. Bundling it makes pricing simple but needs a rule for usage spikes. See how to price chatbot work.

More in this topic: ManyChat: for agencies (8 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…