What changed for Instagram DM automation in October 2026?
Meta updated its Instagram messaging docs twice. On October 18, 2026 it explained how other apps take a conversation from Meta Business AI. On October 28, 2026 it added a handoff_reason field telling apps why Meta's Business Agent handed a chat over.
Meta Business AI on Instagram: the dates
Both changes appear in Meta's Instagram Messaging changelog, which we read on October 30, 2026. They matter to any business that runs ManyChat, GoHighLevel, n8n or another tool on Instagram and has also switched on Meta's own AI agent for the same account. If that is you, or you are about to, our Instagram DM automation service sets up both so they do not talk over each other.
| Changelog date | What Meta changed | Who it affects |
|---|---|---|
| October 28, 2026 | Webhook reference documents message.handoff_reason for Meta Business Agent handoffs | Apps that receive handoffs from Meta's agent |
| October 18, 2026 | Conversation Routing explains taking control of conversations owned by Meta Business AI | Any connected app that sends replies on the same account |
| September 28, 2026 | Docs state the standard window may extend up to 7 days for conversations started from Click-to-Direct ads | Ad-driven Instagram flows |
What is Meta Business AI on Instagram?
It is Meta's own AI agent that answers customers in a business's messages. Meta announced Business Agent on June 3, 2026, said it was extending it to Instagram, and said getting started is free, with paid subscription tiers to come.
Meta's newsroom post describes the agent as "AI that lets every business show up for every customer as if they had an infinite team behind them." It answers questions and lets the business decide when a team member steps in. Meta's developer docs call the same thing "Meta Business AI" in some places and "Meta Business Agent" in others.
The practical issue is that Instagram lets several apps connect to one account. When Meta's agent owns a conversation, your own automation tool is no longer the one allowed to reply.
Why would your ManyChat, GoHighLevel or n8n replies fail?
If Meta Business AI owns the conversation and the new setting is off, your app's normal replies fail with error code 100, subcode 2534037. Meta's docs say the "Take control of conversations with your Business AI" setting is off by default.
Who may reply when Meta Business AI owns a chat
The October 18, 2026 changelog entry and the Conversation Routing page set out the rules:
- A separate setting. "Take control of conversations with your Business AI" is independent of the older "Take control of conversations" setting, and is configured per connected app.
- Where it lives. Page Settings, Page Setup, Advanced Messaging, Connected apps, or Meta Business Suite, Settings, Conversation routing.
- When it is off. Untagged Send API requests fail with error code 100 and subcode 2534037. Your app still receives the person's messages on the standby channel.
- What Meta tells apps to do. "Wait for a
messaging_handoverswebhook event containingpass_thread_controlbefore responding."
For a business this shows up as a flow that looks fine in your tool's builder and silently stops sending on Instagram, while customers get answers from Meta's agent instead. Our guide to Instagram DM rules and restrictions covers the other common reasons messaging stops.
What does the new handoff_reason field tell your app?
When Meta's Business Agent hands a conversation over, the webhook can now include handoff_reason: purchase_intent, payment_received, human_requested or other. Apps can route on that value instead of parsing the localized text message Meta sends with the handoff.
| handoff_reason value | Example trigger in Meta's reference | What we would route it to |
|---|---|---|
purchase_intent | The person is ready to buy or asks to start checkout | Sales: booking link or a salesperson within minutes |
payment_received | The person completes a payment and the agent hands off | Fulfilment: confirmation, receipt, onboarding steps |
human_requested | The person asks for a person or customer support | A staff member, with an alert, inside the Human Agent window |
other | Missing information, unsupported request, another app taking over, a response failure, or unspecified | A general queue for review |
Three limits from Meta's webhook reference. The field is optional, and apps must keep handling notifications without it. Several conditions produce other, and the webhook does not say which one. A messages notification "does not itself transfer conversation ownership", so the routing rules above still apply.
What this means for your business
If you run your own Instagram automation, decide which system owns each conversation before switching on Meta's agent. Then turn on the right takeover setting for your tool, and route handoffs by reason so buyers reach a person fast.
| Symptom | Likely cause | Fix |
|---|---|---|
| Your tool's Instagram flows stopped sending after Meta's agent was switched on | Business AI owns the threads; the takeover setting for your app is off (error 100, subcode 2534037) | Pick one owner per entry point; if your app should answer, turn on "Take control of conversations with your Business AI" for that app |
| Two bots answer the same person | Your app replies to standby messages | Ignore standby messages; reply only after pass_thread_control |
| Handoff alerts go to the wrong team | Routing reads the localized handoff text | Route on handoff_reason, with a fallback when it is missing |
| Ad conversations close too early | Flow assumes 24 hours for every chat | For Click-to-Direct ad chats, allow for the window of up to 7 days Meta now documents |
Our view: Meta's agent is free to start on Instagram and fine for simple questions. Businesses whose leads must land in a CRM with tags, pipeline stages and bookings usually keep their own automation as the owner and use Meta's agent nowhere, or only on one entry point. If you use GoHighLevel, our GoHighLevel comment-to-DM guide shows the workflow side, and our AI chat agent service covers running your own AI on the same channel. In September we also covered Meta's Muse connector for HighLevel, another Meta AI product that touches the same accounts.
More questions about Meta Business AI and Instagram automation
Can Meta Business AI and ManyChat run on the same Instagram account?
Yes, both can be connected, but only one owns a conversation at a time. Meta's Conversation Routing docs say other apps receive messages on the standby channel while Meta Business AI owns a thread, and should reply only after a pass_thread_control event. Decide which tool answers which entry point, and set the takeover settings to match.
What does Instagram error code 100 subcode 2534037 mean?
Meta's docs say it is returned when your app sends an untagged message into a conversation owned by Meta Business AI while the "Take control of conversations with your Business AI" setting is off for your app. Either turn the setting on for that app or wait for Meta's agent to pass the conversation.
Is Meta Business Agent free on Instagram?
Meta's June 3, 2026 announcement says getting started on Instagram is free and that paid subscription tiers will come in the following months. It gave no prices. Check Meta Business Suite for the current terms before relying on it for customer conversations.
Do I need to change anything if I do not use Meta's AI agent?
No action is required. The October changes only matter when Meta Business AI owns conversations on your account. If nobody has switched it on, your existing ManyChat, GoHighLevel or n8n flows keep working as before. Check Meta Business Suite once so you know whether it is on.
Where does the September 28 seven-day window change fit in?
Meta's changelog for September 28, 2026 records that its messaging policy and Instagram Platform overview now state the window may extend up to 7 days for conversations that start from Click-to-Direct ads, counted from the person's first message after the click. Other entry points keep 24 hours.
Sources and further reading
- Meta: Instagram Messaging changelog (entries of September 28, October 18 and October 28, 2026)
- Meta: Conversation Routing for Instagram
- Meta: Instagram Messaging webhooks reference (handoff reasons)
- Meta Newsroom: Be There for Every Customer With Meta Business Agent (June 3, 2026)
- Meta: Instagram API with Instagram Login, Send Messages (windows)
