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

# Create and use saved replies

> Save answers your team sends often while keeping each reply personal.

<Note>
  This guide includes features awaiting release. If an option is not available in your workspace, contact StackShift Support.
</Note>

## What you can do

Save answers your team sends often while keeping each reply personal. Where to find it: Saved replies; insert them from a conversation composer.

## Before you start

* Permission to manage saved replies for creation; conversation reply access to use them.

## Steps

<Steps>
  <Step>
    Create a saved reply with a name your team can find, such as Delivery tracking or Returns instructions.
  </Step>

  <Step>
    Write the reusable answer. Keep customer-specific details out of the saved text unless you will replace them before sending.
  </Step>

  <Step>
    Save it, then open a test conversation and insert it into the composer.
  </Step>

  <Step>
    Read the inserted reply, update names and details, and send it only when it answers that customer’s question.
  </Step>

  <Step>
    Edit outdated replies when your policies change. Remove replies that staff should no longer use after reviewing the confirmation.
  </Step>
</Steps>

## Example

Save a returns explanation and personalize the order number before sending.

## Things to know

* Inserting a reply is not sending it. You remain responsible for the final message.
* Keep links current and avoid promises that depend on an unverified order or payment.

## What happens next

<Check>
  Staff can reuse approved wording without automatically sending it.
</Check>

## If something goes wrong

<Warning>
  * Cannot find a reply: check your workspace and any search/filter you applied.
  * A reply contains stale information: correct the saved version and review the draft already inserted in the conversation.
</Warning>

## Related guides

<CardGroup cols={2}>
  <Card title="Reply, add private notes and work together" href="/stackshift-support/reply-and-collaborate">
    Keep customer replies separate from internal discussion.
  </Card>
</CardGroup>


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