Follow up on every unhappy satisfaction rating
Every morning, WebRun opens Kayako, finds the satisfaction ratings left below your threshold overnight, reads the conversation behind each one, opens a Trello card for the support manager with the customer and the story attached, and logs every rating in Airtable so the pattern by agent is visible over time.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I follow up on low customer satisfaction ratings?
WebRun opens Kayako every morning, finds the satisfaction ratings left below your threshold, and reads the conversation behind each one. It opens a Trello card for the support manager with the customer, agent and story attached, and logs every rating in Airtable, so an unhappy customer gets a human follow-up.
- Every unhappy rating from overnight has an owned card by 8:00 AM
- Low ratings on still-open conversations are handled first
- The pattern by agent and by issue builds up instead of resetting each week
Built for support managers · customer service teams · helpdesk leads · SaaS companies
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
kayako.comin a real browser with your saved login - no setup, no API keys. -
1
Kayako - find low satisfaction ratings
WebRun opens Kayako to find low satisfaction ratings. - Open Kayako and filter satisfaction ratings to those left since the last run
- Keep only the ratings below the threshold you set
- Read the conversation behind each low rating and capture what actually went wrong
- Note the agent who handled it, the customer, and the current ticket status
- Flag any low rating on a conversation that is still open, since those need a reply before a follow-up
Done when Every low rating has its conversation, agent, customer and status captured.
-
2
Trello - open a follow-up card
WebRun opens Trello to open a follow-up card. - Open a card on the support manager's board for each low rating
- Title it with the customer name and the rating given
- Put the summary of what went wrong, the agent, the ticket link and the current status in the description
- Put cards for still-open conversations at the top of the list
- Leave the customer follow-up itself to the manager. WebRun does not contact the customer
Done when Every low rating from overnight has its own Trello card with the context attached.
-
3
Airtable - log the pattern by agent
WebRun opens Airtable to log the pattern by agent. - Add a row per low rating with the date, agent, customer, score and the reason in one line
- Keep every previous rating in place so a pattern by agent or by issue builds up
- Show a running count per agent for the current month
- Mark rows where the follow-up card has since been closed
Done when The Airtable log holds today's low ratings alongside the running history.
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 reply to the unhappy customer?
No. WebRun never replies in a conversation and never emails a customer. It opens an internal Trello card with the full story so the support manager can make a human follow-up themselves.
Does it change the ticket in Kayako?
No. It reads ratings, conversations and status only. It never reassigns a ticket, never changes a status and never adds a note, so the agent's record stays exactly as it was.
What counts as a low rating?
Any score below the threshold you set once. WebRun checks every rating left since the last run against it and only creates cards for the ones that fall short.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.