CUSTOMER SUPPORT
Detect VIP accounts and fast-track their tickets
On each new Zendesk ticket, looks up the requester in Salesforce to check account tier, and for high-value accounts bumps priority, applies a VIP tag.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Zendesk ticket createdZendesk
- ActionLook up requester account in SalesforceSalesforce
- LogicAccount meets VIP threshold?
- ActionRaise priority + apply VIP tag in ZendeskZendesk
- OutputNotify priority-support Slack channelSlack
What it does
This enriches every inbound Zendesk ticket with account context from Salesforce. It matches the requester's email to a CRM account, reads the plan tier and ARR, and when the account qualifies as VIP it raises the ticket priority, applies a VIP tag, and notifies a priority-support Slack channel so a senior agent claims it quickly.
When to use it
Use this when your highest-value customers need faster response times than the default queue provides. It enforces SLA tiering automatically instead of relying on agents to recognize key accounts by name.
How it works
- 1A new Zendesk ticket triggers the flow.
- 2The requester email is looked up in Salesforce to fetch account tier and ARR.
- 3A branch evaluates whether the account meets the VIP threshold.
- 4For VIP accounts, the ticket priority is raised and a VIP tag is applied in Zendesk.
- 5A notification with the account name and ticket link is posted to the priority Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect SalesforceAccounts, opportunities, cases.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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.