ManyChat or a Custom AI DM Worker for Instagram Replies

The short verdict

If most of your Instagram messages fall into three or four predictable requests, ManyChat is the lower-risk starting point. Its visual builder is designed for flows that a team can set up in a day and adjust later. If your customers ask open questions about sizes, delivery to a particular area, or which product fits a specific need, a keyword flow will keep sending them back to the menu. A custom AI DM worker can read a free-text question and answer only from the product and price list you approve. It can also hand the chat to a person when the question falls outside that list.

Neither option removes the need for a person. Someone has to own the approved answers, review the hand-off queue and decide what the bot may say about refunds, stock or pricing exceptions. Treat the choice as a question of where the answers come from, not of which tool is smarter.

Side-by-side comparison

Vendor prices and limits change often. The table below records what was published in 2026. Where a vendor does not show a figure, the table says so.

What Meta's rules mean for both options

Meta's developer documentation sets the messaging window at 24 hours for most interactions. A user's message opens the window, and each new message from them restarts the clock. After the window closes, a business can send only a message with an approved tag, and promotional content is not allowed under those tags. For Instagram, the window can run up to seven days after a Click-to-Direct ad, according to Meta's documentation as summarised by third-party guides in 2026.

The human agent tag is the route most teams ask about. Meta describes it as a tag for live human agents who reply within seven days. It is not meant for automated bot logic. A custom worker that tries to use it for follow-ups will be rejected by the platform and risks account restrictions. Keep the tag in your human inbox, not in the bot.

Serving your own Instagram account needs only standard access. A product that serves accounts owned by other people needs Meta's Advanced Access, which requires App Review and business verification. This matters if you build a worker for a group of businesses. It matters less for one company that runs its own account. ManyChat already holds that approval, so its users do not face the review step directly.

Meta also expects an automated chat to say it is automated, at least where local law requires it. An older commentary on Meta's guidance names California and Germany as examples. Write the greeting so that a customer knows early that a bot is replying.

Who each option suits

ManyChat suits a team that wants to start within a week, has a small set of repeat requests and has no developer on staff. It also suits a business that runs many comment-triggered campaigns, because the comment-to-DM flow is its core feature. Its weakness is breadth. Each new question needs a new branch, and the menu becomes long fast.

A custom AI DM worker suits a business with a stable product list, a steady flow of free-text questions and a person who can review the answer library every month. It also suits a company that wants its Instagram answers to match its order system, stock records or booking calendar. It is a poor fit if your products change weekly without anyone updating the approved list, because the worker will then answer from old information.

Some businesses should use neither. If you receive only a few messages a week, a shared inbox and a human reply will be cheaper and more accurate. Automation adds value when the volume and repetition justify the upkeep.

Total cost of ownership: what the sticker price leaves out

The monthly subscription is the visible cost. The larger costs for either option sit in setup time, upkeep and the cost of a mistake. Meta publishes no per-message price for the Instagram Messaging API, so the real costs are the build, the hosting, the review process if you need Advanced Access and the staff time to maintain answers.

• Setup: flow design and testing for ManyChat; app setup, webhook, answer library and testing for a custom worker.
• Maintenance: someone must update prices, stock notes and policies, and check the hand-off queue every week.
• Breakage: a Meta policy change, a permission change or a changed account type can stop replies. Both options are exposed to this.
• Overage: ManyChat's paid plans charge per extra active contact, reported in 2026 as $0.10 on Essential, $0.05 on Pro and $0.025 on Business. Viral campaigns raise this line quickly.
• Vendor lock-in: flows built in ManyChat do not move cleanly to another tool. A custom worker keeps your answer library in files you own.

A keyword menu rarely breaks in a way that customers notice quickly. A wrong answer from an AI worker can reach many people before anyone checks it. That is why the approved list and the hand-off rule carry most of the risk.

The custom-built option and when it wins

A custom worker wins when the questions are too varied for a menu, and when the answers must match your own records. The worker reads the incoming message, identifies the request and answers only from the approved list. If the question is outside that list, or the customer asks for a refund, a complaint or a legal position, the worker passes the chat to a person with a short summary.

It also has real limits. It cannot promise delivery dates it cannot see, and it cannot make pricing decisions that belong to a manager. It cannot open a chat after the 24-hour window closes, except through the approved routes. It will sometimes say something unhelpful, so someone must read a sample of conversations each week. Results depend on the quality of your product data and the volume of questions, which a free automation audit measures before any build begins.

Migration notes if you switch

Moving from a keyword flow to a custom worker is simpler than most owners expect, if you start with the questions. Export the keywords and the replies your flows use. Group them by the question they answer. Those groups become the first version of your approved answer library.

1. Record the top twenty questions your team answers by hand, and the answer each one gets.
2. Confirm which Instagram accounts the worker will serve, and whether Advanced Access is needed.
3. Run the worker alongside the flow for two weeks, with a person checking every reply.
4. Switch off the old comment triggers only after the new hand-off queue has been tested.
5. Keep the old flow exports so you can restore a known-good version if a reply goes wrong.

Do not delete ManyChat contact data until you have confirmed where it is stored and how you will retain it. If customers in the European Economic Area or the United Kingdom are among your contacts, the General Data Protection Regulation and the UK GDPR apply to that data. This explains the rule in general terms; it is not legal or tax advice for your case.