CUSTOMER SUPPORT
Downgrade Attio account health on angry Zendesk tickets
On every new Zendesk ticket, an LLM detects high-frustration or cancellation-intent language.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Zendesk ticket createdZendesk
- ActionDetect frustration and cancel intentOpenAI
- LogicGate on high frustration / cancel intent
- ActionFind account in AttioAttio
- OutputDowngrade health and log noteAttio
What it does
This workflow keeps your account health scores honest by reacting to support tone in real time. As Zendesk tickets arrive, it detects strong frustration or explicit cancellation intent, and for those tickets it downgrades the matching account's health field in Attio so CSMs and renewal forecasts immediately see the risk.
When to use it
Use it when health scores are set manually and drift out of date, while the clearest churn signal, an angry support ticket, sits unconnected in Zendesk. Ideal for teams that forecast renewals off Attio health.
How it works
- 1A new Zendesk ticket created event triggers the run.
- 2An LLM classifies the ticket body for frustration level and any cancellation or downgrade intent.
- 3A logic gate continues only when frustration is high or cancellation intent is detected.
- 4The workflow finds the account in Attio via the requester's email domain.
- 5It lowers the account health rating and writes a note recording the ticket, detected signal, and timestamp on the Attio record.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect AttioReal-time CRM with structured data + powerful views.
- 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.