See how shoppers felt after getting help, which support paths are creating promoters or detractors, and which unhappy customers still need a human follow-up.
Garrio sends satisfaction requests after supported conversations, then rolls the responses into one merchant view. This is where you spot whether shoppers are unhappy because of slow follow-up, unclear policies, damaged orders, or a support path that keeps creating extra work.
The fastest workflow here is simple: check callback requests first, then read the latest detractor comments before you decide whether the fix belongs in Queues, Knowledge, or your store operations.
76
Range: -100 to +100
SuccessExcellentResponse breakdown
2
Customers waiting for a callback
These are customers who rated their experience poorly and requested to be contacted.
Loading distribution chart...
68 responses with written feedback this period
The team fixed the damaged order quickly and the replacement arrived exactly when promised.
Maya R.
I got help in the end, but I still had to repeat the sizing problem before someone took ownership.
Jordan T.
Helpful update and clear next steps. I only wish the return window had been explained sooner.
Avery P.
Start with callback requests and low scores. If the complaints are about delays or broken promises, fix the queue workflow. If they are about confusing answers, tighten Knowledge or assistant instructions. If they are about the product or shipping itself, hand the pattern to the person who owns that part of the store.
Channel breakdown matters when one path is dragging the score down. A healthy overall score can still hide a rough escalation flow or a draft-review path that needs work.
The live route does not invent a score if survey responses are still sparse. Merchants will see a simple `No NPS data available` or `No NPS responses found for this period` state until Garrio has enough feedback to summarize.
That matters because the next step is usually operational, not analytical: keep using Queues, keep follow-up moving, and come back here once more post-support feedback has been collected.