setscale

Facebook Messenger chatbot rules in 2026 for booking calls

October 4, 2026·16 min read
Woman around thirty with short natural black curls, wearing a sage green knit sweater, sitting at a long walnut table in a bright bookshop cafe with wooden shelves, laptop open and a coffee cup beside her, soft warm light from the side, a small team blurred in the background

A Facebook Messenger chatbot can answer your leads, qualify them and book a call, and Meta's platform costs nothing to use for that. What limits it in 2026 is a short set of rules: a person has to start the conversation, your bot writes freely only inside a messaging window, a bot declared as automated must answer every input within 30 seconds, and in some markets it has to say it is a bot.

Several of the rules around it changed in 2026. Meta's Messenger policy page, last updated on 28 September 2026, says the window may last up to 7 days after a click to Messenger ad, while another Meta guide still says 24 hours. Three message tags stopped working on 27 April 2026, which changes how a booked call gets its reminder. And since 3 March 2026, bookings made inside Messenger reach third party tools. This guide reads each rule in Meta's own documentation, as it stands on 4 October 2026, and turns it into a setup for a bot that books calls. It is not legal advice.

TL;DR

  • A person must start the conversation. For most actions your bot then has 24 hours to write freely, promotional content included. After a first message sent from a Click-to-Messenger or Click-to-Direct ad, Meta's policy says the window may last up to 7 days.
  • A bot declared as "automated" must respond to any input within 30 seconds. A bot that hands leads to a human closer matches the type Meta calls "hybrid".
  • Where the law requires it, the bot must disclose that it is automated: at the start, after a long pause, and when a human hands the chat back to it. Meta names California and Germany.
  • Since 27 April 2026, the CONFIRMED_EVENT_UPDATE, ACCOUNT_UPDATE and POST_PURCHASE_UPDATE tags return error code 100. A reminder for a call booked outside the window now goes through a utility template.
  • Meta launched its own Business Agent on 3 June 2026, free to start. Whether a third party setter is worth it depends on how many channels your leads use and how many people take the calls.

Table of contents

The Facebook Messenger chatbot rules at a glance

Every rule below comes from a Meta page opened on 4 October 2026. The main one is the Messenger Platform and IG Messaging API policy, stamped "Updated: Sep 28, 2026". The others are linked in each section.

Rule What Meta's documentation says What it means for a bot that books calls
Who starts "A person must initiate the conversation." No cold outreach from a Page: your entry points are ads, links, buttons and comments
Standard window 24 hours for most user actions, up to 7 days after a first message sent from a Click-to-Messenger or Click-to-Direct ad Qualify and book inside it; promotional content is allowed there
Human Agent tag Manual replies within a separate 7-day period A late answer is typed by a person, not generated by the bot
Responsiveness Automated bots respond to any input within 30 seconds No dead end menus, no silent fallback
Disclosure Required "when required by applicable law", with California and Germany named Put a bot line in the first message for those audiences
Reminders outside the window Three event and account tags return error code 100 since 27 April 2026; utility templates cover appointment reminders Rebuild reminder flows on templates
Cost "The Messenger Platform is free to use." Marketing messages are charged per message Replies cost nothing; paid re-engagement is a separate product

When your Messenger bot is allowed to write

Meta calls it the standard messaging window. In the policy's words, "for most user actions, it lasts 24 hours. When the user action is a person sending their first message after clicking a Click-to-Messenger or Click-to-Direct ad, the window may last up to 7 days from that message." Messages sent inside it may contain promotional content.

The actions that open the window, as the policy lists them:

  • the person sends a message to your Page;
  • the person clicks a call to action button such as Get Started;
  • the person clicks a Click-to-Messenger or Click-to-Direct ad, then sends a first message;
  • the person starts a conversation through a plugin, such as Send to Messenger or the Checkbox plugin;
  • the person clicks an m.me or ig.me link with a ref parameter on an existing thread;
  • the person reacts to a message.

The ad extension is the line to put in your booking maths. A lead who clicks your ad on Friday night and sends one message can still be inside the window on Monday morning. One caution: on 4 October 2026, Meta's send messages guide still lists the ad click among the actions that open a 24 hour window. Until the two pages agree, design your flow for 24 hours and treat the extra days as margin, not as a plan.

Once the window closes, your options narrow:

  • Message tags, for personally relevant updates. They "may not be used to send promotional content, including but not limited to: deals, offers, coupons, and discounts."
  • The Human Agent tag, which lets a business representative reply manually within a separate 7-day period. Manually is the word that matters: it covers your closer, not your bot.
  • A one-time notification, when the person explicitly asked to be told about something. The token works once and expires within 1 year.
  • Sponsored messages, labelled "Sponsored", which may carry promotional content outside the window.
  • The Marketing Message API, for subscribers who opted in. Meta "charges the sending business directly for each marketing message". It is open only to tech providers, for businesses in a listed set of regions that includes the United States, and messages cannot be sent to people in the European Union, Japan, South Korea, Australia or the United Kingdom, according to the Marketing Message API page.

How to sequence follow ups across those windows is covered in our sales follow up process for setter teams.

Automated, hybrid or manual: the bot type you declare

The policy sorts bots into three types, chosen by a Page admin when the bot launches:

Type Meta's definition Typical case
Automated "All responses from the bot are programmed ahead of time" and need no manual intervention A news or weather bot
Manual Reply All responses come from live representatives A team answering through a CRM
Hybrid Automated and human interactions combined Meta's example: an airline bot that gives flight status instantly and connects you to an agent for changes

The 30 second rule applies to bots identified as automated. They "must respond to any and all input from the user", which Meta defines as freeform text, quick replies, call to action buttons and persistent menu clicks. The Get Started button is the only exception, and a bot that disables the composer must still answer every other input.

A setter that qualifies a lead, books the call and lets a closer take over the conversation is hybrid by Meta's own example. If that is your setup, the policy points to the bot's response setting, in Page Settings under Advanced Messaging.

Enforcement runs through the Page Support Inbox. Page admins receive the notice there, and the policy adds: "If you don't respond or make the appropriate changes within 7 days, your bot's ability to send messages may be limited." Meta says to expect a reply within 3 business days if you write back.

Whatever type you declare, the useful design rule is the same: every typed sentence gets an answer, not just every button. The human side of that clock is in our lead response time SLA.

Telling people they are talking to a bot

The policy sets the rule in one sentence: "When required by applicable law, automated chat experiences must disclose that a person is interacting with an automated service". It then names three moments:

  1. at the beginning of any conversation or message thread;
  2. after a significant lapse of time;
  3. when a chat moves from human interaction to automated experience.

Meta asks experiences serving the California market or California users, and the German market or German users, to pay special attention. Its sample wording includes "I'm the [Page Name] bot" and "You are talking to a bot". It also recommends disclosure where the law does not require it, "as this helps manage user expectations".

The third moment is the one teams forget. A closer takes the call, hands the thread back, and the bot resumes with a reminder: in the markets where disclosure is required, that hand back is a new point where it applies. Meta does not quote the laws themselves, so check the ones that apply to your audience.

Reminders for a booked call since the tag change

A booking flow usually sends three messages: a confirmation right after booking, a reminder the day before and one shortly before the call. The confirmation sits inside the window. The reminders often do not, as soon as the call is booked more than a day out.

Message tags were one route for that: Meta's send messages guide describes them as personally relevant updates, for example about "an upcoming reservation or flight". Three of them are now retired. Meta's Messenger changelog announced on 27 March 2026 that from 27 April 2026, "all API requests containing the deprecated Message Tags CONFIRMED_EVENT_UPDATE, ACCOUNT_UPDATE, and POST_PURCHASE_UPDATE will receive error code 100". Meta points to utility templates or the Marketing Message API instead.

Utility messages are built for this. Meta's utility message guide defines them as template messages carrying "order or account status updates, and appointment or event reminders", personalised with a name or an appointment date. What the guide spells out:

  • you can clone one of Meta's templates or create your own; a Page-owned template receives approval "within seconds of creation";
  • your app needs the page_utility_messaging permission;
  • the Page does not need to be linked to a business;
  • utility messages must not contain marketing material, and a template with marketing content is rejected with the reason TAG_SHOULD_BE_MARKETING.

In practice, ask your tool one question: which mechanism sends the reminder outside the window? If the answer is one of the three retired tags, those reminders have been failing since 27 April. And keep reminders strictly about the call: no offer, no upsell.

Want your Messenger leads qualified, booked and followed up without hiring a setter? Start your 7-day free trial.

Handing the lead to a closer with Conversation Routing

The handoff mechanism changed too. Meta's Conversation Routing page opens with a warning: "Meta no longer supports Handover Protocol for Messenger and all the businesses are migrated to Conversation Routing". Most Handover Protocol calls keep working.

The model in plain terms:

  • one default application answers when no other app holds the conversation, and the Meta Business Suite inbox can play that role;
  • the app holding a conversation is its thread owner; it can pass control to another app, release it, and other apps can take or request it;
  • thread control expires after 24 hours of inactivity unless the owner extends it; for Click-to-Messenger ads, a setting introduced on 22 July 2025 lets the app keep control for up to 30 days;
  • if someone moves a message to the Main folder of the inbox, or replies from the inbox in a conversation the inbox does not control, the inbox takes control.

For a team, the clean setup is short. The bot owns new conversations, qualifies and books. When the lead is booked or asks for a person, the bot passes control to the inbox where the closer works. The trap is running without a default application: Meta notes that in that mode all apps can answer the same message, and that coordination between the app and the inbox is needed "to ensure no duplicate responses". How the roles split on the sales side is in our setter closer model.

Bookings made inside Messenger now reach your tools

Since 3 March 2026, according to the changelog, appointment booking data from Messenger is exposed in the Conversations API and in webhooks, so "partners can access appointment details" without switching to Meta Business Suite. The messages webhook reference lists the fields of the appointment_booking attachment:

Field Content
booking_id ID of the booking
status requested, confirmed, declined or cancelled
start_time, end_time Unix timestamps in seconds
timezone IANA identifier, for example America/Los_Angeles

When the business confirms or declines, the message echoes webhook carries the updated data. Two consequences. If some leads book through Messenger and others through your calendar link, one tool can now see both. And a requested booking is not a confirmed call: your reporting should count confirmations, not requests.

Meta Business Agent or a third party setter

On 3 June 2026, at its Conversations event in London, Meta introduced the Meta Business Agent. Its announcement on the WhatsApp Business blog says the agent "books appointments and qualifies incoming leads" and "lets you decide when a team member steps in", and that "more than one million businesses are already using a Meta Business Agent on WhatsApp and Messenger". It adds: "Getting started with the Business Agent is free. In the coming months, businesses will access the agent through our paid subscription offerings."

One detail from the same post matters for a booking flow: connecting "with the tools to manage your calendar" appears, in that June post, among the capabilities Meta says it will add in the future.

So the honest starting point is your own situation, not a feature list:

  • One Page, one person answering, bookings you can confirm by hand. Try Meta's agent first: it is free to start.
  • Leads arriving on Instagram, WhatsApp and Messenger. Check whether one inbox can hold the three channels with the same qualification rules.
  • Several closers sharing calls. Check how a booked lead reaches a named closer, and who owns the thread afterwards.
  • An agency with client Pages. Check how client accounts stay separate and how results are reported per client.

Before you switch on a Messenger chatbot that books calls

  1. Entry points listed: ads, m.me links with a ref parameter, Get Started, comments. A private reply to a Page comment is allowed within 7 days of it.
  2. Bot type declared: hybrid if a person ever takes over.
  3. Every input answered within 30 seconds, typed sentences included, if the bot is declared automated.
  4. Disclosure line written for California and German audiences, repeated when the bot resumes after a human.
  5. Reminders on utility templates, with no promotional content.
  6. A default application set in Conversation Routing, and the pass to the closer's inbox tested.
  7. The vendor's Meta access checked: an app used by people without a role on it needs Business Verification, and Advanced Access through App Review, says Meta's Messenger Platform overview. App Review is not required if you only message for your own Page.
  8. Client access collected properly, for an agency: see our client account access checklist.

Running the same flow on other channels? The WhatsApp rules are in our note on the WhatsApp AI chatbot, and the Instagram clocks and limits in Instagram messaging API rate limits.

Where SetScale fits

SetScale is an AI setter in DMs, on Instagram, WhatsApp and Messenger, for people who sell a service. Every plan runs the full setter: it qualifies leads, books appointments and sends follow ups, from a single inbox. You start solo, on one account; when you grow, you add closers, accounts or client spaces without changing tools. The Scale and Business plans add the agency layer: separate client accounts, closers, reporting per client, white label and API.

See the Messenger page, or read our guide to the AI appointment setter.

FAQ

Is a Facebook Messenger chatbot free? On Meta's side, yes: "the Messenger Platform is free to use". Marketing messages to opted-in subscribers are charged per message, and the tool that runs your bot has its own subscription.

How long can a Messenger chatbot reply after someone writes? For most actions, 24 hours; after a first message sent from a Click-to-Messenger or Click-to-Direct ad, up to 7 days according to the policy updated on 28 September 2026. After that: non promotional message tags, a manual reply under the Human Agent tag within 7 days, or a one-time notification the person asked for.

Does a Messenger chatbot have to say it is a bot? When applicable law requires it, yes, at three moments: the start of the thread, after a significant lapse of time, and when a human hands the chat back. Meta names California and Germany and recommends disclosure everywhere.

Can a Messenger chatbot send appointment reminders? Yes, through utility templates, which Meta lists for "appointment or event reminders". The older CONFIRMED_EVENT_UPDATE tag returns error code 100 since 27 April 2026. A reminder must not contain marketing content.

Conclusion

A Facebook Messenger chatbot that books calls in October 2026 is constrained less by what it says than by when and how it says it: inside the window, within 30 seconds, with a disclosure where the law asks for one, and with reminders on templates rather than retired tags.

Write those four points into your setup before launch, set the handoff to your closer in Conversation Routing, and re-read the policy page each time its date changes. The last update was 28 September 2026.

Start your 7-day free trial