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

# No Match Reply

> Catch incoming messages that don't match any keyword automation, so customers never get silence.

## What is this?

**No Match Reply** fires when an incoming message doesn't match any **Message Received** keyword automation on that channel. It's the fallback that keeps a customer from being ignored just because they didn't type an expected keyword.

## How to use it

<Steps>
  <Step title="Create the workflow">
    Go to **Automation → Create Automation**, choose the channel, and pick **No Match Reply** as the **Trigger Type**. See [Create a Workflow](/workspace/automation/create-a-workflow).
  </Step>

  <Step title="Reply with a way forward">
    Send a short message that either lists the main keywords or hands off to a teammate — don't leave the customer at a dead end.
  </Step>

  <Step title="Test, then activate">
    Send a message that matches none of your keyword automations, confirm this flow catches it, then activate — see [Manage Live Flows](/workspace/automation/manage-live-flows).
  </Step>
</Steps>

<Tip>
  Keep only one **No Match Reply** automation active per channel. If several exist, only one predictable flow should own the fallback.
</Tip>

## Troubleshooting / Technical Notes

* **It fires for a message you expected to match.** Check the keyword spelling and phrasing on the matching **Message Received** automation.
* **The flow never runs.** Check that it's **Active** and the channel matches the conversation.

## Related docs

* [Triggers](/workspace/automation/triggers/overview)
* [Message Received](/workspace/automation/triggers/message-received)
* [Create a Workflow](/workspace/automation/create-a-workflow)
* [Manage Live Flows](/workspace/automation/manage-live-flows)