Overview
Canned replies allow Support Agents to create reusable responses that can be quickly added to Ticket replies. They help save time and maintain consistent responses to common customer queries.
Where to Find
Go to Support → Canned Reply.
How It Works
Create a canned reply by defining its Title, Body, Categories, and Visibility. Once created, Agents can use the canned reply when responding to Tickets based on its visibility and category.
Step-by-Step Guide
- Go to Support → Canned Reply.
- Click Add New to create a canned reply.
- Enter a suitable Title.
- Add the response content in Body.
- Select a Categories for the canned reply.
- Select the required Visibility.
- Save the canned reply.
Options / Settings
Title
Enter a suitable title that clearly identifies the canned reply.
Body
Enter the response content that will be used when the canned reply is inserted into a Ticket reply.
- You can use macros to insert dynamic information.
- Macros can include details such as Customer name, Subject, Date of creation, and Assignee.
Categories
Assign a category to organize canned replies and make them easier to find.
- Categories can be managed from Support → Settings → Canned Reply → Categories.
- You can use categories to group related canned replies.
Visibility
Controls which users can view and use the canned reply.
- Private – Only the author of the canned reply can view and use it.
- Public – All Support Agent roles can view and use it.
Example
For a frequently asked question about ticket response times, you can create a canned reply with the title Response Time, add the standard response in Body, assign an appropriate Categories, and set Visibility to Public so Support Agents can use it.
Notes / Tips
- Use clear and descriptive Title values to make canned replies easy to identify.
- Use Categories to organize frequently used responses.
- Use macros in Body when the response needs dynamic Ticket or customer information.
- Use Private visibility for responses intended only for personal use and Public for responses shared across Support Agent roles.