Facebook opened Messenger's chat pipes to outside businesses

The conversation

On 12 April 2016, at its F8 developer conference, Facebook told developers that starting that day, all developers and businesses would be able to build bots for Messenger and submit them for review. The company's own announcement described the launch around three capabilities: a Send/Receive API for text, images and interactive rich bubbles; structured Generic Message Templates with buttons and calls to action; and a customizable welcome screen shown when someone first opens a conversation with a business. Facebook said Messenger was used by 900 million people every month at the time, and separately introduced natural-language help through what it called the wit.ai Bot Engine.

What the documents show

The F8 post is a company describing its own newly opened platform; it does not describe how the platform functions ten years later. Meta's own Messenger Platform documentation, retrieved 16 September 2026 through an archived copy after the live documentation returned a server error during this research, states plainly what the mechanism still is: the platform lets an app send and receive messages between a Facebook business page and its customers, potential customers and followers. Its table of contents lists webhooks, a handover protocol for passing a conversation between systems, and a policy and usage guidelines section, showing that a review-and-policy layer, not just an open API, has remained part of the platform's structure since the 2016 launch.

The system boundary

The 2016 post already drew the relevant boundary: Facebook would provide the messaging pipes and templates, but the experience was the developer's to build, meaning a business's own server decides what a message means and what to send back. The submission-for-review step marked a second boundary, between what a developer could build and what Facebook would let run against real users, a distinction the current policy and usage guidelines section continues to formalize. Neither document describes a bot as an autonomous conversational agent; the platform is consistently framed as a pipe and a policy gate around a business's own logic.

Where it fails

The clearest gap in this record is that Facebook's live current documentation was not reachable directly during this research and had to be read through an archived copy, which means any very recent policy change would not appear here.

• What specific guidelines, policies and controls apply to a given automated Messenger flow today, and has the bot been reviewed against the current version rather than the 2016 baseline?
• How does the handover protocol move a conversation to a human operator, and has that handoff been tested under real load?
• Does the business have its own record of what any platform-scale figure, such as Facebook's own 900-million-user count, means for its specific customer base, rather than treating a global figure as a local one?

The 2016 launch and the current documentation agree on the basic shape: a messaging pipe, a template system, and a policy layer around whatever logic a business supplies.