A first draft of every reply, written from your own answers.
Select Draft with Core AI in the ticket composer. Core writes a reply from the ticket and what your team already knows, and the technician decides what gets sent.
Most replies repeat something your team has already written: a KB article, a fix from last month, a checklist step. Core AI Draft Replies pulls that context into the composer so technicians start from a grounded draft instead of a blank editor.
Draft with Core AI
#2214 · VPN drops after Windows update
Draft reply · ready for review
- Hi Alex, thanks for the details on the VPN drops.
- Reinstalling the VPN client after the update fixed this for another site last month.
- I can walk you through it on a quick call if that helps.
Grounded
Drafts start from your workspace, not the open web.
Ticket context. Core reads the ticket and the latest customer message before it writes anything.
Your knowledge. Relevant KB articles, similar resolved tickets, and linked checklists shape the reply.
Ticket
KB article
Resolved ticket
Drafts start from your workspace, not the open web.
In control
Nothing is sent without a technician.
Draft, not send. The reply lands in the editor. Drafting never sends a message, changes status, or adds recipients.
Rewrite in place. Core AI rewrite tidies text you have already typed, and undo restores the original.
- Inserted as a draft
- Technician reviews and edits
- Sent only by the technician
Nothing is sent without a technician.
Boundaries
The same permissions as the ticket.
Workspace scoped. Ticket and KB retrieval stay inside the current workspace and the records the user can reach.
Untrusted input. Customer messages and retrieved KB text are treated as reference material, never as instructions.
The same permissions as the ticket.
Frequently asked questions
Ready to try Core?
Start a free trial or talk to us about rolling out Core AI Draft Replies with your team.