> ## Documentation Index > Fetch the complete documentation index at: https://docs.ravenna.ai/llms.txt > Use this file to discover all available pages before exploring further. # Snippets > Save reusable response templates as snippets and insert them into ticket replies for fast, consistent answers. Snippets are reusable response templates that live at the workspace level. Save a frequently used reply once, then insert it into any ticket to keep tone, formatting, and policy language consistent without retyping. ## Mental model Snippets are saved response templates scoped to a workspace. Each snippet has a `name` used to find it and a `content` body that is inserted into a ticket reply. Snippets are not tied to a specific ticket, requester, or channel. They are workspace-wide building blocks the agent can pull into any outgoing message. The agent can list, search, retrieve, create, update, and delete snippets through the snippet MCP tools. *** ## When to use snippets * Inserting an established response for a recurring question instead of generating new wording each time. * Reusing approved policy language (for example, security disclosures or refund terms) verbatim. * Saving a high-quality reply you just composed so a teammate or future ticket can reuse it. * Updating a snippet when the canonical answer changes so every future reply uses the new wording. *** ## Constraints and gotchas * Snippets are workspace-scoped. A snippet created in one workspace is not visible in another. * `name` and `content` are both required and must be non-empty when creating a snippet. * Deleting a snippet is permanent. It does not affect messages that were already sent using the snippet, but the template will no longer appear in searches or future inserts. * Snippets are plain text content. They do not personalize themselves. If the saved response references a specific requester or ticket, edit the inserted text before sending.