Chapter 1 · The scenario
Example: A houseboat enquiry in Kochi
A traveller messages a Kochi travel agency's Page from a post about houseboat packages on a Friday evening. The bot answers inside the window with prices and a carousel of boats, and flags the conversation for the sales desk. The agent who picks it up on Monday is past 24 hours but within seven days, so she replies with the HUMAN_AGENT tag. When the booking is paid, the confirmation and the day-before reminder go out as utility message templates — the agency used to send them with the CONFIRMED_EVENT_UPDATE tag, which has returned error code 100 since 27 April 2026.
Chapter 2 · What is the Messenger Platform?
The Messenger Platform is Meta's set of APIs for businesses to talk to people on Facebook Messenger as a Facebook Page. Incoming messages, button postbacks and delivery and read events arrive at your webhook; replies go out through the Send API, a POST to /{PAGE_ID}/messages on the Graph API with a Page access token. Each person is identified by a page-scoped ID (PSID) — an identifier unique to that person and that Page — rather than by a phone number.
Its core rule is the standard messaging window. When a person messages the Page, taps a button or otherwise acts, the Page has 24 hours to respond, and Meta's policy allows promotional content inside that window; the first message after a Click-to-Messenger ad can open a window of up to seven days. Outside the window a Page needs an approved route: the HUMAN_AGENT tag lets a person on your team reply manually within seven days, and Meta points other out-of-window updates to utility message templates and the Marketing Messages API. Since 27 April 2026, requests using the CONFIRMED_EVENT_UPDATE, ACCOUNT_UPDATE and POST_PURCHASE_UPDATE tags return error code 100.
It resembles WhatsApp's model but differs where it matters. The WhatsApp Cloud API addresses people by phone number, lets a business open a conversation with an approved template and charges per delivered message by category. On Messenger the person must reach the Page first, the ID only works for that Page, and the Page's name and profile are the business identity. Both are OTT messaging channels run by Meta, so many teams answer them side by side in an omnichannel inbox.
Key takeaways
- The Messenger Platform is Meta's API for Facebook Pages to send and receive Messenger messages, using the Send API and webhooks.
- People are addressed by a page-scoped ID (PSID), not a phone number, and a Page only gets a PSID once the person contacts it.
- A Page may reply freely, promotions included, for 24 hours after a person's action; outside that window it needs an approved route.
- Since 27 April 2026 the CONFIRMED_EVENT_UPDATE, ACCOUNT_UPDATE and POST_PURCHASE_UPDATE tags return error 100; HUMAN_AGENT remains.
- Unlike the WhatsApp Cloud API, there is no template-first outreach to phone numbers: the conversation starts with the person.
Chapter 3 · How it unfolds
How does the Messenger Platform work?
Connect a Page to your app
Subscribe the app to the Page's
messages,messaging_postbacksand related webhook fields, and use a Page access token with thepages_messagingpermission; live use needs App Review.Receive the person's message
Your webhook receives an event whose
sender.idis the PSID. That action opens or renews the 24-hour standard messaging window.Reply with the Send API
POST to
/{PAGE_ID}/messageswithrecipient.idset to the PSID,messaging_typeset toRESPONSE(orUPDATEfor a proactive message inside the window) and the message object.Escalate before the window closes
Hand complex cases to a person. With
messaging_typeMESSAGE_TAGand theHUMAN_AGENTtag, a human agent can still reply manually for up to seven days.Plan out-of-window updates
Send later order or booking updates as utility message templates and promotions through Meta's marketing messages for Messenger. The three retired tags fail with error 100.
Chapter 4 · In code
The Messenger Platform in code
curl -X POST "https://graph.facebook.com/v26.0/{PAGE_ID}/messages?access_token={PAGE_ACCESS_TOKEN}" \-H "Content-Type: application/json" \-d '{"recipient": { "id": "{PSID}" },"messaging_type": "RESPONSE","message": { "text": "Yes, a two-bedroom boat is free on 14 November. Shall I hold it for you?" }}'# Response# { "recipient_id": "{PSID}", "message_id": "m_AG5Hz2U..." }
Reply inside the standard messaging window: the PSID comes from the person's own message.
Chapter 5 · Why it matters
Why does the Messenger Platform matter?
Messenger is often where a brand's Facebook audience already talks to it, especially from Page posts and ads. Building on the Platform correctly means answering inside the window, escalating to people before it closes and planning later updates as utility templates rather than tags that now fail. Knowing how it differs from WhatsApp stops teams copying WhatsApp logic — phone-number lookups, template-first outreach — into a channel that does not work that way.
Chapter 6 · The facts
The Messenger Platform: key facts and limits
| Send endpoint | POST /{PAGE_ID}/messages (Graph API) |
|---|---|
| Recipient ID | Page-scoped ID (PSID), unique per person per Page |
| Standard window | 24 hours after the person's action |
| After a Click-to-Messenger ad | Window can last up to 7 days |
| Human agent tag | HUMAN_AGENT: manual replies within 7 days |
| Retired tags | Return error 100 since 27 April 2026 |
| Business-initiated outreach | None to phone lists: the person contacts the Page first |
Chapter 7 · Where it goes wrong
Common mistakes with the Messenger Platform
Treating a PSID as a global user ID
A PSID belongs to one Page. The same person has a different PSID on your other Pages and unrelated IDs on Instagram and WhatsApp, so link them in your CRM rather than assuming they match.
Still sending the retired tags
CONFIRMED_EVENT_UPDATE, ACCOUNT_UPDATE and POST_PURCHASE_UPDATE have returned error code 100 since 27 April 2026. Move those flows to utility message templates.
Using HUMAN_AGENT for automation
The tag is for a person replying manually. Bot or promotional messages sent under it break policy and can restrict the Page's messaging.
Copying WhatsApp logic
There is no template-first outreach to a list of phone numbers. Design acquisition around Page posts, ads and the Page's chat entry points instead.
Chapter 8 · Messenger Platform FAQs
Messenger Platform FAQs
What is a PSID in the Messenger Platform?+
Can a Page message someone after 24 hours on Messenger?+
Is the Messenger Platform the same as the WhatsApp Business API?+
Which Messenger message tags still work in 2026?+
Chapter 9 · What good teams do
Best practices for the Messenger Platform
- Show agents the 24-hour countdown and the seven-day human-agent deadline on every Messenger conversation.
- Store each PSID per Page alongside the phone number and WhatsApp ID in one customer profile.
- Answer automated replies within seconds and say clearly when a person will take over.
- Pin the Graph API version in Send API calls and upgrade on a schedule.