Acting on customer satisfaction ratings in Zoho Desk: the short answer

Acting on customer satisfaction ratings in Zoho Desk means every poor score starts a follow-up on its own, without anyone having to spot it first. You switch on happiness ratings. You set a bad rating to reopen the ticket and notify its owner. You add a rule that alerts a team lead. Then you track the reopened tickets in reports.

A happiness rating is the score a customer gives the support they received, either each time an agent responds or when the ticket is closed. Zoho Desk describes the choices as Happy, Neutral and Unhappy, and the customer can add a comment. Each rating is attached to a specific ticket. That link to the ticket is what makes follow-up possible.

Collecting ratings without acting on them gives you a number and little else. The Zoho Desk team describes its customer satisfaction (CSAT) report as "an early indicator of potential churn by highlighting dissatisfied customers and recurring issues". An early warning only helps if someone responds to it.

This guide covers the settings, a worked example, the two reports that show ratings per agent and per topic, and how to measure whether follow-ups worked. If you are still choosing a help desk, the Zoho Desk overview for UK teams explains what the product covers beyond ratings.

Switching on happiness ratings in Zoho Desk: where the setting lives and who can change it

Happiness ratings in Zoho Desk are switched on under Setup, then General, then Customer Happiness. You need a Support Administrator profile to change them. If you cannot see the option, ask whoever owns your Zoho Desk administration before going further.

Zoho Desk ships with three rating types by default. You can rename them to suit your organisation, for example Satisfied, Dissatisfied and Need Help. Each rating can show an emoji, which gives the customer a quick way to answer with one click.

Departments and the sending address

If your Zoho Desk has more than one department, you choose which department the survey is sent from. Pick the department the customer already recognises from the ticket. A survey from an unfamiliar name is easy to ignore.

The sending address matters for the same reason. Zoho Desk lets agents reply from their own email addresses, but Zoho states that almost all businesses prefer responses to come from the common support address. Survey emails should follow the same rule, so customers see one consistent sender from first reply to rating request.

Renaming the ratings is worth a moment's thought. "Need Help" invites the customer to say the problem is not solved, which is exactly the signal you want to catch and act on.

Happiness rating settings checklist: what to choose for reliable follow-up

The happiness rating settings in Zoho Desk decide whether a bad score reaches a person or sits unread. The table below lists each setting, the options Zoho Desk offers and what to choose if follow-up is your goal.

Setting	Options	Choice for follow-up
When ratings are sent	With every reply, or only once the ticket is Closed	Closed, unless you want feedback on each individual response
Who can open the rating link	End user only, anyone with the link, or only the user it was shared with	End user only, so a forwarded email cannot skew the score
Bad rating reopens the ticket	On or off	On
Ratings that notify the ticket owner	All, good, bad, okay, or none	Bad at minimum; all if owners want praise too
Department the survey comes from	Any department you run	The department that handled the ticket
Recent ratings on the Help Centre	Shown in real time, or not shown	Your call; it shows good and bad alike

Timing affects how many customers answer. Zoho Survey advises that CSAT surveys "should be sent immediately after the relevant interaction, within minutes or hours". Sending on closure fits that advice. Some customers still do not reply straight away, and Zoho Desk users have asked in the community whether the survey can be re-sent days or weeks later. Plan your reporting around missing responses rather than assuming everyone rates.

If you publish ratings on your portal, read the guide to planning and launching a Zoho Desk help centre first.

Turning a bad rating into a follow-up: reopen, notify, escalate

A bad rating in Zoho Desk can trigger three separate actions, and you want all three. Each one closes a different gap.

Reopen the ticket. The original ticket goes back into the queue with its full history attached.
Notify the ticket owner. The agent who handled the case learns about the score directly.
Alert a lead with an automation rule. A rule triggered by the happiness rating notifies a manager whenever a bad rating comes in.

Reopening is the follow-up ticket. Creating a fresh ticket would split the conversation in two, and the agent picking it up would lose the context. A reopened ticket keeps the customer's comment, the original thread and the rating together in one record.

The lead alert matters because the owner may be the cause of the complaint, or simply absent. A lead who sees every bad rating can decide who calls the customer back. The lead also sees patterns that a single agent would not, such as several bad ratings on the same product.

At Svennis we set the bad-rating rule up before ratings go live to customers. We then submit a test rating from a dummy contact and check that the ticket reopens and the lead receives the alert, because a rule that silently fails is worse than no rule.

A worked example: from a Dissatisfied rating to a resolved ticket

This worked example follows one bad rating through a Zoho Desk set up with the settings from this guide. The support team has two departments, Customer Service and Technical Support. An administrator with the Support Administrator profile does the setup.

The administrator opens Setup, then General, then Customer Happiness.
The three ratings are renamed Satisfied, Dissatisfied and Need Help.
Ratings are set to send only once the ticket status is Closed.
Link access is limited to the end user.
A bad rating is set to reopen the ticket automatically.
The ticket owner is notified of bad ratings.
An automation rule notifies the Technical Support lead on every bad rating.

A customer's ticket about a failed software update is closed on a Tuesday. The survey arrives from the Technical Support department. The customer clicks Dissatisfied and comments that the update still fails on one machine.

The ticket reopens with the comment visible. The agent who closed it gets a notification, and so does the lead. The lead checks the thread, sees the agent tested on a different machine, and asks the agent to call the customer that afternoon. The agent fixes the remaining machine and closes the ticket again with a note on what changed.

Nobody had to read a report to find this customer. The rating did the finding. The reports come later, to show whether such cases are rare or a pattern.

Reading ratings per agent in the Zoho Desk agent performance report

The agent performance report in Zoho Desk shows how each agent handles tickets, including the ratings their responses received. It tracks response, resolution, SLA and customer happiness metrics side by side. The happiness metrics count the agent responses that received good, ok and bad ratings.

A few details from the Zoho Desk team's description of the report affect how you read it:

The data refreshes every hour, so a rating given a few minutes ago may not show yet.
Only administrators can view the dashboard.
Deleted, merged and spam tickets are included, so counts can differ from a manual tally.
You can filter by high-priority tickets, ticket types or custom periods.

Read happiness alongside resolution and SLA figures, not on its own. An agent with several bad ratings and slow first responses has a different problem from an agent with fast responses and bad ratings. The first may be overloaded. The second may be closing tickets too early.

Use the per-agent view for coaching rather than ranking. Zoho Desk's own team notes that ratings "help support agents by providing feedback that enables them to deliver more effective support". A lead can open a bad-rated ticket with the agent and walk through what the customer expected.

Reading ratings per topic and channel in the Zoho Desk CSAT report

The CSAT report in Zoho Desk turns ratings into positive, negative and neutral counts, trends over time, and performance by agent, department and channel. Because each rating is linked to a ticket, you can also break results down by issue type. That breakdown shows which topics cause unhappy customers.

Two measures in the report are worth knowing by name. The overall satisfaction score is a single health figure for a chosen period. The rating distribution is the split between positive, neutral and negative responses. It shows whether a high score comes from many okay experiences or from truly delighted customers.

Channel and customer views

The channel view compares satisfaction by email, chat, phone and other channels. If phone tickets rate well and email tickets rate badly on the same topic, the problem may be the written answer rather than the fix. Zoho Desk's integrated analytics also lets you monitor ratings across contacts, accounts and time frames, which helps you spot one account that keeps rating badly.

If you want a percentage to compare with others, Zoho Survey gives the usual formula: satisfied responses divided by total responses, times 100. It adds that a CSAT score between 75% and 85% "is generally considered strong across most industries, though benchmarks vary by sector". Treat that range as a rough guide, not a target.

Tracking recovery after a bad rating in Zoho Analytics

Recovery is what happens to a customer after a bad rating: whether the ticket was reopened, who picked it up, and whether it was resolved. Zoho Desk's own reports show the ratings. Recovery tracking asks a second question, which is whether your follow-up worked.

Three measures cover most of it:

Bad ratings received in the period, by agent and by ticket type.
Reopened tickets from bad ratings that have been closed again.
Reopened tickets still open, with their age.

If you want these alongside sales or billing data, Zoho Analytics is the place to combine them. Check one thing before you build. A community user reported that the Happiness Rating did not appear when they exported ticket data for use in Zoho Reports, and asked whether there was another way to export it. Confirm that the rating field actually arrives in your reporting data before you design a dashboard around it.

Keep the first version small. One report of bad-rated tickets and their current status, reviewed weekly by the lead, tells you more than a large dashboard nobody opens. Add trend charts once the weekly review is a habit.

The cost of an unanswered bad rating: why follow-up pays

An unanswered bad rating risks losing a customer who was still willing to stay. Zoho Desk's own writing on customer loyalty puts it plainly: "People who complain are the ones who still believe in your ability to make it right." The same article argues that satisfied customers "complain, but they stay".

The figures quoted by Zoho point the same way. Treat them as cited estimates from other publishers, not as Zoho's own research:

Zoho Desk cites HuffingtonPost: "91% of unhappy customers who are non-complainers simply leave."
Zoho Desk cites Harvard Business Review: acquiring a new customer costs five to 25 times more than retaining one.
Zoho Survey cites Bain & Company: a 5% increase in customer retention can boost profits by as much as 95%.

A bad rating is the moment a customer becomes a complainer instead of a silent leaver. That is the cheapest point to win them back. Zoho Survey describes churn rate as a lagging indicator, which means you only see it after customers have gone. A rating is transactional and immediate. It captures how the customer felt right after the ticket, while there is still time to respond.

This is why reopening on a bad rating matters more than the score itself. The score tells you something went wrong. The follow-up is what changes the outcome.

What acting on ratings means for a UK support team

For a UK support team, acting on Zoho Desk ratings mostly comes down to two practical points: survey emails that arrive, and someone on duty to receive bad-rating alerts. The sources for this guide contain no UK-specific rule on customer ratings, so the advice here is operational.

Making sure survey emails arrive

Gmail and Yahoo began enforcing stronger email authentication from February 2024, as a Zoho Desk notice pointed out. If your customers use those mailboxes, surveys from a poorly configured support domain may never reach them. Send surveys from the common support address, and have whoever manages your domain confirm it meets the newer requirements.

Covering holidays and quiet periods

A bad rating that arrives during a bank holiday or the Christmas shutdown still reopens the ticket. Make sure the automation rule alerts someone who is actually working. Zoho Desk's December 2025 Ask the Experts session covered exactly this, including automations to activate while you are on holiday.

Those community sessions suit UK hours. The December 2025 one ran on Tuesday 16 December from 8:30 am to 2:30 pm GMT. It was a text-based forum discussion with no registration required, so you can read the questions and answers afterwards.

Next steps: checking your Zoho Desk rating setup this week

The quickest way to start acting on customer satisfaction ratings in Zoho Desk is to check the settings you already have. Most of the work is configuration, not new software. Work through this list with whoever holds the Support Administrator profile:

Open Setup, then General, then Customer Happiness, and confirm ratings are switched on.
Rename the three ratings if the defaults do not invite honest answers.
Set bad ratings to reopen the ticket and notify the owner.
Add an automation rule that alerts a team lead on every bad rating.
Submit a test rating from a dummy contact and check both alerts arrive.
Book a weekly review of bad-rated tickets with the agent performance and CSAT reports.

Once the follow-up loop runs for a few weeks, decide whether you need ratings combined with other data in Zoho Analytics. Until then, the built-in reports are enough to find patterns.

If your Zoho Desk setup needs more than a settings change, start with the Zoho Desk page for UK teams to see what a full configuration covers. If you are weighing outside help, what a Zoho partner does explains how that kind of engagement usually works.

Sources

Looking for a Zoho partner in the UK? Svennis has been a Zoho Premium Partner since 2011, with more than 200 implementations delivered. See how we work as a UK Zoho Partner.

Acting on customer satisfaction ratings in Zoho Desk so no bad score goes unanswered