Measuring Customer Happiness in Instant Messaging: CSAT with Zoho Desk

Measuring Customer Happiness in Instant Messaging

Getting genuine, useful feedback after a chat support interaction shouldn't feel forced for you or your customers. With Zoho Desk, you can gather honest feedback without interrupting the conversation flow.
This guide covers how Customer Satisfaction (CSAT) ratings work in instant messaging (IM) channels, when and how feedback is collected, how ratings are processed, timeout rules, what happens when feedback arrives late, and how agent notifications are handled.

What is Customer Happiness in IM?

Customer happiness shows how satisfied someone feels during and after their support interaction. In Zoho Desk's IM channels, it's measured through a simple CSAT survey at the end of the conversation.
When the ticket closes, customers are asked: "How was your support experience?" They can choose:
  • Good (Satisfied)
  • Okay (Neutral)
  • Bad (Dissatisfied)
These quick responses help assess agent responsiveness, clarity of communication, and how effectively the issue was resolved.

Why are Customer Happiness ratings important?

CSAT ratings give you insight into how customers really feel about their IM support experience. Here's why they matter:
  • Feedback is only collected once a conversation ends; either manually by an agent or automatically due to inactivity.
  • Customers can respond with just a tap; simple and friction-free.
  • There's no extra burden on agents; feedback is automated by Zoho Desk.
  • All responses are stored in reports, helping you track trends, monitor team performance, and improve service quality.
  • CSAT data can spotlight recurring pain points, helping you tweak your support approach over time.

How it works

Feedback is always requested after the conversation has truly ended. That means no mid-chat interruptions. Feedback is triggered in one of two ways:
  • When an agent manually closes the ticket after resolving the issue.
  • When the conversation times out due to customer inactivity.
At that point, the system sends a respectful, timely feedback request, asking customers to rate their experience.

How ratings are processed

Once the customer responds, their rating is automatically recorded in Zoho Desk's analytics tools. These insights can help you:
  • Evaluate both team-wide and individual agent performance.
  • Identify and address frequent service issues.
  • Make smart decisions to improve customer experience and retention.
Every response helps shape a better support journey moving forward.

How to set up Customer Happiness ratings

To enable and customize CSAT in Zoho Desk, follow these steps:
Setup
1. Go to Setup.
2. Click on the Setup icon in the top navigation bar.
3. Navigate to Customer Happiness.
4. Under the General section, select Customer Happiness.
5. Click Get Started. This enables the feature for all departments by default.
6. Configure Rating Settings:
  • Rating Question: Enter a question for customers, such as "How satisfied are you with the support you received?" or "Was your issue resolved to your satisfaction?"
  • Rating Options: Customers can choose from three responses: Good (Satisfied), Okay (Neutral, which can be disabled if not required), and Bad (Dissatisfied).
7. Save the configuration. Apply the settings to activate CSAT for your selected departments.
Limitation
Reopen Ticket setting is currently not applied to IM tickets.
In IM, when a customer submits a Happiness Rating for a closed conversation, the ticket may reopen and move to the Unassigned state.
Zoho Desk has a Reopen Ticket setting for Happiness Ratings, with options such as Don't reopen, For all ratings, and For bad ratings. While these options work for regular Zoho Desk tickets, they are not currently applied to IM tickets.
As a result, a closed IM ticket is reopened when a rating is submitted, even if Don't reopen is selected in the Customer Happiness settings.

Timeout mechanism and feedback triggers

CSAT is only triggered when the chat session ends. Zoho Desk uses two main triggers:
  • Auto-close after inactivity.
  • Manual close by an agent.
This ensures feedback is only requested when the conversation is clearly over.

Feedback after timeout

  • If a customer responds after the ticket is closed, Zoho Desk creates a new ticket.
  • All agents are notified so the conversation can be picked up again.

Only specific replies count as feedback

Feedback is logged when the customer taps a button (Good, Okay, Bad), or types the word "Good", "Okay", or "Bad" (case-insensitive). If a customer responds with anything other than the specific feedback options, their message is treated as a new inquiry. For example, if they reply with "Thank you" or ask a follow-up question, the system logs it as a new ticket rather than feedback.

Agent notifications

  • New ticket notification: Agents are notified whenever a new ticket is created, allowing them to take timely action.
  • Feedback-only submission: No notifications are sent for feedback-only submissions, helping reduce unnecessary alerts for agents.

Trigger scenarios

Scenario Trigger Type Feedback Sent?
Conversation inactive beyond timeout Auto-close Yes
Agent closes the conversation manually Manual trigger Yes
Customer does not respond before timeout Auto-close Yes
Customer ends conversation voluntarily Auto-close Yes
Agent keeps conversation open No trigger No

Handling late feedback and new ticket creation

Sometimes, feedback arrives after the timeout. Here's how that works:
When a customer responds within the feedback window, the rating is logged under the original ticket and no new ticket is created. When a customer responds after the window has closed, the response is treated as late feedback: the system creates a new ticket and notifies agents so the conversation can be picked up again. The same applies when a customer types any message other than a valid rating — it is treated as a new inquiry rather than feedback.

IM channel limitations for feedback

Each IM channel has its own limits for the number of rating buttons, the text length per button, and the maximum question length.
Channel Buttons Text per Button Max Question Length
WhatsApp 3 20 characters 1024 characters
Telegram 3 40 characters 1024 characters
Facebook Messenger 3 20 characters 640 characters
Instagram 3 20 characters 640 characters
LINE 3 13 characters 60 characters

Multilingual support for feedback collection

  • Feedback surveys are sent in the customer's preferred language.
  • You can customize messages for each supported language.
  • Multilingual support allows for more accurate and respectful regional analysis.

Step-by-step breakdown of ticket handling and feedback processing

Let's walk through it with a WhatsApp chat example.

1. Conversation begins

Time What Happens
12:00 PM Customer messages you: "Can't log in".
12:01 PM Zoho Desk creates a ticket (#1001) and assigns it to an agent.
12:05 PM Agent responds, "Please let me know if this resolves your issue."
Ticket status: Open (customer goes quiet).

2. Auto-close and feedback request

Time What Happens
1:05 PM Auto-close kicks in after 60 minutes (ticket and conversation closed).
1:06 PM System sends: "How was your support?" with rating buttons.
1:30 PM Customer taps one of the options (Good, Okay, Bad) and the feedback is logged. Done.
Ticket status: Closed.

3. Customer responds before auto-close (within the 30-minute window)

Time What Happens
1:30 PM Customer taps one of the options (Good, Okay, Bad). Feedback is logged under the same ticket (#1001). No new ticket is created, and no agent notification is sent.

4. Customer responds after the timeout (beyond 30-minute window)

Time What Happens
2:30 PM Customer taps one of the options (Good, Okay, Bad). The response is considered late feedback. The system creates a new ticket (#1002), and agents are notified of the new ticket.

5. Customer types any other response (before or after timeout)

Time What Happens
1:15 PM or 2:30 PM Customer types a message like "Great service!" or "Thank you!" instead of pressing a button or typing an exact match. The system does not recognize it as valid CSAT input. A new ticket (#1002) is created, and agents are notified of a new conversation.

Frequently Asked Questions

Q: Can customers change their feedback after submission?
A: No, feedback cannot be altered once submitted.
Q: Can businesses customize the feedback question?
A: Yes, Zoho Desk allows businesses to modify the rating prompt.
Q: Will customers receive multiple feedback requests for the same issue?
A: No, only one request per session is sent.

Troubleshooting Guide

Feedback request not sent to customers

  1. Ensure the conversation is closed either manually or via an auto-close timer. Open conversations do not trigger feedback requests.
  2. Verify that CSAT is enabled under Setup > Customer Happiness.
  3. Confirm that the IM channel supports feedback collection.

Duplicate feedback requests sent to customers

Short auto-close timers may prematurely close the conversation, triggering unnecessary feedback requests. Adjust the timer as needed.

Customer's response not recognized as feedback

Only button selections or exact matches are considered feedback; different typed responses are ignored and start a new conversation.

Feedback sent in wrong language

  1. Ensure multilingual support is enabled and feedback messages are translated under Customer Happiness settings.
  2. If no matching translation exists, the system defaults to the primary language.

Best practices

Optimize feedback timing

  1. Set an appropriate auto-close timer to avoid closing the conversation too soon or leaving it open for too long.
  2. Use a delayed feedback request to allow customers time to reflect before submitting a rating.

Prevent duplicate feedback requests

Adjust ticket closure settings to give customers enough time to respond before auto-closing.

Ensure accurate feedback collection

  1. Train customers to use rating buttons ("Good," "Okay," "Bad") instead of typing responses.
  2. Enable multilingual feedback messages so customers receive rating requests in their preferred language.