CUSTOMER SUPPORT
Route upsell-blocked feature requests to the sales Slack channel
Detects when a Zendesk ticket asks for a feature the customer's tier does not include, confirms the gap against Stripe.
How it runs
The automated pipeline, trigger to output.
- TriggerZendesk ticket created or updatedZendesk
- LogicClassify request as gated feature or limit overageOpenAI
- ActionConfirm current tier and MRR in StripeStripe
- LogicKeep only upgrade-unblockable requests
- OutputPost qualified upsell card to sales SlackSlack
What it does
This workflow scans incoming Zendesk tickets for requests that hit a plan limit or a tier-gated feature. When it confirms the customer is on a lower tier than the request requires, it packages the context into a qualified upsell signal and posts it to a sales Slack channel so revenue can follow up while intent is hot.
When to use it
Use it when support tickets are a hidden pipeline of expansion revenue and you want plan-blocked asks captured and handed to sales automatically rather than answered with a flat "not available on your plan."
How it works
- 1A new or updated Zendesk ticket triggers the flow.
- 2A logic step classifies whether the ticket requests a gated feature or exceeds a plan limit.
- 3Stripe confirms the customer's current tier and monthly value.
- 4A branch filters to only tickets where an upgrade would unblock the ask.
- 5The workflow posts a structured upsell card (account, current tier, requested feature, MRR) to the sales Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect StripeCustomers, subscriptions, payments.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect OpenAIModels, embeddings, files.
- 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.