Facebook public thread replies
Reply publicly from an existing Facebook conversation that retains its connected Page and original public thread.
What it is
Feed Setup is the public Facebook option on a connected Page account. An existing Facebook conversation with the required Page and public-thread association can send a public reply. Ask Powerfront to confirm support for your existing connection before relying on this flow.
Who uses it and why
- Operators reply to existing public Facebook conversations where the connection supports them.
- Administrators and developers coordinate the Page connection with Powerfront and confirm whether public engagement is available for their setup.
Where to find it
Powerfront manages Feed Setup in the Facebook Messenger account editor under Settings › General Settings › Integrations. Its switch is Enable Facebook Feed Integration.
Operators reply from an existing Facebook conversation. This public reply flow is separate from a private Messenger conversation.
How it works
The conversation must retain both the connected Page and the public object or thread to reply to. INSIDE uses that Page's authorisation to submit the reply to the recorded public target.
Ordinary replies become text with retained links. Product content can become text and a linked attachment, rather than an INSIDE product card.
Confirm the conversation's public context before replying. A public reply is visible according to Facebook's visibility for the target object; it is not a private message to the customer.
Configure it
Ask Powerfront to review the Page connection and Enable Facebook Feed Integration. Confirm incoming-comment support for your existing connection before asking Powerfront to enable this option.
For an existing connection, agree a test public thread with Powerfront and verify the reply on Facebook.
Settings
| Setting | Where | Applies to | Default | Who can change it | What it does |
|---|---|---|---|---|---|
| Enable Facebook Feed Integration | Settings › General Settings › Integrations › Account Setup | channel | On in the new-account editor; Off if never saved | Powerfront | Enables the Page's public feed option separately from private Messenger. Powerfront must confirm that the existing connection supports the required public conversation flow. |
Limits and good to know
- The conversation needs an existing public target. INSIDE cannot choose an arbitrary Facebook post from the reply composer in this flow.
- Public replies and private Messenger replies use different targets and content handling.
- A transcript entry does not confirm that Facebook published the public reply. Check the target thread directly.
- Ask Powerfront which incoming public events your existing connection supports.
- Treat this as an existing-connection feature pending confirmation from Powerfront.
Depends on and works with
View all connections as a list
This feature uses
- Starting, ending and expiring chatsRequires
Replies originate in an existing Facebook conversation.
- Messages and rich contentRequires
Public replies convert supported conversation messages into Facebook comment text and links.
- Messaging channel connectionsRequires
Public replies need a connected Page and its authorisation.
- Facebook Messenger channel setupRelated
Private Messenger and public feed replies have separate enable switches on the Page account.
Used by
- Facebook Messenger channel setupRelated
Public Facebook replies use a separate feed option from private Messenger messages.
FAQ and troubleshooting
Does turning on the feed switch create a public-comment inbox?
Ask Powerfront to confirm the incoming-comment flow for your connection before using it as a public engagement inbox.
Why did a reply in INSIDE not appear on Facebook?
The target thread, Page authorisation or provider submission may have failed. Check the thread directly and give Powerfront the conversation and reply time.
Can I use this to send a private response?
Use a supported private Facebook Messenger conversation for private messaging. The public reply path sends to a public target.
Why did a product card appear differently?
The public reply path converts product content to text and a linked attachment. It does not preserve the INSIDE card layout.