CUSTOMER SUPPORT
Gate Intercom replies on plan tier before promising a feature
Intercepts inbound Intercom support conversations, looks up the requester's plan tier in Stripe.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Intercom conversation openedIntercom
- ActionLook up customer subscription tier in StripeStripe
- LogicMap tier to entitlements and detect gated asks
- ActionCompose tier-aware agent guidanceOpenAI
- OutputPost private entitlement note to IntercomIntercom
What it does
When a support conversation opens in Intercom, this workflow resolves the customer's active subscription tier from Stripe and attaches a private note listing which requested features their plan actually entitles them to. It prevents agents from accidentally promising gated functionality and flags upgrade-required asks before a reply is sent.
When to use it
Run this on every new inbound support conversation in teams where feature access varies by plan (Starter / Pro / Enterprise). Especially useful when frontline agents lack direct billing visibility and over-promise during fast replies.
How it works
- 1A new Intercom conversation triggers the flow with the contact's email.
- 2The customer record is fetched from Stripe to read their active subscription and price tier.
- 3A logic step maps the tier to an entitlement set and detects whether the conversation mentions a gated feature.
- 4If the ask is plan-blocked, the workflow composes an upsell-safe framing; otherwise it confirms the feature is included.
- 5The result is posted back to the Intercom conversation as a private note for the agent.
Set it up
What you configure once, before turning it on.
- 1Connect IntercomConversations, contacts, articles.
- 2Connect StripeCustomers, subscriptions, payments.
- 3Connect OpenAIModels, embeddings, files.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.