CUSTOMER SUPPORT
Flag missing Loom walkthroughs from last week's repeat tickets
Runs weekly, clusters the past week's Zendesk how-to tickets by topic, checks which topics lack a Loom walkthrough.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionFetch past week's resolved how-to ticketsZendesk
- ActionCluster tickets into topics with volumeOpenAI
- ActionList existing Loom walkthroughsLoom
- LogicKeep uncovered topics above volume threshold
- OutputPost recording backlog to SlackSlack
What it does
This is the content-gap side of the walkthrough program. Each week it pulls resolved how-to tickets from Zendesk, clusters them by topic, and cross-references your existing Loom library. Topics with high ticket volume but no walkthrough video are ranked and delivered as a recording backlog, so you film the videos that will deflect the most tickets.
When to use it
Use it once your Loom-attach workflow is live and you want to grow coverage deliberately instead of guessing. It turns repeat tickets into a data-driven recording queue for your support content owner.
How it works
- 1A weekly schedule triggers the run.
- 2The workflow fetches the past week's resolved how-to tickets from Zendesk.
- 3OpenAI clusters them into recurring topics and counts volume per topic.
- 4It lists your existing Loom walkthroughs and marks which clustered topics already have coverage.
- 5A filter keeps only uncovered topics above a volume threshold.
- 6The ranked gap list is posted to a Slack channel for the content owner to action.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LoomVideo transcripts, libraries.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Customer Support workflows
Send a tailored Loom onboarding sequence on Front first-reply
When a new customer's first email lands in Front, this picks the Loom onboarding walkthroughs matching their plan and use case, builds a friendly sequenced reply.
Suggest the right Loom video by classifying Intercom message intent
Reads each new inbound Intercom conversation, classifies what the customer is trying to do, and surfaces the best-matching Loom walkthrough to the agent as an internal note.
Draft personalized fix-live replies for support to review
When a Sentry issue resolves, an agent reads each linked ticket's full thread and drafts a tailored 'your fix is live' reply per requester.
Close the loop with requesters when a Linear bug moves to Done
When a Linear issue created from a support escalation moves to Done after deploy, look up the originating Zendesk tickets and notify each requester that their reported bug is…
Reopen and notify Front conversations when their bug fix deploys
When a deploy resolves a Sentry issue, find the snoozed or closed Front conversations linked to it, reopen them, and send the customer a reply that the fix is now live.
Tell Intercom users their reported bug shipped after a Vercel deploy
On a successful Vercel production deployment, match the release's resolved Sentry issues to Intercom conversations and message each affected user that their reported issue is…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.