A generic feedback form -- a rating scale plus an open comment box -- collects useful data, but treats every response the same on the way in: same submission, same inbox, same non-response until someone happens to read it. A five-star rating with glowing feedback and a one-star rating describing a real problem land in the same undifferentiated pile, when they call for completely different, and differently urgent, next steps.
Score is a routing signal, not just a metric
The rating a customer gives is useful for tracking NPS or CSAT over time, but it's also immediately actionable as a routing signal the moment it's submitted. A low score paired with a specific complaint is a candidate for fast follow-up, potentially before the customer churns. A high score is a candidate for a very different next step -- asking for a public review, or a testimonial, while the sentiment is fresh.
Structuring a feedback form that routes, not just collects
- Branch the follow-up question by the initial score. A low score should trigger a specific "what went wrong?" follow-up, structured to capture something actionable (which part of the experience, not just open-ended venting). A high score should trigger a different follow-up -- "what worked well?" or a direct prompt to leave a public review, while they're already in a positive frame of mind.
- Flag low scores for immediate internal visibility, not the standard queue. A response landing in a low-score range should be tagged distinctly from the moment it's submitted, so it's visible in the response queue without anyone having to scroll through a mix of scores to find the ones that need urgent attention.
- Route high scores toward the ask that actually helps -- a review, a referral, a testimonial -- rather than a generic "thanks for your feedback." This is the moment a happy customer is most willing to publicly vouch for you; a form that doesn't ask in that moment wastes it.
- Keep the initial rating question fast and frictionless. A single tap or click for the score, with the branch-specific follow-up appearing only after -- not a wall of questions before anyone's even given the headline rating.
The same feedback form asking a happy customer for a review and an unhappy customer what went wrong isn''t two features -- it''s one branch point most feedback forms never build.
Why undifferentiated feedback forms quietly fail
A feedback form that treats every response identically tends to produce a stream of ratings that get reviewed periodically -- weekly, monthly -- rather than acted on individually. That's fine for trend-tracking, but it misses the response that needed same-day attention, sitting in the same queue as routine feedback until the next scheduled review catches it. Routing by score fixes exactly that gap.
Building this without a developer
Branching the follow-up question and tagging the response by initial score is buildable visually using the logic engine's branching. The work is deciding what the low-score and high-score follow-ups should actually ask, not building the branching logic itself.