Canned responses
Canned responses are reusable quick replies for common customer questions, so agents don't retype the same answers. Build a small library of your most-used messages here; agents pick from them in the chat window. The header shows a running count of how many you've saved.
Creating a response
Fill in the add-response form and click Add Response (disabled until the response text isn't empty):
- Response text — the message itself, for example "Thank you for contacting us! How can I help you today?" This is the only required field.
- Link to task (optional) — attach the response to a flow. Only active (non-disabled) flows appear in the list. Use this when a canned reply belongs to a specific workflow.
- Variables (optional) — add placeholder names (type and press enter) that get filled in automatically when the response is used, so a single template can be personalized per customer.
Each response is added to the list immediately on save.
Creating canned responses with Copilot
Ask Copilot in the dashboard to add or update a canned response. Specify chat, email, or both; new responses default to chat when no channel is specified. For example:
Add a canned response for both chat and email: Hi [Customer name], we are checking your order [Order ID].
Copilot matches clearly dynamic fields to known data points and uses their exact names in double curly braces, such as {{customerName}} and {{selectedOrderName}}. The canned response review card shows the proposed text, channel, and registered variables. Click Save to save the response and its variables together. When automatic applying is enabled, Copilot can apply the requested change and show an undo control.
Copilot uses built-in variables, the account's data points, and collected values from its tasks. When a field has no clear match, Copilot leaves a manual placeholder, such as [Coupon code], and explains what needs attention. You can provide the correct data point name in a follow-up. Ask Copilot to keep text verbatim or use no variables when you want a fixed response.
Variables fill when an agent inserts the response into a chat or email. Values must already exist in the current conversation or ticket context. Inserting a response does not fetch missing data or run a workflow; a variable without a value stays as a placeholder for the agent to review before sending.
Managing responses
Saved responses appear in a numbered list. Each shows its text, a purple tag for its linked flow (if any), and blue {{variable}} tags for any variables. Hover a row to reveal:
- Copy — copies the response text to your clipboard.
- Delete — removes the response, after a confirm prompt.
If you have no responses yet, the list shows an empty state prompting you to add your first one.