Messenger handover protocol: sharing a Page's inbox between an AI agent and people
Meta replaced the Messenger handover protocol with Conversation Routing, which keeps its thread control calls: pass_thread_control hands a conversation to another app, such as the Page inbox with app ID 263902037430900, take_thread_control claims it, request_thread_control asks for it, and release_thread_control returns it to idle. With routing on, the app that controls a thread receives its messages and the others get them on the standby channel.
easyCoexistence gives your AI agent a Page's Messenger conversations through one MCP connector: send_social_dm replies inside the 24-hour window and new messages are forwarded to your endpoint as they arrive.
The target_app_id Meta gives for passing control of a conversation to the Page Inbox.
Subcode, under error 10, for a message that failed because another app controls the conversation.
Without a message from the person for this long, a thread goes idle, and only the default app can then send.
How far extend_thread_control can stretch an app's control beyond the 24-hour response time frame.
Take control of conversations with your Business AI; while off, untagged sends to a Business AI conversation fail with 10, 2018300.
What happened to the handover protocol?
Meta folded it into Conversation Routing. Its guide says Meta no longer supports the handover protocol for Messenger, that businesses have been migrated to Conversation Routing, and that routing is backwards compatible with most handover protocol calls, so pass_thread_control, take_thread_control and the messaging_handovers webhook are expected to keep working. What changed is who decides: the business sets a default app and routing rules in its Page settings, under Conversation Routing.
Who controls a conversation?
One app at a time, which Meta calls the thread owner. A thread is active while the person and the owning app are talking, and idle when the person has not written for 24 hours or the owner has released control; in an idle thread only the default app can send, inside the messaging window. Routing rules decide who takes a thread:
- Default app: the one that answers when no other app is configured or responding.
- Social routing: the app that takes control when the person opens an idle thread or taps Get Started.
- Link routing: an app assigned to each m.me link.
- Campaign routing: the app chosen for a Click-to-Messenger ad, in control for that conversation's messaging window, up to 7 days.
Which calls move control between apps?
Each is a POST to an edge of the Page with recipient set to the person's PSID, and each answers success true; most also take a metadata string that the next app receives:
pass_thread_control: hands the thread to the app intarget_app_id, which receives amessaging_handoversevent.release_thread_control: ends the app's control and returns the thread to idle.take_thread_control: makes the calling app the owner, for apps the business allows to take control.request_thread_control: asks for control of the conversation.extend_thread_control: keeps control past the 24-hour response time frame, up to 7 days, with duration in seconds.- The Send API can pass or release control with the message itself, through a
thread_controlobject.
POST /{page-id}/pass_thread_control
?recipient={id:<PSID>}
&target_app_id=263902037430900
&metadata=Customer asked for a person
{ "success": true }How do people in the Page inbox step in?
By answering. Conversation Routing treats the Meta Business Suite inbox as one more connected app, which a business can even make the default; when someone replies there in a conversation the inbox does not control, or moves it to the Main folder, the inbox takes control. An app hands a conversation to people with pass_thread_control and target_app_id 263902037430900, and an app that relays a person's reply after the 24-hour window sends it with the HUMAN_AGENT tag, within 7 days of the person's last message.
What happens when Meta's Business AI owns a conversation?
Other apps receive the person's messages on the standby channel and should not answer them. Meta's guide says to start responding after a messaging_handovers event with pass_thread_control; a messages notification may carry admin_text and a handoff_reason such as human_requested or purchase_intent, but it does not transfer ownership. With Take control of conversations with your Business AI off, the default, an untagged send to that conversation fails with code 10, subcode 2018300.
How does an app check who owns a thread?
GET /{page-id}/thread_owner with recipient set to the PSID returns the owning app's app_id and when its control expires, to the owner itself or to the Page's default app. The is_owner field of the Conversations API answers the same question per conversation once routing is on, and GET /{page-id}?fields=messaging_feature_status shows the Page's Conversation Routing status in fields such as msgr_multi_app.
What happens without Conversation Routing?
Meta calls it default behavior, meant for a Page with one connected app that receives and answers messages on its own. All connected apps receive messaging webhooks and can answer the same message, take_thread_control is blocked until a default app is set, and only campaign routing is available. Meta's advice for this setup is to coordinate the app and the Page inbox so nobody answers the same message twice.
What does easyCoexistence do in a shared inbox?
It subscribes each Page to feed, messages and mention, not to messaging_handovers, standby or message_echoes, so it forwards the person's messages while its app receives them and sees neither handover events nor replies sent from the Page inbox. send_social_dm sends a RESPONSE without thread_control, and when Meta refuses a send because another app holds the conversation, the tool returns Meta's code 10 and message to your AI. The thread control calls, thread_owner and is_owner are not among its tools.
Common mistakes
- Answering standby messages. They reach an app that does not own the thread; wait for pass_thread_control before replying.
- Reading admin_text as a handover. A messages notification with handoff context does not transfer ownership; the messaging_handovers event does.
- Running an AI and the inbox side by side without routing. With default behavior both receive the message, and Meta asks for coordination to avoid two replies.
- Holding a thread after the flow ends. Meta recommends releasing control as soon as the app is finished, instead of waiting for the response time to expire.
Meta's thread control calls are not among its tools; a person takes a conversation over by replying in the Page inbox. US$ 9 to US$ 0.75 per connection per month, falling as you add connections, with the first 3 days free.
easyCoexistence is a multichannel API and MCP server that connects AI agents such as Claude and ChatGPT to WhatsApp, Instagram, TikTok, Facebook and more. On WhatsApp it uses Coexistence: the business keeps using its number in the WhatsApp Business app while the AI works through Meta's official API.
Frequently asked questions
Do two apps on one Page need Conversation Routing?
Meta recommends it when several messaging apps are connected and each should answer certain conversations. With one app receiving and answering, default behavior is enough.
How long does an app keep control of a conversation?
Until it releases control or the thread goes idle, 24 hours after the person's last message. extend_thread_control adds time, up to 7 days.
Does a reply from the Page inbox reach other apps?
Apps subscribed to message_echoes receive it as an echo whose app_id is the Page inbox's, 263902037430900, as Meta's changelog describes for Graph API v12.0 and later.
What happens to easyCoexistence's replies when a person answers from the inbox?
With Conversation Routing on, the inbox takes control, and until control returns the person's messages reach easyCoexistence's app only on standby, which it does not subscribe to. Without routing, both keep receiving them.
Keep reading
Connect your first channel in two minutes.
No platform reviews to wait for. Connect WhatsApp, Instagram, TikTok or another channel, then ask your AI to post, reply or report, and watch it work.
- 3 days free
- Cancel any time
- Official APIs only
- Monitored 24/7
Verified on