CUSTOMER SUPPORT
Daily Front Sentiment Digest per CSM
Each morning summarizes the prior day's Front conversations by owning CSM, ranks accounts by sentiment trend, and posts each CSM a personalized digest of who needs attention.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekday morning schedule
- ActionPull prior-day Front conversationsFront
- ActionScore and aggregate sentiment per accountOpenAI
- LogicGroup by CSM and rank by risk
- OutputDM each CSM their personalized digestSlack
What it does
Runs on a daily schedule, pulls the previous day's resolved and active Front conversations, scores and aggregates sentiment per account, then sends each CSM a personalized Slack digest ranking their accounts from happiest to most at-risk.
When to use it
Use it when you want proactive, calm triage instead of real-time alarms — a once-a-day read on which relationships are trending the wrong way so CSMs can plan outreach rather than firefight.
How it works
- 1A scheduled trigger runs every weekday morning.
- 2Front returns all conversations touched in the previous 24 hours with their contacts.
- 3OpenAI scores each conversation and rolls scores up into a per-account sentiment trend.
- 4A logic step groups accounts under their owning CSM and sorts each list by risk.
- 5The flow renders a per-CSM digest highlighting the top declining accounts.
- 6Slack delivers each CSM their own digest as a direct message.
Set it up
What you configure once, before turning it on.
- 1Connect FrontShared inbox, conversations.
- 2Connect OpenAIModels, embeddings, files.
- 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.