A runbook on every ticket — drafted by Core AI, owned by your team.
Junior technicians get guided steps, senior technicians skip what they know, and every proven procedure can become a reusable template.
The hardest part of a new ticket is not knowing whether you have solved this before. Core reads your knowledge base, resolved tickets, and authored checklist templates, then drafts a concrete set of steps right on the ticket. Work it like a normal checklist — check off, skip, add notes — and promote it into a template once it is proven.
Ticket #1842 · VPN reconnect loop
Assistant-generated troubleshooting checklist
KB article
VPN split tunnel troubleshooting
Past tickets
3 resolved Meraki firewall cases
Checklist template
Remote access triage
User reports VPN reconnect loops after the firewall profile changed.
Generated from KB, checklists, and resolved tickets
1. Confirm tunnel profile and affected user group
from KB · VPN profile matrix
2. Compare firewall rule changes since last success
from resolved ticket tkt-1204
3. Restart VPN service and capture reconnect logs
from checklist · Remote access triage
4. Test split-tunnel DNS resolution
from KB · DNS over VPN
5. Promote proven fix to reusable runbook
save as template after validation
Grounded in your data
Built from the signals you already have.
KB retrieval. Semantic search across your published knowledge base surfaces the relevant articles for this ticket type.
Prior resolutions. The assistant looks at recently resolved tickets on the same type and customer so your team benefits from collective memory.
Authored templates. Checklist templates you already maintain are treated as first-class seed material — so proven playbooks keep showing up.
Matched section
5 steps · grounded
Pinned to ticket
Built from the signals you already have.
Runs inside the ticket
No new surface to learn.
Just a checklist. The runbook renders in the existing checklist card so the check-off, skip, note, and completion tracking behavior is identical to what your techs already use.
Regenerate or save. Regenerate from fresh context when the ticket evolves, or promote a proven runbook into a reusable template for future tickets.
Clear the print queue
from KB · ~2 min
Restart the spooler
from ticket tkt-1204 · ~1 min
Reinstall driver
from playbook · ~8 min
No new surface to learn.
Frequently asked questions
Ready to try Core?
Start a free trial or talk to us about rolling out Core AI Runbook Assistant with your team.