> ## Documentation Index
> Fetch the complete documentation index at: https://www.plain.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Suggested responses
> Put Ari's draft replies in the composer for a user to review, edit, and send.
**Suggested responses** surface **Ari** generated draft replies directly in the composer using your knowledge sources and the full thread context.
**Suggested responses are only available on the Horizon or Frontier plans.**
## How it works
When a new thread comes in, Plain generates a suggested reply if there is enough information in your knowledge sources and the full thread context to provide the answer. The suggestion appears directly in the composer, ready for review, edits, or sending.
The more knowledge sources you connect, the better suggestions become. This is especially effective for teams handling technical, policy heavy, or product specific questions where accuracy matters.
If Plains AI doesn't have enough information, a reply won't be generated. This helps ensure that suggested replies are always useful.
## Enabling suggested responses
1. Go to **Settings → Plain AI**
2. Toggle **Suggested responses**
Once enabled, suggestions will appear automatically in the composer whenever they're available.
Team members who prefer not to see suggested responses can toggle their visibility using the icon button directly in the composer.
## Make suggestions smarter with knowledge sources
To provide deeper and more accurate suggestions, connect your support documentation. Plain indexes it and use it alongside past conversations to generate better replies.
This matters most for B2B teams handling technical, policy-heavy, or product-specific questions. See [knowledge sources](/docs/product/agents/knowledge-sources) to get started.
You can rate any suggested response with a thumbs up or thumbs down directly in the composer. You can also leave an optional comment explaining why the suggestion was or wasn't helpful. This feedback is used to improve future suggestions.
## Bring your own suggestions
If you generate replies elsewhere, for example with your own model or an internal knowledge base, you can push them into Plain with the `addGeneratedReply` API mutation.
They appear in the composer alongside Plain's own suggestions, and the customer sees nothing until a user sends the reply.
Your API key needs the `generatedReply:create` permission, and suggested responses must be toggled on for the suggestion to appear in the composer. See [suggested replies](/docs/graphql/messaging/suggested-replies) in our API docs.