Skip to main content
Connecting a Facebook Page brings your Messenger conversations into the DMLY Inbox, lets a bot answer them, and lets comments on your posts open a private conversation. Messenger works differently from WhatsApp in one way that shapes everything else: there are no message templates, so you can only reach people who messaged you first. Prefer to watch first? This walkthrough covers connecting a Page end to end.

​
Read this before you plan around Messenger

Messenger has no message templates. You can only send freely to someone who has messaged your Page in the last 24 hours, with one exception: if a contact accepted a Marketing Opt-in request, DMLY can send them one further automated message outside the window. Otherwise automated messages and broadcast sends outside the window are skipped, not queued.
That has two practical consequences:
  • Broadcasts on Messenger are freeform text. They reach contacts inside the 24-hour window, plus anyone who accepted a notification opt-in (pick the Opted in — notifications or Messaging window open (24h) audience). Everyone else is recorded as failed with a window_closed reason.
  • Messenger is a reply channel, not an outreach channel. For anything you need to initiate (reminders, promotions, follow-ups), use WhatsApp.
The Default reply section on Bot setup works on Messenger. When a contact sends a message that matches no flow and no keyword, DMLY sends the reply you configured here, honouring Once per 24 hours per contact or Every time. Any message the contact sends counts: a typed message, but also a photo, video, file, story reply or shared post. A bare QR-code or link open that carries no message doesn’t trigger it, and it never fires for a contact who has opted out or had the bot paused. See Bot setup.

​
Before you start

  • You must be an admin of the Facebook Page. The Page picker lists only Pages you administer. If the Page is missing, your Facebook role is the reason.
  • Your plan must allow a Facebook channel. If it doesn’t, the connect button stops you before Facebook’s permission screen appears.
  • Connecting with a personal Facebook account is fine. DMLY asks Facebook for permission to read and reply to your Page’s messages; it never gets your Facebook password.

​
Connect the Page

1

Open the channel list

Go to Integrations → Channels and start adding an account.
2

Choose Facebook Page

Select the Facebook Page tile (Connect a new Facebook page).
3

Approve on Facebook

Facebook asks you to sign in and approve the permissions DMLY needs, including reading and sending your Page’s messages. Approve all of them; declining any one of them can leave the channel connected but silent.
4

Pick the Page

Choose the Page you want from the list Facebook returns, and finish.
DMLY then creates the Channel, stores the Page’s access credentials, and asks Facebook to start delivering that Page’s messages, comments and mentions. If that last step is refused, the Page connects but nothing arrives. See Fix a silent Facebook Page or Instagram account.
Connecting Instagram uses the same Facebook permission screen, because Instagram DMs are delivered through the linked Facebook Page. See Instagram.

​
What you get

Unified inbox

Messenger conversations sit alongside WhatsApp and the rest, with assignment, statuses and quick replies.

Bots and flows

Trigger a flow on a new message, a story reply, or a comment on your posts.

Freeform broadcasts

One-to-many plain messages, delivered to contacts inside the 24-hour window, plus anyone who accepted a notification opt-in.

Comment to DM

A new comment on a post can open a private conversation, which is not limited by the 24-hour window.
Messenger contacts arrive with a placeholder name like Messenger user <last 4 digits> and are renamed once Facebook returns the person’s profile. They become ordinary Contacts, the same record used everywhere else in DMLY.

​
The 24-hour window, precisely

The clock starts at the contact’s last inbound message and runs for 24 hours. The 7-day allowance is Meta’s rule for a human agent answering a customer. It applies to a reply you send from the Inbox, not to automation.
The Message step of a Messenger broadcast has a Reach choice, which shows a Marketing Messages (paid) option for reaching opted-in people outside the window. It is labelled Coming soon and cannot be used yet.
If someone replies stop, unsubscribe, cancel or similar, DMLY opts them out: it tags them, cancels their running flows and sequences, and refuses further automated sends. You can still reply by hand. start or subscribe opts them back in.

​
Bot setup: what syncs to the Page on save

Open Bot setup and pick your Facebook Page from the channel selector. Saving does two things: it stores the settings in DMLY, and it pushes the menu-style parts straight to your Page on Facebook. A few rules Facebook imposes, which DMLY applies for you:
  • Get Started is automatic. Facebook only shows a greeting, menu or ice breakers if the Page has a Get Started button, so DMLY adds one as soon as you configure any of the three.
  • Turning something off and saving removes it from the Page. Facebook needs to be told explicitly to clear a field, so an empty section is actively deleted rather than left behind.
  • Ice breakers: up to 4. Questions longer than 80 characters are shortened.
  • Persistent menu: up to 3 items per level, 3 levels deep. Labels longer than 30 characters are shortened.
  • Menu items that open a URL or start a flow work. A menu item set to Postback does nothing useful: the payload you type is never acted on. Use Start flow instead.
The Buttons editor under the Welcome message works: up to three buttons are delivered with the welcome message as tappable buttons. A URL button opens a link, a Start flow button launches that flow, and a plain reply button posts back so a keyword automation can react to the tap. The buttons editor on Default reply works the same way. Ice breakers and the Persistent menu are still there for always-available prompts.
If the push to Facebook fails, saving still succeeds and you get a warning: “Saved, but syncing to Meta failed”. The reason is in Logs, usually an expired Page connection or a missing permission.

​
What you can send

Beyond plain text and media, Messenger flows can send tappable buttons (up to 3, short labels) and quick replies (up to 13), including native chips that ask for the contact’s email or phone number. Carousels are supported. WhatsApp-only message types are not available here.
There are four causes, they look identical from the outside, and three of them you can fix yourself. Work through Fix a silent Facebook Page or Instagram account, which tells you how to tell them apart.The fastest first check: if messages do reach the Inbox and it’s only the bot that stays quiet, the connection is fine and your automations are pointing at an older copy of the Page. That page covers it.
When Facebook rejects a send because the Page access is no longer valid, DMLY marks the channel as needing attention and emails your workspace admins a reconnect prompt. Reconnect the Page from Integrations → Channels.

​
Next

Bot setup

Welcome message, ice breakers and the persistent menu.

Ice breakers

The suggested questions first-time visitors see.

Persistent menu

The always-available menu in the conversation.

Broadcasts

Who a Messenger broadcast can actually reach.