CUSTOMER SUPPORT
Triage feature requests by tier and log expansion-blocked asks
Reviews inbound Intercom feature requests, checks the requester's Stripe tier, and logs plan-blocked requests to a Postgres table while routing genuine product gaps to Linear.
How it runs
The automated pipeline, trigger to output.
- TriggerIntercom feature-request conversation taggedIntercom
- ActionResolve requester plan tier in StripeStripe
- LogicDecide tier-gated vs true product gap
- ActionLog expansion-blocked ask to PostgresPostgres
- OutputFile genuine gaps as Linear issuesLinear
What it does
This agent-driven workflow reads feature requests arriving in Intercom and decides whether the ask is already available on a higher tier (an expansion opportunity) or a true product gap (a roadmap input). Tier-blocked requests are logged to a Postgres demand table for the revenue team; real gaps are filed in Linear for product.
When to use it
Use it when feature requests are a mixed signal and you want to stop treating every "can it do X" as roadmap fuel. It cleanly splits requests that an upgrade would satisfy from requests that need engineering work.
How it works
- 1A new Intercom conversation tagged as a feature request triggers the flow.
- 2Stripe resolves the requester's current plan tier.
- 3An agent step decides whether the requested capability exists on any tier the customer is not on.
- 4If it is tier-gated, the request is appended to the expansion-demand table in Postgres.
- 5If it is a genuine gap, a roadmap issue is created in Linear with the customer context attached.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect StripeCustomers, subscriptions, payments.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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.