Start every workday with a support health digest in Slack
Every weekday morning, your team gets a plain-language summary of yesterday's support performance and today's priorities, posted straight to Slack.
Dixa
Slack BotCustomer SupportOperationsDaily DigestsAI ReportsEvery weekday at 8am, post a support health digest to our team's Slack channel so everyone starts the day knowing where things stand. Run Monday through Friday only, and use yesterday as the reporting window.
First, pull yesterday's key numbers from Dixa. Use the Metrics Catalogue operation to confirm the available metric IDs, then use Get Metric Records Data to fetch yesterday's figures for conversation volume, customer satisfaction (CSAT), response time, and resolution time. Where possible, also fetch the same metrics for a recent baseline (for example the trailing few weeks of the same weekday) so you have something to compare against.
Next, check the current backlog. Use List queues to enumerate our queues, then use Get queue availability for each queue to see how loaded things are right now. Note any queue that looks unusually backed up.
Then surface conversations that need attention today. Use Search conversations with filters to find still-open or aging conversations, for example ones that have been open longer than usual or are still waiting on a first reply. Pull out the handful that most need eyes today rather than listing everything.
Now write the digest. Keep it short and in plain language. Lead with a one-line read on how yesterday went, then call out what changed versus a typical day (volume up or down, a CSAT dip, slower responses, a queue that is backing up) and what the team should prioritize today. Do not dump raw numbers or restate every metric; only cite a figure when it makes a point. Aim for something a manager can skim in under a minute.
Finally, send the digest to our team channel using Slack's Send a Message operation. Format it for Slack with a clear headline and a few short sections or bullets so it reads well in the channel.
Keep the send time, the Slack channel, and which metrics appear easy to adjust so we can tune them over time.
Additional information
What does this prompt do?
- Pulls yesterday's key support numbers from Dixa: conversation volume, customer satisfaction, and how fast your team responded and resolved.
- Checks your live queue backlog and surfaces still-open or aging conversations that need attention today.
- Writes a short, plain-language digest that calls out what changed versus a normal day and what to prioritize, instead of dumping raw numbers.
- Posts it to your team's Slack channel every weekday morning, so everyone starts the day on the same page.
What do I need to use this?
- A Dixa account (a Dixa administrator connects it for you).
- A Slack workspace with a channel where the digest should be posted.
- A rough sense of what a normal support day looks like, so the digest can flag anything unusual.
How can I customize it?
- Change the send time or the days it runs, for example 8am on weekdays only.
- Point it at a different Slack channel, like a leadership channel or a per-team channel.
- Choose which metrics appear, such as adding first response time or dropping CSAT.
Frequently asked questions
When does the digest arrive?
Will it just dump a wall of numbers?
Which support metrics does it include?
Where does the digest get posted?
Do I need to be technical to set this up?
Related templates
Start every morning knowing where support stands.
Set up your daily support health digest and give the team a clear, prioritized read on the day before the first ticket lands.