Recover every unhappy Dixa customer the same day
Every morning, WebRun opens Dixa, finds the conversations that closed with a low satisfaction rating, summarises what went wrong and who handled it, records each in Airtable, and opens a Trello recovery card so the follow-up happens the same day.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I follow up on low customer satisfaction ratings in Dixa?
WebRun reviews your Dixa conversations every morning and picks out the ones that closed with a low satisfaction rating. It summarises each issue, records the score, agent and cause in Airtable, and opens a Trello recovery card due that day, so an unhappy customer is followed up within hours.
- Unhappy customers get a recovery attempt within hours, not weeks
- Every low rating carries a summary and a tagged cause
- Repeat causes by queue become visible after a month of logging
Built for support leads · customer service managers · ecommerce support teams · contact centres
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.dixa.comin a real browser with your saved login - no setup, no API keys. -
1
Dixa - find low rated conversations
dixa.com
WebRun opens Dixa to find low rated conversations. - Open Dixa and filter closed conversations to those rated at or below your threshold
- Read each conversation and summarise the issue in two lines
- Capture the customer, the agent, the queue, the tags, and how long the conversation ran
- Note any written comment the customer left with the rating
Done when Every low rated conversation has a summary, an agent, and a queue.
-
2
Airtable - record rating and cause
airtable.com How to Automate Airtable
WebRun opens Airtable to record rating and cause. - Add a row per low rated conversation with the score, date, agent, and queue
- Paste in the summary and the customer's written comment
- Tag the likely cause: wait time, wrong answer, tone, or an unresolved issue
- Keep running counts by agent and queue so patterns show over the month
Done when Every low rating is recorded with a cause tag in Airtable.
-
3
Trello - open a recovery card
trello.com How to Automate Trello
WebRun opens Trello to open a recovery card. - Create a recovery card per low rated conversation on your support board
- Put the score, the summary, and the agent on the card and set the due date to today
- Attach a suggested recovery action and a drafted apology for the owner to review
- Leave contacting the customer to a person. WebRun never emails or messages a customer
Done when Every low rating has a recovery card due today.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it contact the unhappy customer itself?
No. WebRun writes a suggested recovery action and a drafted apology onto the Trello card. A person reads it, adjusts it, and reaches out. No message goes to a customer automatically.
What counts as a low rating?
Whatever threshold you set, commonly the bottom two scores on your Dixa satisfaction scale. Anything at or below it becomes a recovery card that morning.
Does it put agents on blast?
The agent is named on the card so the right person can help with context, and the Airtable log tracks causes rather than individuals. Coaching stays a private conversation you have.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.