Get Slack alerts for low Dixa customer satisfaction scores

Every 30 minutes we scan Dixa for conversations that just got a low satisfaction rating and post a ready-to-act summary to your support leads in Slack.

Agentic Task
DixaSlack BotCustomer SupportNotifications & AlertsFeedback Triage
PromptCreate

Every 30 minutes, check Dixa for conversations that just received a low customer satisfaction rating and alert our support leads in Slack with enough context to act. Run this on a cron schedule that fires every 30 minutes.

Two settings should be easy to change at the top of the workflow: the score threshold (default: flag any rating that is at or below 2 out of 5) and the Slack channel where support leads receive alerts (a support-leads channel).

First, use Dixa's Search conversations with filters to pull conversations that were recently closed or rated, looking back over roughly the last hour so nothing is missed between runs. This is the set of conversations to inspect.

For each conversation, use Dixa's List ratings for a conversation to read its satisfaction scores. Ratings are reported per survey question, so treat the conversation as low-rated if any question scored at or below the threshold. Skip conversations that have no rating yet or where all scores are above the threshold.

For each low-rated conversation, use Dixa's List messages to read what actually happened in the conversation before writing anything.

Then summarize, in a few short lines: the issue, the likely reason the customer was unhappy, and one suggested recovery step. Post that summary to the support-leads Slack channel using the Slack Bot integration's Send a Message, and include a direct link to open the conversation in Dixa (built from its conversation id) so a lead can jump straight in. Include the low score and the conversation id in the message as well.

Do not ping leads twice about the same conversation. Keep a record of the conversation ids you have already alerted on, and skip any conversation that is already in that record before posting. Add each conversation id to the record once its alert has been sent.

Example output

Low CSAT alert - Dixa conversation #48213 Rating: 1 / 5 Issue: Customer waited three days for a refund on a duplicate charge and was passed between two agents without a resolution. Likely reason: Slow response times and repeated handoffs made the customer feel ignored. Suggested recovery: Have a senior agent personally reach out, confirm the refund is processed today, and offer a goodwill credit. Open in Dixa: https://app.dixa.io/conversations/48213

Additional information

What does this prompt do?
  • Checks Dixa every half hour for conversations that were just rated at or below your chosen satisfaction score.
  • Reads the actual conversation to understand what went wrong, why the customer was unhappy, and how to make it right.
  • Posts a clear summary to your support-leads Slack channel with a direct link to the conversation.
  • Remembers what it already flagged so your leads never get pinged twice about the same conversation.
What do I need to use this?
  • A Dixa account with permission to view conversations and their satisfaction ratings.
  • A Slack workspace and the channel where your support leads should receive alerts.
How can I customize it?
  • Change the satisfaction score that counts as low (the default flags anything at or below 2 out of 5).
  • Point the alerts at a different Slack channel.
  • Adjust how often the check runs or how far back it looks for new ratings.

Frequently asked questions

How quickly will my team hear about an unhappy customer?
The check runs every 30 minutes, so a low rating usually reaches your Slack channel within half an hour of the customer submitting it.
What counts as a low score?
You set the threshold. By default, any rating at or below 2 out of 5 triggers an alert, and you can raise or lower that at any time.
Will the same conversation alert my team more than once?
No. It keeps track of conversations it has already flagged, so your leads only get pinged once per unhappy customer.
What is included in each Slack alert?
A short summary of the issue, the likely reason the customer was unhappy, a suggested recovery step, and a direct link to open the conversation in Dixa.
Do I need to be a Dixa administrator?
You need an account that can read conversations and ratings. Creating the initial connection usually requires an administrator, but you can hand the workflow off to your team afterward.

Never let an unhappy customer slip by unnoticed.

Turn Dixa satisfaction scores into instant Slack alerts your support leads can act on.