- New ticket webhook
- Claude classifies
- Draft from help docs
Triage support tickets and draft first replies
Every new Zendesk ticket gets a category, priority and sentiment tag plus a draft reply in an internal note before an agent opens it.
A Slack agent answers enrollment and coursework questions from your Notion handbook, cites the page, and tags staff when it is unsure.
Online course and bootcamp teams answer the same questions every cohort: deadlines, refund windows, how to submit assignments, where the recordings live. Staff spend evenings in the community Slack instead of improving the course. Students who post late at night wait until morning for a one-line answer that already exists in the handbook.
Make sure each policy lives on one Notion page with a clear title such as Refund policy, Assignment submission or Office hours. Archive pages from past cohorts; if last cohort’s deadline is still in there, the agent will cite it.
In Relevance AI, add a knowledge source through the Notion integration and select only the handbook and FAQ pages. Set it to re-sync daily so policy edits show up the next morning.
Create an agent with a Claude model selected, the system prompt below, and a knowledge search tool limited to the top 4 results. Require it to include the Notion page link it used in every answer.
Add the Slack trigger for app mentions and new messages in #ask-the-team, replying in thread only. Exclude staff by Slack user ID so the agent never answers instructors.
Give the agent a tool that posts to #staff-escalations and tags the on-duty instructor. It fires when no answer is found, or when a question involves a specific student’s grade, refund or extension, or a complaint.
Every Friday, skim #staff-escalations and turn repeated questions into new handbook pages. Each new page is one less question that needs a human next cohort.
You are the help assistant for {{course_name}}, run by {{school_name}}. You answer students in Slack.
Answer using only the handbook search results. Every answer must end with the link to the Notion page you used.
Rules:
- Keep answers under 80 words. Give the direct answer first, then any steps.
- Quote dates and deadlines exactly as written in the handbook, including the timezone.
- If the handbook does not answer the question, say so and escalate. Never guess a policy.
- Always escalate questions about an individual's grade, refund or extension, or a complaint about staff, even if the handbook covers the general policy.
- Do not give assignment solutions; point students to office hours instead.
When escalating, reply: "Good question. I've passed this to {{staff_role}} and someone will reply in this thread." Then call the escalate tool.Every new Zendesk ticket gets a category, priority and sentiment tag plus a draft reply in an internal note before an agent opens it.
Score every demo request against your ICP, update HubSpot and ping the right rep in Slack within a minute of the form submit.
Copilot and Claude review each PR for bugs, missing tests and risky changes before a human looks, so reviewers can focus on design.