> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jelou.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Feed private reply

> Choose whether the conversation is assigned to the agent or routed to a workflow based on the message keyword.

This setting defines **what happens when a user replies on Messenger** to a private reply that an agent sent from a comment on a Facebook post.

The setting is defined per **Facebook Feed** channel and applies only to conversations that start from a private reply.

> [!NOTE]
>
> You can find this option under **Settings → Automations → Feed private reply**. It only appears for **Facebook Feed** channels and for users with channel settings permission.

## How a private reply works

**1. A user comments on a post**

The comment arrives through your **Facebook Feed** channel.

**2. The agent sends a private reply**

From the post in monitoring, the agent clicks **Send private reply** and sends a single Messenger message to the person who commented.

**3. The user replies on Messenger**

The message you sent **does not create a conversation yet** in the Inbox. The conversation is created only if the user replies.

**4. This setting decides who handles it**

Depending on the selected mode, the conversation is assigned to the agent or a workflow runs.

## Response modes

| Mode | Behavior |
| - | - |
| **Assign to agent** | When the user replies, the conversation is assigned directly to the agent who sent the private reply. This is the default mode. |
| **Route to workflow** | When the user replies, a workflow runs based on the keyword in the message. If no keyword matches, the default workflow runs. |

## Assign to agent mode

It needs no extra configuration. Select it and click **Save**.

## Route to workflow mode

Configure two elements:

1. **Default workflow** (required): runs when the user's reply doesn't match any keyword.
2. **Keyword routes** (optional, up to **5**): each route links up to 5 keywords to a workflow.

The available workflows are:

* Those of the **Messenger channel linked** to the Facebook Feed channel.
* Only those with **Facebook** among their channels.
* Listed in alphabetical order.

Channel requirements:

| Condition | What you see |
| - | - |
| The Facebook Feed channel has no linked Messenger channel | "To use workflow routing, this channel must have an associated Messenger channel. Contact your administrator to set it up." |
| The linked Messenger channel has no Brain | The workflow selector is disabled with the error "This channel has no Brain configured". |

## How changes are saved

Changes are saved in two different ways:

| Action | When it's saved |
| - | - |
| Changing the mode and default workflow | When you click **Save** in the header |
| Adding, editing or deleting a route | **Immediately**, when you confirm in the modal or delete the row. If it fails, the change is reverted |

## Sending the private reply from the Inbox

The agent sends the private reply from the post in monitoring, using the **Send private reply** modal.

| Aspect | Rule |
| - | - |
| Content type | Text, image, document or video; **only one per message** |
| Text | Maximum 2000 characters |
| Image | PNG, JPG or GIF · maximum 5 MB |
| Video | MP4 or MOV · maximum 25 MB |
| Document | PDF, DOCX or XLSX · maximum 15 MB |
| Limit per person | **Only one** private reply per person; once sent, the button is disabled |
| Delivery channel | Messenger |

Once sent, the post shows the **Private reply sent** banner, a preview of the message, and a notice that the conversation will be created and assigned automatically if the user replies on Messenger.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.