Recipes
Real configs for real support automation
Every recipe here is either a scitor.yaml block straight from the configuration reference, or a GitHub Actions workflow adapted from Scitor's own documented examples. Nothing here is invented — each one links back to its source.
Route tickets to the right team by category or label
Auto-assign billing, bugs, and urgent tickets to different people.
View recipe
Escalate a ticket the moment its SLA is breached
Apply a label and assign on-call the instant a response deadline passes.
View recipe
Flag VIP customers by email domain
Auto-tag contacts from your biggest accounts as VIP.
View recipe
Keep spam and internal tickets out of your CSAT surveys
Stop satisfaction surveys from going out on tickets that were never real support requests.
View recipe
Auto follow up when a customer goes quiet
Nudge a customer who hasn't replied, then close the ticket if they still don't.
View recipe
Stop follow-up emails from opening duplicate tickets
Match a customer's reply to their existing thread instead of starting a new one.
View recipe
Alert Slack when a frustrated customer reports a bug
Combine Scitor's sentiment and category labels to catch the tickets that need eyes now.
View recipe
Post a weekly support digest as a GitHub Issue
A scheduled workflow summarizes the week's tickets by category and sentiment.
View recipe
Auto-assign new tickets by category
Route bug reports, billing questions, and feature requests to different people the moment they're labeled.
View recipe
Auto-close and block high-confidence spam
When Scitor's spam score is high, block the sender and close the ticket — no human needed.
View recipe
Your support repo, running on autopilot
Takes under 5 minutes. Free tier available. No credit card required.