Customer Support · Risk & alerts
Knowledge Base Gap Detection
Starts when: Every Monday, over the previous week of resolved and escalated tickets
Free plan · Outcome verification included · You approve every connection
How it runs
Six stages, from the moment it starts to the checks that keep running afterwards.
It starts
Every Monday, over the previous week of resolved and escalated tickets
Awish plans it and asks for each app
The apps it needs are connected one at a time, with your permission, before anything runs.
It does the work
Exactly as the request below describes, across the connected apps.
It stops where a person should decide
Do not auto-publish generated help content; require content-owner approval.
It verifies the outcome
After each run, Awish checks that the ticket was routed, answered or escalated in time.
It keeps monitoring
Failures, silent failures and connection health are watched on every plan; anomalies, root cause and recommendations on Business.
The request it runs
This is what opens in chat when you use the template. Change any part of it before anything connects.
“I need an automation that detects knowledge base gaps from tickets. Run it every Monday at 9:00 AM using the previous week of resolved and escalated tickets. It should find repeated questions with low deflection or long handling time, map them to existing articles, flag gaps and outdated content, draft an article brief and create the knowledge task. Connect it with Zendesk, Notion, Slack and Jira. Do not auto-publish generated help content; require content-owner approval.”
- Zendesk
- Notion
- Slack
- Jira
Monitoring included
What Awish watches once this template is running.
- Outcome verificationEvery plan
- Silent-failure detectionEvery plan
- Connection healthEvery plan
- Hours saved and ROIEvery plan
- Anomaly detectionOn Business
- Root-cause explanationOn Business
- Recovery recommendationOn Business
More Customer Support templates
Churn Risk Detection and CS Tasks
- HubSpot
- Stripe
- Segment
- Zendesk
Incident Communication to Customers
- PagerDuty
- Statuspage
- Zendesk
- Slack
Onboarding Milestone Monitoring
- HubSpot
- Asana
- Segment
- Gmail
Refund and Return Intake with Approval
- Shopify
- Stripe
- Zendesk
- Slack
Questions about this template
Can I change where it stops for approval?
Yes. Open the template in chat and say where you want it to stop. The plan updates before anything connects.
What if one of these apps is not connected yet?
Awish asks you to connect each app it needs, one at a time, before the workflow runs. You can decline any of them.
How does Awish know this workflow worked?
After each run it checks that the ticket was routed, answered or escalated in time, in the app where that should happen. If a run reports success but the result is missing, it flags a silent failure.
Run it on your own apps
It opens in chat with the request written. See the plan, approve each connection, and Awish verifies the outcome from the first run.
Free plan · No credit card required