Facebook Messenger AI Agent Setup in 10 Steps

Quick answer: Publish a Facebook Page, connect it to a Meta app holding pages_messaging (or use a partner platform or Meta’s Business Agent), verify an HTTPS webhook and answer every message within 30 seconds. Your AI may reply freely for 24 hours after each customer message, or up to 7 days after a Click-to-Messenger ad; beyond that, only Meta’s named exceptions apply.

If you are asking “how do I set up a Facebook Messenger AI agent for my business”, the work splits into two halves. The first is plumbing: a Facebook Page, a Meta app or a partner that owns one, a set of Page permissions, a webhook and a Page access token. The second, which is where most projects stall, is Meta’s messaging policy. It says when your agent may speak, what it must tell people about being automated, how fast it must answer, and how a conversation moves from the AI to a person through Conversation Routing (Meta has retired the old Handover Protocol for Messenger). This guide covers both, in the order you hit them. Everything about Meta comes from Meta’s own developer documentation and newsroom, read on 14 October 2026; where the live developer site would not load from our side, we read a dated Internet Archive capture of the same page and say so in the source table at the end.

What you need before step one

The Messenger Platform is the API side of Messenger: Meta’s overview says it lets a business’ Facebook Page “respond to people who message them”, that “a person must initiate the conversation”, and that “the Messenger Platform is free to use”. Your AI agent never cold-messages anyone on Messenger. It answers people who wrote to your Page, clicked a Click-to-Messenger ad, used an m.me link, commented on a post, or opted in to a follow-up.

You need four things on day one: a published Facebook Page, a person with the right access to that Page, a Meta developer account (if you are building your own app), and an HTTPS server with a valid certificate that can receive webhooks. If you use a partner platform, the partner supplies the app and the server; you still supply the Page and the access.

The same Send API also serves Instagram professional accounts, but the Instagram setup differs and this page covers Messenger only.

The 10-step setup critical path, with the blocker at each step

Each step names the first action, the finish state and the thing that most often blocks it. Steps 1 to 6 get a working agent on your own Page; steps 7 to 10 keep it inside Meta’s rules.

Step	First action	Finished when	Common blocker
1. Page and access	Publish the Page; confirm you can perform the MESSAGING and MODERATE Page tasks	You can generate a Page access token	Unpublished Page (App Review requires a published one); a role without messaging access
2. Choose a route	Pick Meta Business Agent, a partner platform, or your own Meta app	You know who owns the app	Building an app when a partner or Meta’s own agent would do
3. Meta app and permissions	Create an app with the “Engage with customers on Messenger” use case	Required permissions added	Missing `business_management`, which `pages_messaging` depends on
4. Webhook	Deploy an HTTPS endpoint that echoes `hub.challenge`	Meta verifies it and events arrive	Self-signed certificate; slow 200 OK responses
5. Page token and subscription	Connect the Page in Messenger API Setup and subscribe to webhook fields	A test message reaches your server	A user-backed token that breaks when that person’s access changes
6. First reply	Message your own Page, then answer with `messaging_type` RESPONSE	The reply lands inside 24 hours	Using a Facebook Login user ID instead of the Page-scoped ID
7. Responsiveness	Declare the bot type and measure response time	Every input answered within 30 seconds	LLM latency plus tool calls exceeding 30 seconds
8. AI disclosure	Write the opening line that says it is automated	Disclosure at the three moments Meta lists, wherever the law requires it	Serving California or German users without it
9. Hand-off to a person	Set the default app and the Page Inbox in Conversation Routing	A pass to the inbox works end to end	Two apps answering the same message
10. Outside-window messages and review	Map every message you plan to send to the send-permission table below	Each message has a legal route; App Review passed if you need it	Retired message tags returning error 100

Step 1: Get the Facebook Page and admin access right

Meta’s overview says the person requesting the Page access token “must be able to perform the MESSAGING and MODERATE Page tasks”. Its Conversation Routing guide sets a higher bar for routing work: Admin access or the MANAGE task on a classic Page, Facebook access on the New Pages Experience, or Full control in Business Settings. Meta’s App Review page lists “Publish the Facebook Page associated with your app” as a requirement before submission. Do this first, because every later step needs a Page token issued by someone with these rights.

Step 2: Decide who owns the app

There are three routes. You can switch on Meta Business Agent, Meta’s own AI agent (covered in its own section below). You can use a third-party platform that already holds a reviewed Meta app; Meta’s create-an-app guide says an app that accesses “business data owned by other business portfolios” must become a Tech Provider, with extra questions and App Review. Or you can build your own Meta app for your own Page. The last route is lighter than it sounds: Meta’s overview says App Review is “not required if you only send and receive messages for your own Facebook Page.”

Step 3: Create the Meta app and add the Messenger permissions

Create an app in the Meta App Dashboard and add the “Engage with customers on Messenger” use case. Meta’s use-case table marks five permissions as required and impossible to remove: business_management, pages_manage_metadata, pages_messaging, pages_show_list and public_profile. (That table prints the second one as “page_manage_metadata”; Meta’s overview spells it pages_manage_metadata.) Optional additions include pages_read_engagement, pages_utility_messaging for utility templates, paid_marketing_messages, and the three pages_user_* profile permissions. The overview adds that business_management “is a dependency for pages_messaging, pages_show_list, and instagram_manage_messages”.

Step 4: Stand up the webhook

Meta’s webhooks guide says your server must handle verification requests and event notifications over HTTPS with “a valid TLS or SSL certificate”, and “self-signed certificates are not supported”. On verification, check that hub.verify_token matches the string you set in the App Dashboard and return hub.challenge. For events, return 200 OK. Meta’s App Review checklist asks that the webhook return “a 200 OK response to webhook events within 20 seconds”, so acknowledge first and let the model think afterwards.

Step 5: Connect the Page and choose a token that will not break

In Messenger API Setup, click Connect, pick the Page, then Add Subscriptions for the webhook fields you need (messages and messaging_postbacks at minimum, plus the routing fields in step 9). Meta’s best-practice page warns that a Page access token “backed by an user” can be invalidated by that person’s actions and recommends “a stable access token backed by a system user”. It also tells you to handle error 190, which means the token is no longer valid, by alerting a Page or app admin.

Step 6: Send the first reply (your day-one test)

Meta’s get-started guide is the right first action. From a personal Facebook account, send your Page a message. That creates a Page-scoped ID (PSID) for you. Fetch it from /<PAGE_ID>/conversations, then POST to /<PAGE_ID>/messages with messaging_type RESPONSE. Meta notes that this “must be sent within 24 hours of your Page receiving the customer’s message”. If it fails, Meta’s send guide lists the common codes: 10 (permissions, check pages_messaging), 100 (invalid parameter), 190 (expired token), 551 (person unavailable) and 613 (rate limit). One trap is in the same guide: user IDs from Facebook Login integrations “are app-scoped and will not work with the Messenger platform”.

Step 7: Meet the 30-second responsiveness rule

This is the step AI projects underestimate. Meta’s policy says automated bots “must respond to any and all input from the user”: free text, quick replies, CTA buttons and persistent-menu clicks, with only the Get Started button excluded. They must answer “within 30 seconds”. The rule applies to bots identified as “automated” (not “hybrid” or “human”) that are submitted for approval via the App Dashboard; treat 30 seconds as your target even if you never submit, because Meta’s App Review page separately asks for an average response time under one minute. If people as well as the AI answer on your Page, Meta tells you to update the response setting in Page Settings > Advanced Messaging. If Meta flags a violation, you have 7 days to fix it before your bot’s ability to send “may be limited”.

The practical fix is to send something fast. Meta’s Sender Actions show a typing indicator, and a short “checking that for you” reply covers a slow lookup. For a fuller treatment of why the first reply’s speed matters commercially, see our guide to speed to lead with AI agents.

Step 8: Tell people they are talking to an AI

Meta’s policy is conditional, and the condition matters. “When required by applicable law, automated chat experiences must disclose that a person is interacting with an automated service” at three moments: “at the beginning of any conversation or message thread”, “after a significant lapse of time”, or “when a chat moves from human interaction to automated experience.” It singles out California and German users. Its examples include “You are talking to a bot” and “I’m the [Page Name] bot”. Even where the law does not require it, Meta recommends disclosure as best practice. Its design guide goes further: “do not disguise an automated interaction as a real person.” In practice, put the disclosure in your agent’s first message and again whenever a person hands the thread back to it.

Step 9: Wire the hand-off to a person with Conversation Routing

Meta’s Conversation Routing guide opens with a warning: “Meta no longer supports Handover Protocol for Messenger and all the businesses are migrated to Conversation Routing,” which it says is backwards compatible with most Handover Protocol calls. If your AI agent is the only app on the Page, Meta’s default behaviour needs no routing setup. You still have to stop the AI and your staff in the Page inbox answering the same message twice.

If more than one responder is involved, set a default app in the Page’s settings. Meta’s prerequisites for passing conversations between apps also list a Meta Ad Account and connecting every app to the Page. Subscribe each app to messages, messaging_referral, messaging_handover, messaging_postbacks and standby, and use the four control flows: pass, release, take and extend. To hand a thread to people working in Meta Business Suite, pass control to the Page Inbox, which Meta identifies as target_app_id 263902037430900. Thread control “will expire after 24 hours of inactivity” unless the owning app extends it. Include the conversation summary in the metadata field when you pass, so the person picking it up does not ask the customer to repeat themselves; we cover what to put in that summary in AI-to-human handoff and context transfer.

Step 10: Map every outbound message, then pass App Review if you need it

Before launch, list every message your agent will send that is not a direct reply, such as reminders, follow-ups, surveys and re-engagement. Then find each one’s row in the send-permission table below. If you serve other businesses’ Pages, or anyone without a role on your app, you need Advanced Access. Meta’s overview says that requires App Review, and Business Verification if the app is used by people without a role on it. Meta’s publishing checklist asks for an app icon, a privacy policy URL, a data deletion URL, and a Data Protection Officer contact if you do business in the European Union.

The Messenger send-permission table: when can my AI agent message someone?

This is the Messenger send-permission table: find how long it has been since the person last messaged your Page, then why you are messaging them, and read off whether Meta allows it and through what. One rule decides every row: a reply is free inside the window. Anything after it needs a named exception, and only sponsored messages, marketing messages and one-time notifications may carry promotional content.

Time since the person’s last message or action	Purpose	Allowed?	Via what (Meta’s mechanism)
0 to 24 hours	Any reply or proactive update, including promotional content	Yes	Standard messaging; `messaging_type` RESPONSE or Meta’s “Updates” type
Up to 7 days after their first message from a Click-to-Messenger ad	Any, including promotional content	Yes	Standard messaging window, which Meta says “may last up to 7 days” for this entry point
24 hours to 7 days	A person on your team answering the customer’s own inquiry	Yes, after approval	Human Agent message tag (`HUMAN_AGENT`); the Human Agent permission needs App Review
24 hours to 7 days	Your AI agent continuing the conversation automatically	No tag covers it	Meta’s tag table lists “Automated messages” as disallowed under Human Agent; use one of the routes below or wait for the person to write again
Up to 7 days	A satisfaction or feedback survey	Yes, template only	`CUSTOMER_FEEDBACK` tag with the Customer Feedback Template, which Meta marks “in development”
Outside the window	Appointment reminder, order or account update	Not by tag since 27 April 2026	Utility message templates (`pages_utility_messaging`); the retired tags CONFIRMED_EVENT_UPDATE, ACCOUNT_UPDATE and POST_PURCHASE_UPDATE return error 100
Outside the window	One follow-up the person explicitly asked for (such as a back-in-stock alert or appointment reminder)	Yes, once	One-time Notification: a single-use token that expires within 1 year; Page-level permission
Outside the window	Promotions to people with an open conversation	Yes, as an ad	Sponsored Messages, labelled “Sponsored” and bound by advertising policies
Outside the window	Recurring promotions the person subscribed to	Yes, via a Tech Provider	Marketing Message API: Tech Providers only, businesses in 20 listed regions (Australia included), but not sent to users in the EU, Japan, South Korea, Australia or the United Kingdom, so an Australian business cannot use it to reach customers in Australia
Within 7 days of a comment or visitor post	A private reply to that comment	Yes, one message	Private Replies
Any time (registered news Pages only)	Non-promotional news	Yes	`NON_PROMOTIONAL_SUBSCRIPTION` tag, News Page Index Pages only
More than 24 hours, none of the above	Anything	No	Meta’s FAQ: “The message will fail to be sent.”

Two rows change how an AI agent should be designed. First, the 24-hour reply window is the AI’s working space. Once it closes, your agent cannot carry on the chat by itself, and the Human Agent tag is reserved for people. Second, the retirement of three tags on 27 April 2026 moved tagged appointment reminders onto utility templates (a one-time notification still covers a single reminder the person asked for). Meta’s changelog told senders to “migrate to Utility Templates or Marketing Messages API”. Meta’s utility guide says a Page-owned template is approved “within seconds of creation”. The utility guide we read does not itself state a time limit for sends, so confirm that before you rely on it for a reminder sequence.

One honest caveat about the tag rows: the HUMAN_AGENT string and its “Automated messages” exclusion come from Meta’s 2022 message-tag table. Meta’s current pages (September 2026) confirm the Human Agent tag and its 7-day period, but every 2026 copy of the full tag reference we tried was a JavaScript shell we could not read. Check the current Send API reference before you build on the exclusion.

What is Meta Business Agent, and should I use it instead?

Meta now has its own AI agent for business messaging, and a fair setup guide has to treat it as a real option. In its 3 June 2026 announcement, Meta said Business Agent can “answer questions specific to your business”, “make product recommendations from a business catalog”, “book appointments and qualify incoming leads”, “let you decide when a team member steps in to provide support” and “close sales”. Meta said more than one million businesses were already using a Business Agent on WhatsApp and Messenger, that it “can be set up in minutes”, and that “getting started is free”, with paid subscriptions to follow “in the coming months”. It also announced a Meta Business Agent Platform with connections to systems such as Shopify, Zendesk and Shopee. On 28 September 2026 Meta listed Business Agent as part of its new Meta Enterprise Platform. Those paid plans have since arrived. Meta’s 15 September 2026 Meta One announcement lists business bundles starting at $14.99 a month (Essential, with “more access to Meta Business Agent on WhatsApp”), $49.99 a month (Advanced, with “even more Meta Business Agent responses”), and $149 and $499 a month (Expert and Max, with Meta’s “highest levels of feature access and Meta Business Agent capacity”). Meta adds that “plans, benefits, pricing, and availability may vary by region, by app, and by account.”

The trade-off is ownership. A Meta-run agent lives inside Meta’s apps. An agent you run, or a platform runs for you, can work the same lead across channels Meta does not own, such as phone calls, SMS and email. (Meta’s Business Agent Platform does connect to business systems such as Shopify and Zendesk.) If you are making the same call for WhatsApp, our comparison of the best WhatsApp AI agents for sales teams covers that channel.

Which tool should run my Messenger AI agent?

Method: we list the routes a business can actually take to put an AI agent on Messenger. We describe Meta’s routes from Meta’s own published pages, read on 14 October 2026, and Zian and LeadsNow.ai from our own product information, and rank by fit for businesses that want Messenger to be one channel in a sales and reception operation. Disclosure: zian.ai publishes this table, and Zian appears in it.

Rank	Option	Best for	What it covers	Published price
1	Zian AI (platform)	Teams that want one AI agent across Messenger and every other channel	AI sales and reception agents for inbound and outbound conversations across voice calls, SMS, email, WhatsApp, Instagram DMs and Facebook Messenger; appointment booking; 30+ languages; HubSpot, Salesforce, HighLevel and Zapier integrations; human-in-the-loop approvals	None public; partnership-application beta
2	LeadsNow.ai (done for you)	Businesses that want the agent run for them	Managed AI appointment setting and lead generation that runs on Zian; pay-per-result	Pay-per-result; no figure published here
3	Meta Business Agent	Businesses that live inside Meta’s apps	Answers questions, recommends catalogue products, books appointments, qualifies leads, hands off to a team member; WhatsApp, Messenger, Instagram	Free to start; Meta One business plans with more Business Agent access from $14.99 a month (Meta, 15 Sep 2026; may vary by region)
4	Your own Meta app	Developers with one Page and an in-house model	Everything in the 10 steps above; no App Review for your own Page	Messenger Platform free; you pay for hosting and the model

Zian’s honest gap is that it is in partnership-application beta, with no public price. The DIY route costs more than it looks. Someone has to keep a webhook answering within 20 seconds and a bot answering within 30, rotate tokens, keep the disclosure and routing rules current, and rebuild reminder flows whenever Meta retires a mechanism, as it did on 27 April 2026. Where people review AI drafts before they send, our guide to human-in-the-loop controls for AI sales agents sets out the approval patterns.

Run Messenger as one channel, not a separate project. Zian’s AI agents run Facebook Messenger conversations alongside voice calls, SMS, email, WhatsApp and Instagram DMs, and book the appointment at the end.

Apply For Partnership

How long does a Facebook Messenger AI agent take to set up?

On your own Page, the critical path has no Meta waiting step. App Review is not required, and Meta says utility templates are approved within seconds. The time goes into your own build: the webhook, the 30-second response budget, the disclosure copy and the routing tests. The waiting steps appear when you need Advanced Access (App Review, and Business Verification when people without a role use the app) or the Human Agent permission. Meta’s 2022 tag page says that permission “is not available in standard access/dev mode”, and Meta publishes no review time on the pages we read. Meta Business Agent is the fastest route on paper, since Meta says it “can be set up in minutes”.

Frequently asked questions

Can an AI agent reply on Facebook Messenger after 24 hours?

Not by itself in an ordinary conversation. Outside the 24-hour window (up to 7 days after a Click-to-Messenger ad), Meta allows only named exceptions: message tags, utility templates, one-time notifications, sponsored or marketing messages, and a private reply to a comment. The Human Agent tag covers replies for 7 days but is meant for people, and Meta’s tag table lists “Automated messages” as disallowed.

Which permissions does a Messenger bot need?

Meta’s Messenger use case requires business_management, pages_manage_metadata, pages_messaging, pages_show_list and public_profile. The person issuing the Page token must be able to perform the MESSAGING and MODERATE Page tasks.

Do I need Meta App Review for a Messenger AI agent?

Not if the app only sends and receives messages for your own Facebook Page. You need App Review for Advanced Access, for example when serving other businesses’ Pages, and for the Human Agent permission.

Does Meta require my Messenger bot to say it’s an AI?

Where applicable law requires it, yes: at the start of a conversation, after a significant lapse of time, and when a chat moves from a person back to automation. Meta’s Messenger Platform policy names California and German users and recommends disclosure everywhere as best practice.

What replaced the Handover Protocol on Messenger?

Conversation Routing. Meta says it no longer supports the Handover Protocol for Messenger and has migrated all businesses. Conversation Routing keeps pass, take and release thread control, and uses a default app and entry-point routing to decide which app answers.

Is Meta Business Agent free?

Getting started is free, according to Meta’s 3 June 2026 announcement, which also said paid subscription offerings would follow “in the coming months”. On 15 September 2026 Meta launched Meta One, whose business plans start at $14.99 a month and include more access to Meta Business Agent; Meta says pricing may vary by region, by app and by account.

Want Messenger, WhatsApp, Instagram, SMS and calls answered by one AI agent that books the meeting? Zian is in partnership-application beta.