Write the common replies once.
Save replies your team sends every day, then insert them with /respond and let Core fill in the ticket details.
Password resets, onboarding steps, and maintenance notices get typed again and again, a little differently each time. Canned responses give your team one approved version, with the customer, contact, and ticket details filled in for each ticket.
Canned responses
Insert with /respond
Password reset sent
- Hi {{contact_first_name}},
- We reset the password on ticket {{ticket_number}}.
- {{assigned_technician_first_name}} will follow up today.
Fast
Type /respond and pick a reply.
Slash insert. Find a response by title or shortcut in any ticket note editor and insert it at the cursor.
Meeting requests too. The meeting request dialog has its own canned response picker.
Type /respond and pick a reply.
Personal
Variables fill in for each ticket.
Ticket details. Ticket number, title, status, priority, company, contact, assigned technician, and ticket link fill in on insert.
Line breaks kept. Responses are plain text, and spacing comes through exactly as written.
Variables fill in for each ticket.
Shared
One library for the team, one for you.
Personal or shared. Keep drafts to yourself, or share a response with everyone in the workspace.
Tagged and governed. Template admins tag responses by topic and can update any shared response.
One library for the team, one for you.
Frequently asked questions
Ready to try Core?
Start a free trial or talk to us about rolling out Canned Responses with your team.