Facebook & Messenger
Every Page you run, pinned to one desk
Connect the Facebook Pages you manage and work the whole surface — Messenger threads, comments, publishing and an optional DM agent — from one workspace and one API.
Kalyani Motors
DefaultAgent: Showroom agent
Meera Bakes
No agent attached
- The first Page you connect becomes the default.
The desk at a glance
- Newest 200
- threads returned per inbox call — every connected Page in one list, newest first.
- 24 h → 7 d
- the messaging window: standard replies for a day, the human-agent tag up to a week, refused after.
- Not metered
- reading threads, sending replies, publishing and comment moderation consume no API credits.
One rail, every Page’s threads
The console inbox lists the newest 200 Messenger threads across every connected Page — each row carries the Page it belongs to and the window it sits in.
Reading is all the console does here. Replies leave through the API — POST /api/v1/facebook/messages — or through an agent you attach to that Page’s DMs. Try the rail: filter by Page, open a thread, flip an agent on.
Priya S. · Kalyani Motors2 h ago — 24 h window open
Hi, is the showroom open tomorrow?
API reply
Perfect, see you then.
This inbox is read-only
A reply goes out through the API — or through the attached DM agent — not from a box here. This thread would be answered with:
POST /api/v1/facebook/messages
{
"page_id": "102938475610293",
"recipient_id": "6284719203847561",
"text": "…"
}Agent status on Kalyani Motors: attached — Showroom agent answers DMs · PATCH /facebook/pages/{ref}/bot
Simulated example — the outcome depends on when the customer last wrote
Sends normally
Within 24 hours of the last inbound message, a reply sends as an ordinary message.
Meta’s window, drawn on the wall
A business can only answer for a limited time after the customer’s last message. CallMissed enforces the window before any upstream call, measured from the thread’s last inbound message — so a refused send fails fast, not silently.
Inside 24 hours. The reply sends as an ordinary message.
24 hours to 7 days. The reply goes out as a human-agent tagged message. That needs Meta’s Human Agent approval — until granted, Meta may still reject it.
Past 7 days. Refused with a 400. The customer has to message again to reopen the window — and no one can be messaged who never wrote to your Page first.
Publishing is a ticket with real bounds
Text and link posts schedule 10 minutes to 75 days out. Photo posts carry a set of 2 to 30 images. Reels get their own window — up to 29 days. Pick a format and the ticket shows the body it would send.
Every media file must sit at a publicly reachable URL — Meta fetches it from its own servers. The Page is resolved from your workspace: the only one, the default, or the one you name with ?account=.
Publishing reference in the docsSimulated example — the card shows the request, nothing posts
POST /api/v1/facebook/posts
- message
A post needs a message, a link, or both.
When
Goes live immediately — no schedule field sent.
Request body
{
"message": "Winter service special is on now."
}The comment thread is a desk job too
Read the comments on a post and its replies, then act on each row: answer as the Page, hide it from public view without losing it, or delete it outright.
Comment lists are cursor-paginated, so the board stays honest while new comments arrive. A delete is permanent — hiding first is the reversible option.
Simulated example — actions map to the real comment endpoints
Post: “Winter service special is on now.” — 4 comments
Ritu S.
3 likes · 1 replies
Do you deliver to Pune?
Example commenter
0 likes · 0 replies
Is the Saturday service slot still open?
Example commenter
1 likes · 0 replies
Check my profile for a better deal!!!
Example commenter
6 likes · 2 replies
Loved the delivery experience last week.
The whole desk, in the console
See which Pages have an agent attached, watch it answer a Messenger question in the inbox, then reply to one comment as the Page and hide a spam one.
A draft on the desk, not a post on the Page
Social Studio turns a topic into a caption and image draft for your connected Facebook Page. Nothing it makes is published — you review the draft, edit it, then send it through the publishing API yourself.
See Social StudioSimulated example — draft content and figures are invented
Studio draft — for review
New this week: winter servicing that comes to you. Bookings are open for January.
Generated image draft
200
Threads read
64
Replies sent
98%
Delivered
Channel analytics track messaging volume and a delivery funnel alongside the inbox.
Three pins to a working desk
01
Connect a Facebook Page you manage — a one-time sign-in flow in the console. Connect several; the first becomes the default and you can move it.
02
Decide per Page whether an agent answers its DMs. Attach one of your configured agents, or leave bot_id null and answer through the API yourself.
03
Read threads and comments in the console, publish posts and reels over the API, and let Social Studio hand you caption and image drafts to review.
Read this before you start
You need a Facebook Page and an account with the required permissions. Messaging and publishing depend on platform review, account eligibility and the messaging-window rules. Connecting a Page is not permission to contact anyone without consent — a conversation always starts with the customer.
Create an account, connect a Page, and the desk is yours.
Pinned questions
What do I need before connecting?
A Facebook Page you manage, and a Facebook account with the permissions the Page requires. Connecting is a one-time sign-in flow in the console, and you can connect several Pages — the first becomes the default, and you can change the default later.
Can I reply to Messenger threads inside the console?
The console inbox is a read-only view: the newest 200 threads across every connected Page, with messages fetched per thread. Replies are sent through the API — POST /api/v1/facebook/messages — or automatically by an agent you attach to the Page.
What is the messaging window?
Meta only lets a business reply for a limited time after the customer’s last message. Within 24 hours a reply sends normally. From 24 hours to 7 days it sends as a human-agent tagged message, which needs Meta’s Human Agent approval and may still be rejected until granted. Beyond 7 days the send is refused — the customer has to message again to reopen the window. You can never message someone who has not messaged your Page first.
Can an AI agent answer my Page’s DMs?
Yes. Attach a configured agent to a Page and it answers incoming DMs from its own instructions and knowledge. Detaching is one call — send bot_id: null — and the Page keeps receiving messages; they simply stop being answered automatically.
What can I publish, and how far ahead can I schedule?
Text and link posts can publish now or be scheduled 10 minutes to 75 days out. Photo posts take one image or a multi-photo set of 2 to 30. Reels publish a video from a public URL and can be scheduled up to 29 days out. Every media file must be at a publicly reachable URL — Meta fetches it from its own servers.
What does it cost?
Social messaging, publishing and comment moderation are not metered — reading threads, sending replies, publishing posts and moderating comments do not consume API credits.
Put your Pages on the desk
Connect a Page, read its threads beside your other Pages, and let an agent or your own integration answer inside the window.
Open the Facebook desk