CUSTOMER SUPPORT
Turn recurring Intercom how-to questions into a reusable Loom FAQ library
Runs on a schedule to find Intercom how-to questions asked repeatedly in the last week, records one canonical Loom for each recurring topic.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionExport last 7 days of how-to conversationsIntercom
- ActionCluster into recurring topicsOpenAI
- LogicSkip topics already in the library
- ActionRecord canonical Loom per new topicLoom
- OutputFile videos in Notion FAQ libraryNotion
What it does
Mines your Intercom history for the same how-to questions asked over and over, then builds a durable video FAQ. On a weekly schedule it clusters recent conversations by topic, identifies the highest-volume how-to themes, records one canonical Loom per theme, and files each video in a Notion library agents can drop into future replies.
When to use it
Use it when the same handful of how-to questions consume agent time every week and you want a self-service video knowledge base built from real customer language instead of guesswork.
How it works
- 1A weekly schedule triggers the flow.
- 2The flow exports the past seven days of how-to-tagged Intercom conversations.
- 3An LLM step clusters them into recurring topics and picks the top themes by volume.
- 4A logic step filters out topics that already have a Loom on file.
- 5A Loom action records one canonical walkthrough per new topic.
- 6The final step writes each video, topic, and summary as a row in the Notion FAQ library.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect LoomVideo transcripts, libraries.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect NotionPages, databases, comments.
- 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.