CUSTOMER SUPPORT
Daily Escalated-Ticket Sentiment Digest to Teams
Each morning, pulls yesterday's escalated Zendesk tickets, scores their sentiment and urgency with an LLM, and posts a ranked exec summary to your Microsoft Teams standup channel.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekday 7:30am schedule
- ActionFetch tickets escalated in last 24hZendesk
- ActionScore sentiment, churn risk, summaryOpenAI
- LogicRank by negativity + urgency, drop neutral
- OutputPost exec digest card to standup channelMicrosoft Teams
What it does
Generates a single, skimmable executive summary of every ticket that was escalated in the last 24 hours, ranked by how angry and how urgent each customer is, and drops it into the channel your team reads before standup.
When to use it
Run it when support leads start standup blind to overnight escalations, or when leadership keeps asking "what are the fires today?" and nobody has a crisp answer. Best for teams on Zendesk who hold a daily standup in Microsoft Teams.
How it works
- 1A schedule fires every weekday at 7:30am before standup.
- 2The flow queries Zendesk for tickets escalated or with priority raised in the last 24 hours, pulling subject, requester, and full comment thread.
- 3An OpenAI step scores each ticket for sentiment (1-5), churn risk, and a one-line plain-English summary.
- 4A logic step sorts tickets so the most negative and most urgent rise to the top, dropping neutral noise.
- 5The summary is formatted into a Teams card with counts, top-5 hotlist, and direct ticket links, then posted to the standup channel.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect Microsoft TeamsChannels, chats, 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.