CUSTOMER SUPPORT
Turn Recurring Front Email Questions Into Linear Doc Issues
Tags closed Front conversations by topic, and when a topic recurs without a matching Notion doc, opens a Linear issue on the docs team to write or update the article.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionPull recently closed Front conversationsFront
- LogicLabel topic and summarize with LLMOpenAI
- LogicKeep topics recurring 4+ times in 30 days
- ActionSearch Notion for an existing docNotion
- OutputOpen Linear doc issue for each gapLinear
What it does
Treats your shared inbox as a signal source. It groups closed email threads by topic, spots topics that keep coming back with no Notion documentation, and routes the work to your Linear docs backlog.
When to use it
Good for teams handling support over email through Front, writing docs in Notion, and tracking engineering or docs work in Linear. Use it to stop the same email question from being re-answered by hand every week.
How it works
- 1A daily schedule starts the run.
- 2Pull Front conversations closed in the last day with their message bodies.
- 3Use an LLM to assign each thread a topic label and a one-line question summary.
- 4Maintain a rolling 30-day count per topic; keep topics seen 4+ times.
- 5For each frequent topic, search Notion for an existing doc.
- 6Filter to topics with no Notion coverage.
- 7Open a Linear issue per gap with the topic, recurrence count, and linked example threads, assigned to the docs team.
Set it up
What you configure once, before turning it on.
- 1Connect FrontShared inbox, conversations.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect NotionPages, databases, comments.
- 4Connect LinearIssues, projects, cycles, triage.
- 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
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.
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.
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.
Article Volume-Rebound Early Warning (Datadog)
Streams support ticket-tag events into Datadog, watches for topics whose volume is reaccelerating against a decaying article.
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.