Almost every guide to building a Messenger chatbot lists four message tags you can use to reach someone after the conversation window closes. Three of them now return an error.
Since 27 April 2026, API requests carrying CONFIRMED_EVENT_UPDATE, ACCOUNT_UPDATE or POST_PURCHASE_UPDATE get error code 100. One tag survives – and Meta describes it as a way for a business representative to manually respond, which is to say it is not for bots.
That single change reshapes what a Messenger chatbot can be. Everything below was read on Meta’s own documentation while writing this – the send reference and the platform overview, both updated in September 2026.
Key Takeaways
What Changed in April 2026
The fact the rest of this article hangs on, stated once and clearly.
Three Tags Now Return an Error
Meta’s send documentation carries a dated notice: effective 27 April 2026, all API requests containing the message tags CONFIRMED_EVENT_UPDATE, ACCOUNT_UPDATE and POST_PURCHASE_UPDATE receive error code 100.
Those three covered reservation reminders, account alerts and post-purchase updates – which is to say most of what people built outside-the-window flows for. If you are following a tutorial that lists them, that tutorial predates this.
What Message Tags Were For
Tags let a business send a message outside the standard messaging window, for personally relevant updates: shipping and delivery, an upcoming reservation or flight, an alert about someone’s account. They were never for promotion – Meta is explicit that tags may not carry deals, offers, coupons or discounts.
Misusing them is not a quiet failure either. The documentation warns it may result in restrictions on the Page or Instagram account’s ability to send messages at all.
What Is Left
One tag: HUMAN_AGENT. It allows a business representative to respond manually within seven days of the person’s message, for issues that cannot be resolved inside the standard window. It needs the Human Agent permission, requested and approved through the App dashboard.
Read the wording again: manually, a representative. Automated messages are outside its approved use. The one remaining way to reply late is the one your bot may not take.
The Windows a Bot Lives In
Two numbers, and the second one surprises people.
Twenty-Four Hours, Normally
The person must start the conversation – there is no cold outreach on this platform, by design. Their message opens a standard messaging window, and for most user actions it runs 24 hours. Inside it you can send freely: text, images, GIFs, audio, video, files, stickers, buttons, menus and templates.
Up to Seven Days, After an Ad
Here is the part worth building around. When the action that opens the window is a person sending their first message after clicking a Click-to-Messenger or Click-to-Direct ad, the window may last up to seven days from that message.
That is a seven-fold difference in how long you have to convert, decided by where the conversation came from. If you run click-to-message ads, the follow-up sequence they justify is nothing like the one an organic DM justifies. The equivalent on the Instagram side is covered in our guide to click-to-Direct ads.
And If You Miss It
Then you are looking at Sponsored Messages or One-Time Notifications, which is where Meta’s own documentation directs businesses who want to send promotional content outside the window. Both are paid placements rather than API calls – a different budget line and a different approval path.
What Reaches Someone, and When
Four situations, four different answers.
| Situation | Can you send? | How |
|---|---|---|
| Inside 24 hours of their message | Yes, freely | Standard messaging |
| Within 7 days of a click-to-ad arrival | Yes, freely | Extended standard window |
| After the window, a service issue | A human can, for 7 days | HUMAN_AGENT tag, approved permission |
| After the window, anything promotional | Not by API | Sponsored Messages or One-Time Notifications |
Compare that with the other channels and the shape of each becomes clearer: WhatsApp has approved templates that reach anyone who opted in, which is a far wider door – set out in our guide to the WhatsApp Business API – while Instagram runs on its own set of limits, covered in Instagram DM limits.
What a Messenger Chatbot Can Actually Send
Richer than most people use, inside that window.
The Content Types
Text, images, GIFs, audio, video, files, stickers, buttons, menus and templates. The send itself is a POST to the Page’s messages endpoint with the person’s page-scoped ID and a messaging type of RESPONSE – which is the whole API surface most bots ever touch.
Buttons and Carousels Do the Heavy Lifting
The generic template carousel – a row of cards with images, titles and buttons – is the single most useful structure on this channel, because it turns an open question into a tap. A bot that asks people to type is a bot that gets typos; a bot that offers three buttons gets three clean answers.
Products, If You Have a Catalog
A Page connected to a Meta Commerce catalog can send products into the conversation. That is the same catalog that serves Instagram and WhatsApp, and its behaviour is worth knowing before you rely on it – we wrote it up in our guide to the WhatsApp Business catalog, and the rules are the catalog’s rather than the channel’s.
The Access Review Nobody Warns You About
Where a working prototype stops being a working product.
Standard Access Is a Sandbox
By default your app has Standard Access, which limits data to people who have a role on your app or on your Page. Your bot works beautifully for you and your colleague and for nobody else.
Advanced Access – the one that reaches actual customers – requires App Review. That is a submission, a demonstration and a wait, and it is the step that turns a two-day build into a two-week one.
Permissions Are Per Capability
The Human Agent tag needs its own permission, applied for separately in the App dashboard and approved before use. Plan for the review you need rather than discovering it when a send fails.
Volume Has Consequences
Meta’s overview notes plainly that high-volume messaging can temporarily disable inbox functionality. Rate limits here are not only about API calls; they are about whether your Page’s inbox keeps working.
If a flow suddenly stops delivering, the pattern is the same as every other channel – find the layer first, as in our guide to automations that stop working.
Chatbot or Auto Reply? They Are Not the Same
The distinction that decides whether you need any of the above.
The Free Layer
Meta Business Suite gives every Page instant replies, away messages, keyword automations and comment-to-message rules, with no developer and no review. For a business answering the same six questions, that is the entire job.
The setup, including the keyword rules and their quirks, is in our Facebook Messenger auto reply guide.
The Platform Layer
A chatbot in the API sense branches on what people say, calls your systems mid-conversation, routes to a human and carries state across a thread. You want it when a reply needs data the Page does not have – an order status, a booking slot, a stock level.
That is a webhook problem rather than a text problem, and it is the real line between the two layers.
Routing Between Bot and Human
When a bot and a human inbox share one conversation, something has to decide who owns it. Messenger fires a handover webhook event for exactly that, and Instagram has been migrated off the old Handover Protocol onto Conversation Routing, which is backwards compatible with most of it.
Whatever you build, make the handoff explicit. The worst Messenger experience is the one where a person has replied and the bot keeps talking.
Messenger Against the Other Channels
Same builder, genuinely different rules.
| Messenger | |||
|---|---|---|---|
| Platform cost | Free | Per delivered message | Free |
| Standard window | 24h, or 7 days after an ad | 24h | 24h |
| Reaching someone after it | One human-only tag | Approved templates | Limited |
| Comment triggers | Yes | No public comments | Yes |
| Product cards | Yes | Yes | Yes |
| AI response in DMpro | No | No | Yes |
The last row is ours rather than Meta’s, and it is stated here for the same reason it appears on the WhatsApp chatbot page: the AI block exists in the builder but the runtime is not wired for either Meta channel.
Building One That Survives Contact With Customers
In order, and the first two steps are where projects actually die.
Decide whether you need the platform at all
If every answer is a fixed answer, Business Suite automations do it free, today, with no review. Only go further when a reply needs outside data.
Apply for the access you need before you build
Advanced Access via App Review, plus the Human Agent permission if an escalation path matters. Both are waits, and both are better started early.
Design inside the 24-hour window
A flow that assumes you can follow up on day three is a flow built on the tags that stopped working in April 2026.
Treat click-to-ad arrivals as their own segment
They carry up to seven days instead of 24 hours. Give them a longer sequence; it is the one place Messenger is generous.
Use buttons instead of asking people to type
Generic template carousels and quick buttons turn free text into clean, parseable answers and cut your failure cases dramatically.
Make the handoff to a human explicit
Routing exists for this. The bot should stop talking the moment a person takes the conversation.
Never put an offer behind a tag
Tags are for personally relevant updates. Promotion outside the window is Sponsored Messages, and the penalty for confusing the two lands on the Page.
What DMpro Does on Messenger
Including the gap, which is a real one.
Five Ways In
DMpro connects a Facebook Page and receives Messenger and Page comment events by webhook. Five things can start a flow: a comment on a post, an inbound message, a postback when somebody taps a button, a Messenger referral from an m.me link or a click-to-Messenger ad, and a Lead Ad form submission.
That last pair is the useful one. An ad click and a form submit both arrive as triggers, so the follow-up happens in seconds rather than whenever someone exports a CSV.
What It Sends
A DM with text or attachments, a generic template carousel of cards, a public reply on the comment, a private reply to a commenter, products from the connected Meta Commerce catalog, and Messenger templates. It can call a webhook mid-flow, branch on the answer and wait for a reply.
The public-reply-plus-private-reply pair is the pattern that works best here, the same way it does on Instagram comment auto reply.
And No AI Response Here
The AI response block runs on Instagram, TikTok, Telegram and Discord. On Facebook and Messenger it is not wired at runtime – the block may appear in the builder, but it does not run on this channel.
So a Messenger flow here is keywords, buttons, branches and webhooks. That covers more than people expect, and when the question is genuinely open-ended the honest answer is a person – which, given that the one remaining message tag is reserved for humans anyway, is where this channel points you regardless.
The Short Route on This Channel
Messenger is the cheapest channel Meta runs – the platform costs nothing – and the most fiddly to build on, between App Review, scoped IDs and a tag list that shrank this year.
DMpro connects your Page and gives you the five triggers without any of that: a comment, a message, a button tap, an ad click, a Lead Ad submission. Public reply and private reply from one automation, cards and catalog products in the thread, webhooks when the answer lives elsewhere.
- Five Messenger triggers, including ad referrals and Lead Ad forms
- Public comment reply plus a private DM from one flow
- Generic template carousels and Messenger templates
- Meta Commerce catalog products in the conversation
- Webhooks mid-flow for order and booking lookups
- The same builder for Instagram, WhatsApp, TikTok, Telegram and Discord
- No App Review, no scoped-ID plumbing, no permission applications
- Lead Ad submissions answered in seconds rather than after an export
- Official Meta connection through the Page, not a password
- No AI response on Facebook or Messenger – the runtime is not wired for it
- No follow gate, and no cold outreach: the person messages first
- Reaching someone after the window is a human job, not an automated one
Conclusion
The honest summary of Messenger in 2026 is that it got narrower and stayed free. Three of the four ways to reach someone after the window closed in April, the survivor is reserved for a human typing, and the platform itself still costs nothing to run.
That combination argues for a particular kind of bot: one that does its work inside the conversation, quickly, with buttons rather than guesses – and that hands over cleanly when it is out of its depth, because the follow-up tomorrow is no longer an option it has.
The one real generosity is the ad window. A person who arrives from a click-to-Messenger ad gives you up to seven days instead of 24 hours. If you are spending on those ads and treating the conversation like any other, that is the cheapest improvement available on this channel.
Comments, DMs, ad clicks and Lead Ad forms, all triggering the same flows.
Start free