How did we do

One question, one click. When a ticket reaches a finishing status, the person who wrote in is emailed a rating request under your own brand. They click a score, land on a page that says thank you, and the answer files itself against the queue. No login, no form, no second question. When it asks You choose which of the status field's own values count as finished (Solved, Closed, Shipped) and how long to wait after a ticket gets there. The wait matters: a ticket is often marked solved a beat before the customer agrees it is, and asking in that gap invites a rating of the wrong moment. The ask goes out by email, worded with your question, under your logo and colours. This is your workspace asking its own customer, exactly like a booking confirmation. Asked once, and not hounded One ask per ticket, ever. A ticket reopened and re-solved does not ask again; the customer already answered, or already declined to. There is also a per-customer cooldown, so somebody who closes four tickets in a week is asked about one of them, not all four. A ticket with no email address is simply never asked — staff-entered tickets are ordinary tickets, not a problem. Where the answers go Scores are 1 to 5, with an optional comment. They gather on the queue's How did we do page, kept on their own ledger rather than as columns on the ticket: a rating is the customer's word, and a cell a person can type into is a cell a person can type into. Tips • The rating link works once. A spent or unknown link shows the same closed page, so nobody can probe which tokens were real. Good to know • Switching the survey off also drops any asks already queued but not yet sent — turning it back on later must not fire a backlog of stale requests. Who can do what • Admins configure the survey and see the scores page.