↑↓ selectEnter openEsc close

    1. Elbuz

    How to collect customer ratings (CSAT) after a reply

    3 min readUpdated

    After “Solved”, Elbuz asks the customer to rate the reply “Good” or “Bad” through the same channel and instantly notifies the assignee and their manager about a bad rating.

    When you need this:

    • You don't know which agents reply poorly — the report shows the share of “Good” for each assignee.
    • An unhappy customer leaves without a word — “Bad” arrives as a notification with a button that opens the ticket.
    • You need to know what exactly went wrong — the customer's feedback goes into the ticket feed.

    Where to start: decide whether to turn it on, then select the checkbox on the “General” tab of the support desk settings.

    What customer rating does

    When to turn on rating

    Rating is off by default: the request goes to the customer on your behalf, and the owner makes that decision.

    Turn it on when agents handle tickets one by one, your customers are retail buyers who reply in chat or by email, and you want to know who replies poorly. The “Bad” signal arrives right away, so you can call an unhappy customer the same day.

    Think first if:

    • you are cleaning up old tickets in bulk. A request goes out for every ticket an employee sets to “Solved”, including by a bulk action. Two hundred solved at once means two hundred emails to customers. Before a cleanup, turn rating off or close old tickets with the “Closed” status — no request goes out for it;
    • the ticket isn't a conversation with a customer: internal questions, correspondence with a supplier. Whoever wrote will get the rating request;
    • most tickets are calls from customers with no email in their card. For a call, the request goes out only by email, and without an address it won't be sent.

    How to turn it on and change the request text

    On the “General” tab, select the “After “Solved” ask the customer to rate the reply (same channel; calls — by email if known)” checkbox and click “Save”.

    Default text: “{CUSTOMER_NAME}, we have resolved your request #{TICKET_ID}. Please rate how we did — it takes one click.” Enter your own text in the field under the checkbox, up to 1000 characters:

    • {CUSTOMER_NAME} — the first word of the customer's name from the ticket or the contact card;
    • {TICKET_ID} — the ticket number;
    • the “Good / Bad” buttons are added automatically, you don't need to type them.

    With no name, {CUSTOMER_NAME} and the comma are dropped and the first letter is capitalized: “We have resolved your request #128…”. The default text, buttons and rating page use the customer's language detected by AI analysis (Ukrainian, Russian or English), or else the storefront's main language. Your own text isn't translated: if customers write in several languages, leave it empty.

    Support desk settings, General tab: the Customer rating (CSAT) block with the checkbox and the request text field
    1Rating checkbox
    2Request text field
    1. A rating request is sent after every “Solved” set by an employee.
    2. Empty means the default text in the customer's language; the “Good / Bad” buttons are added automatically.

    What the customer gets

    When. Right after an employee sets “Solved”: with the status chip, a bulk action, or a reply with the “Solved” status — then the request follows the reply. The request goes out once per ticket.

    SituationRequest
    A process set “Solved”not sent: a process changes the ticket as “System”, not as an employee
    The ticket closed automatically 4 days after “Solved”, or it was set straight to “Closed”not sent
    The ticket has already been rated or the request was already sentnot sent again
    Sending failed: there is neither a chat nor an emailnot marked as sent; the system tries again at the next “Solved”

    Which channel.

    • a ticket from a chat or messenger — a message in the same chat on behalf of the employee who set “Solved”: the text and two lines with “👍 Good” and “👎 Bad” links;
    • a ticket from email — an email with the subject “Rate our reply · request #N: subject” and two buttons;
    • a call — an email, if the address is known from the contact card or the ticket; if sending to the chat fails, also an email.

    Rating page. The link leads to a page of your Elbuz account (on your domain, if one is connected), with no sign-in. Opening the link already records the rating.

    The customer sees “Thank you! Glad we could help” or “Thank you for being honest. We are sorry it went this way”, a feedback field and a “Changed your mind? Rate “Bad”” (or “Good”) link. The link never expires, and the page is hidden from search engines.

    Public customer rating page after a bad rating: sad face, thank-you heading, feedback field with a submit button and a link to change the rating
    1Feedback field
    2Changed your mind link
    1. The feedback goes into the ticket's activity feed.
    2. The rating can be changed - the report counts the latest one.

    Who learns about a “Bad” rating

    Once the customer rates “Bad” or switches from “Good” to “Bad”, the assignee and their manager get “Ticket #N: the customer rated the reply “Bad””. The manager is found as for a breached : by the org structure, then the sales manager, then “Management” (who the manager is). Later feedback sends no separate notification — it's in the feed.

    If AI acted in the ticket, its decisions on this ticket go to the autonomous support review queue (AI quality control). The rating doesn't change the ticket status. To have “Bad” put the ticket back to work, add a process — see the example “‘Bad’ rating — back to work”.

    Where to see ratings

    • In the ticket — a “👍 Good” or “👎 Bad” badge in the header (feedback in its tooltip), and in the feed the events “The customer rated the reply: “Bad”” and “Customer feedback: …”.
    • The “Customer rating (CSAT)” tile in the “Reports” view — the percentage of “Good” among all ratings, with “👍 N · 👎 M · asked K” below. It counts tickets where a rating was requested or the customer rated during the period. The difference between “asked” and the total ratings is those who didn't respond.
    • The column in “By assignee” — the share of “Good” across the assignee's tickets, with good and bad in brackets, for example “86% (12 / 2)”. It counts tickets created in the period, so the total may not match the tile.

    Look at the brackets, not just the percentage: 50% of (1 / 1) is two customers, not a trend. Slow replies and bad ratings point to workload (limit). Fast replies but bad ratings point to content: read the feedback and give the agent macros for common questions. How to read the rest of the report — support desk reports.

    Scenarios

    A retail store wants to know who replies poorly

    What to do. Turn rating on and keep the default text. What you get. A month later, “By assignee” shows each agent's share of “Good”, and the manager learns about every “Bad” the same day.

    Before cleaning up old tickets in bulk

    What to do. Turn rating off or close old tickets with the “Closed” status. What you get. Customers won't get dozens of “Rate our reply” emails about month-old tickets.

    A bad rating should put the ticket back to work

    What to do. A process on the csat event with the value bad: status “Open”, a tag, a note “call back”. What you get. The ticket is back in the assignee's queue, not just a notification.

    What to do when the rating request doesn't arrive

    What you seeWhyWhat to do
    A customer who called didn't get a rating request For a call, the request goes out only by email, and the customer's email is neither in the card nor in the ticket Link the ticket to a contact with an email before “Solved” (what the customer gets)
    Customers complain about dozens of “Rate our reply” emails Someone solved many old tickets with a bulk action while rating was on Before a bulk cleanup, turn rating off or set “Closed” (when to turn it on)
    The CSAT tile shows a dash Rating is off, or nobody rated during the period Check the checkbox and the “asked” number (where to see ratings)
    A process solved the ticket, but no request went out The request goes out only when an employee sets “Solved” This is by design (when the request goes out)

    FAQ

    Can I ask for a rating again?

    No, the request goes out once per ticket. If the customer comes back and the ticket is solved a second time, there will be no second request.

    The customer clicked “Bad” by mistake. What should I do?

    The rating page has “Changed your mind? Rate “Good”” — the customer can change the rating themselves, and the report counts the latest one. A “Bad” notification already sent is not withdrawn.

    Does an agent see the ratings of their tickets?

    Yes: a badge in the ticket header and feedback in the feed. The agent gets a “Bad” notification if they are the assignee.

    Can I use a 1 to 5 scale or NPS?

    No, the rating is only “Good” or “Bad”: customers answer with one click.

    Will a request go out if I close the ticket with the “Closed” status?

    No. The request goes out only after “Solved” (when the request goes out).

    Where it is and who has access

    Turn on
    “Tickets” → gear → “Support desk settings” → “General” tab
    Results
    “Tickets” → view button → “Reports”
    Access right
    only “Management” can turn it on; ratings are visible to everyone who has access to the window
    Prepare
    customers' email addresses in their cards — for tickets from calls

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free