Hiring a ManyChat Expert: What to Check and What to Build First

Hire a ManyChat expert when you need more than one channel, a verified WhatsApp setup, a CRM connection or AI replies; build a simple comment-to-DM flow yourself first. The expert's first project should be one keyword flow that captures an enquiry, tags it and hands a person the chat, on accounts you own.

The mistake is hiring for "a chatbot" and receiving a large, clever flow nobody on your team understands. A small first build, proven on real comments, tells you quickly whether the expert is good and whether automation suits your business. The checks below cover what to ask, what to test and what to keep in your own hands.

Follow me on Instagram@sagnikteaches

Decide first: hire, or build the first flow yourself?

ManyChat's own pricing page shows how low the entry barrier is. The Free plan lets you build automations with up to four live triggers, and offers more than 60 ready-made templates for replying to comments, greeting new followers and sharing links in DMs. It allows 25 active contacts, which are the people you interact with in a month. The Essential plan costs $14 a month billed annually ($17 monthly) for 250 active contacts and unlimited automations, and Pro costs $29 annually ($39 monthly) for 2,500 contacts, adding broadcasts and its AI features. Business is $69 annually ($99 monthly) for 7,500 contacts. The page adds that prices exclude tax and depend on your billing country. For how that scales, see what 500, 2,500 and 7,500 contacts cost.

Connect on LinkedInSagnik Bhattacharya

A rough rule for hiring:

Subscribe on YouTube@sagnikteaches

If you want to see what hitting a big audience does to the plan, what a viral reel does to your ManyChat bill explains it, and is worth reading before an expert quotes.

What to build first: one keyword flow, end to end

The first project should be small enough to finish in days and complete enough to prove the idea. My recommendation, for most service businesses, is a comment-to-DM lead flow:

1. Trigger: a person comments a keyword (for example "QUOTE") on a post or reel.
2. Opening DM: a short reply that thanks them, says what happens next and asks one question.
3. Capture: their need in a button choice or one line, plus an email address if they want details.
4. Tag: a tag for the topic and the source post.
5. Handover: a notification to you or your team, and a clear "a person will reply by [time]" message.
6. Safety exits: a button to talk to a person at any point, and a stop word.

That is the whole first build. No AI, no payments, no branches beyond two or three choices. The setup details are in ManyChat Instagram setup: keyword triggers, opening DM and opt-in.

The worked example: a signage company

Illustration only. A signage company posts a reel of a finished shopfront sign each week. Followers often ask in the comments "how much?" and the owner answers each by hand, an hour or two a week that slips when work is busy. The first project is a flow triggered by the word QUOTE. The opening DM reads:

Hi [first name], thanks for asking about the sign.
To point you to the right person, which is closest?
[Shopfront sign]  [Vehicle graphics]  [Interior / wall]  [Something else]

A second message asks for the rough size or a photo of the site and an email address, tags the person with the product and the post, and tells them: "One of us will message you within one working day." The owner receives a notification and carries on by hand from there. The expert's job is the build, the testing and the handover. Cost-wise, a plain flow like this needs the Essential plan (unlimited automations) or less; it does not need the AI tier.

The opening DM, before and after

Wording is where a first flow most often disappoints, and it is yours to approve. An illustrative contrast for the signage company:

BEFORE (default template tone)
Hey there! Thanks so much for your interest! We have SO many amazing
signs. Click below to learn more about our services and get started today!

AFTER (specific, short, one question)
Hi [first name], thanks for asking about the sign on the reel.
It was a 2 m illuminated fascia for a shopfront.
To get you to the right person, which is closest to what you need?
[Shopfront sign] [Vehicle graphics] [Interior / wall] [Something else]
You can type STOP at any time and we will leave you alone.

The second version names the thing they asked about, asks one question and offers an exit. Ask the expert to draft two or three versions, and pick the one that sounds like your reply by hand.

Portfolio checks that tell you whether they are any good

Screenshots of flows prove little: they show boxes and arrows, not whether the thing behaves. Ask instead for these, in this order.

1. A live demo you can use yourself

Ask for a keyword on their own account (or a client's, with permission). Comment it from your own account and watch what happens. Does it reply within seconds? Does the opening message read like a person? What happens if you reply with something unexpected, like "what's your phone number"? A good flow handles the off-script reply gracefully, even if only by offering a human.

2. A description of what went wrong once

Every experienced builder has a story: a trigger that fired twice, a message that did not send because the person had last interacted over 24 hours earlier, a tag that was never applied. Ask for one, and what they changed. If they have never had a problem, they have not built much.

3. Their answer on messaging windows

ManyChat's help page says that, under Meta's policy, automated messages on Messenger, Instagram and WhatsApp cannot be sent outside the 24-hour window after a person's last interaction. After 24 hours, a 7-day window on Messenger and Instagram lets you send manual messages from the inbox, but automations are not delivered. WhatsApp has no 7-day window; after 24 hours you need approved message templates. ManyChat blocks scheduled messages to people who are outside the window. The right answer from an expert shows they know the rules, and explains how the flow keeps follow-ups inside them.

4. Two references, and what you can ask them

Ask for two past clients you can contact, and ask them: did the flow run without attention, was handover clear, and did they keep control of their own accounts?

The ManyChat site links to its own agency listing ("Hire an agency") for owners who want to hire a company rather than a freelancer, and its community forum is another place to find people and see how they answer questions. Treat both as places to find candidates, not as proof of quality.

Meta account ownership: the check that protects the business

A ManyChat flow runs on your Instagram professional account or Facebook Page, connected to ManyChat. If those accounts sit under someone else's login, you can lose both the flow and the audience. Use this checklist:

• The Instagram account is a professional account created by you, with your business email and two-factor authentication on.
• The Facebook Page it is connected to is owned by your business, not a personal profile of the expert or an employee.
• The expert gets access through Meta's partner access in your business portfolio, where you choose full control or partial access to the Page, not a shared password, and is removed at the end.
• The ManyChat workspace is created under your email, and the expert is added as a team member. Check the user limit for your plan: the Free plan has one user, Essential two and Pro three, so a freelancer may occupy a seat you need.
• Any connected service (calendar, CRM, sheet, email tool) is on your own account.
• You hold a list of every connection, with its owner and where to revoke it.

If an expert insists on building in their own workspace "and transferring later", ask how the transfer happens and what is lost, because contacts, tags and history do not always move with a flow. Build in your workspace from day one.

What goes in a first-project scope and quote

Ask for a written scope with these lines, each priced or marked as included:

I would not give you an hourly rate, because I cannot verify one from a vendor page. Compare quotes on the lines, and expect a first flow of this size to be a small, fixed-price job, not a retainer. If a quote proposes a monthly fee for "managing" a flow that has not been built, ask what is being managed.

What to keep in-house

A flow is a system for starting conversations, not for finishing them. These jobs should stay with you or your team:

• Replies to anything the flow cannot answer. A person should check the inbox at set times each day and say so in the flow ("we reply by 5pm").
• Offers and prices. The wording of what you promise is yours; an expert should not invent discounts or deadlines.
• Tone. Read every message aloud. If it does not sound like your business, change it.
• Tags and what they mean. You decide which topics matter; the expert implements them.
• Weekly review. Ten minutes every week looking at new contacts, drop-off points and anything that confused people.
• Budget watch. The monthly contact count against your plan's limit, so a good week does not bring a surprise upgrade.

For a view of how this choice differs between an Instagram flow and a booking-app bot, see ManyChat, Meta's agent or a booking-app bot for a salon.

Acceptance test: five minutes with three accounts

Before you pay, run this test with a friend or your own spare accounts. Write down what you saw.

1. Comment the keyword on the right post. The DM should arrive within seconds, once, with your name and tone.
2. Comment it again. The flow should not send the opening message a second time, or should handle it politely.
3. Tap each button. Every path should end somewhere sensible, with a tag applied and a human notified.
4. Reply with something odd ("do you do weddings?"). A message should offer a human, not loop.
5. Type the stop word. The person should be removed from further automation.
6. Check the tags and the notification. The contact should carry the tags in the map, and you should have been alerted.
7. Check from a person who does not follow you. Message requests and follower status can change what happens.

If anything fails, it is the expert's to fix before payment; if the flow is not behaving after a week of real use, ManyChat not working: fixes for flows that don't fire is a good diagnostic list to hand them.

How the "viral post" problem tends to appear

A plausible failure, so you can plan for it. A signage company's reel gets ten times its normal reach. Hundreds of people comment QUOTE within a day. The flow does exactly what it was built to do, and the owner finds on Monday that the active contact count has leapt well past the plan's limit and that 300 half-finished conversations are waiting for a human. Meanwhile some of those people replied after the 24-hour window, where automations no longer deliver.

How to prepare, and what to ask the expert to build in: a cap or a waiting message ("we are getting a lot of enquiries, we will reply within three working days"), a way to filter the real leads from the idle commenters, and an agreed rule on who checks the plan's usage in the first 48 hours after a post takes off. None of this needs AI; it needs foresight in the first build.

When the expert owns the connection and you cannot edit a word

Another failure that surfaces only months later. A café owner pays a freelancer to build a flow, and it works. Then the menu changes and the owner cannot find who can edit the message. The Facebook Page it runs on is administered by the freelancer's personal profile, and the ManyChat workspace is on the freelancer's email. The freelancer has moved on and does not reply. The owner's choices are to leave a flow with the wrong prices live, or to rebuild from scratch and lose the tags.

It is avoidable in ten minutes at the start: before the first message is written, check that your own login is the owner of the Page and the workspace, and that the expert appears only as an added user. Repeat the check at handover, and again every few months, because people change roles and logins.

A first-month review, with sample numbers

Agree in advance what you will look at after thirty days, so the flow is judged on results and not on a feeling. Illustrative numbers for the signage company:

If replies are strong but few people give details, shorten the question. If comments are strong but replies are weak, the opening message is the problem. If quote requests are many but poor, tighten the first choice buttons. Each reading points to one small edit, which you can often make yourself after the handover.

When the second project should add AI

Once the keyword flow has run for a few weeks, you will have real questions from real people. That is the right moment to consider AI replies, which ManyChat includes from its Pro plan upwards. The method is simple: collect twenty actual questions, run them through the AI step in a test copy, and compare each answer against what you would say. Testing ManyChat's AI step on 20 real questions shows how to score it. The expert's role is to wire it and set boundaries; the content of the answers is yours.

A prompt for judging an expert's proposal

If a proposal is long or technical, an AI assistant can check it against this tutorial. Paste it with names removed:

I run a small business and may hire a ManyChat expert. Below is
their proposal. Check it against this list and answer "covered",
"vague" or "missing" with the sentence that proves it:
1. First project is one small keyword flow, not AI
2. Built in MY workspace, on accounts I own
3. Access to Meta accounts via partner access, not passwords
4. Testing with three accounts, including a non-follower
5. Handling of the 24-hour and 7-day messaging windows
6. A human handover and a stop word
7. Handover guide and recording
8. Aftercare period stated
Then list anything in the proposal that is not in my list and might
cost extra. Do not assume anything the proposal does not state.

[paste proposal]

An illustrative result: "5. vague: 'compliant with Meta rules' but no mention of the 24-hour window. 3. missing. Extra: 'monthly optimisation retainer'." That is three useful questions in thirty seconds. And if you would like to talk through whether your business should automate DMs at all, that is a normal topic for my AI implementation consultation.

The hiring checklist on one page

• I tried building a template flow myself, or I have a reason not to.
• The first project is one keyword flow with a human handover.
• The expert showed me a live flow I could test, and told me one thing that went wrong once.
• They explained the 24-hour and 7-day windows without being asked twice.
• Instagram, Page and ManyChat workspace are under my logins; access is partner-based.
• The scope lists design, build, connections, testing, tone, handover and aftercare.
• I know what stays with me: inbox checks, offers, tone, tags, weekly review, budget.
• I will run the seven-step acceptance test before paying.

Tick every box and you have hired well. Miss two or three, and you are buying a flow you cannot run.

Questions before you hire a ManyChat expert

Can I build my first ManyChat flow myself?

Often, yes. ManyChat's Free plan includes the automation builder with up to four live triggers and more than 60 ready-made templates for replying to comments, greeting new followers and sharing links in DMs. Hire help when you need several channels, a verified WhatsApp setup, CRM connections or AI replies.

Who should own the Instagram and Facebook accounts the flow runs on?

You should, always. Keep the Instagram professional account and the Facebook Page under your own business login, give the expert access through Meta's own sharing tools, and remove it when the job ends. Never hand over a personal password.

Will ManyChat message people whenever I want?

No. On Instagram and Messenger, Meta's rules give a 24-hour window after a person's last interaction, then a 7-day window in which you can send manual replies from the inbox but automations will not deliver. ManyChat blocks scheduled messages that fall outside the window.

Should the first project use ManyChat's AI?

Not first. Build and test the plain keyword flow, then add AI on a paid plan that includes it once you have real questions to test it against. A flow that works without AI is easier to debug and easier to hand over.

Further reads

• Manychat Pricing Tiers: What a Small Business Pays as Contacts Grow — Manychat prices rise with active contacts. Here is the cost at five contact volumes, where each tier breaks even, and how to avoid a surprise bill.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: Manychat pricing page (including its Hire an agency link), Manychat help (Understanding messaging windows), Meta Business Help (giving a partner access to business assets).