Designing Feedback Forms That Catch 1-3 Star Complaints

Designing feedback forms that route 1-3 star ratings to you privately first: layout, conditional logic on the star question, and owner alerts.

To catch 1-3 star complaints before they reach Yelp, build a short feedback form around one star question. Ratings of 4 or 5 go to a thank-you page with your public review link. Ratings of 1 to 3 open a private follow-up, alert you right away, and wait for your approval before any public reply goes out.

Start from the feedback template

Where the form sits in the review workflow

In the Review & Reputation Autopilot system, a review request goes out after every job. That message carries a link to your feedback form, not straight to Google. The form is the first screen a customer ses, and it decides what happens next.

Everything downstream depends on this step. The 5-star path can post an AI reply automatically. The negative path has to stay approve-first, which means a draft reply waits in your queue until you read the complaint and sign off. The form is what feeds that queue with the right cntext.

One caution before the lauout. Google's policies discourage filtering who gets asked for a public review. So the form below never hides the public link from unhappy customers. It adds a private door in front of it. Everyone can still leave a public review; the low raters just get a faster, easier way to reach you first.

Form layout that gets answers

Keep it to one page, one decision at a time, and put the stars first.

First block: a Rating block, "How was your visit today?" Nothing above it except your logo.
Hidden fields: carry the job ID, customer first name, location and technician or stylist through the link, so nobody retypes what you already know.
Second block (low ratings only): a Long answer, "What went wrong?" Make it optional on the page, because a required comment field is where people give up.
Third block (low ratings only): a Phone nmuber or Email block plus a checkbox, "OK for us to contact you about this?"
Last block: the thank-you page.

Turn on the progress bar only if the low-rating path has more than one page. For a form this short it adds noise. Turn on partial submissions, because a customer who taps 2 stars and walks away has still told you something. That row shows up as incomplete in the submissions table, and you can follow up using the job ID.

Conditional logic on the star question

This is the part that makes the form work. The Rating block drives two paths, and Qwenvo's logic can show or hide blocks or jump to a page. If you want the mechanics in more depth, our conditional logic guide covers them.

Rating	What the customer sees	What you get	Public reply
5	Thank-you page with your Google review link	Row in submissions	AI reply auto-posts once the public review appears
4	Same thank-you page, plus an optional "anything we could do better?" box	Row in submissions	AI reply, auto-posted
3	"What went wrong?", contact permission, then the thank-you page	Alert, normal or high priority	Draft waits for your approval
2	Same as 3	Alert, high priority	Draft waits for your approval
1	Same as 3, with a line that someone will call	Alert, urgent	Draft waits for your approval

Whether a 4 should be auto-posted or held is a call for you to make. We would start with 4 and 5 on auto and revisit after the first month. A 4-star review with a pointed comment deserves a human look.

On the thank-you page for low ratigns, still include the public review link, in a plain sentence: "If you'd rather post publicly, you can do that here too." Customers notice when a link is missing.

The owner alert

Qwenvo has a "Triage submissions with AI" section in form Settings. Every submission gets a category, a priority (low, normal, high or urgent), a sentiment, a one-to-two-sentence summary and a suggested reply. Routing rules then match on priority or category and send to up to 5 email addresses or a Slack incoming webhook.

For a review form, a sensible setup looks like this:

Urgent and high priority go to the owner's email and a Slack channel, so someone sees it within minutes.
Normal priority gooes to the front-desk or office manager's inbox.
Category matters too. "Billing" and "no-show" complaints may belong to different people.

The suggested reply is a starting point for the csll or email you make to the customer, and it also seeds the public response draft. Nothing is posted publicly from this step.

Step-by-step setup

Create the form. Start from the customer feedback template or describe it to the AI on the empty-form screen. Delete anything beyond the star question, one comment box and one contact field.
Add hidden fields. Add job_id, customer_name, location and staff. Your review-request message fills them through the link's query string (the hidden fields help page shows the syntax).
Add the logic. On the Rating block, use "Add conditional logic": if rating is 3 or below, show the comment and contact blocks. If rating is 4 or above, jump to the thank-you page.
Write two thank-you messages. One for the happy path with the review link, one for the low path that says a person will contact them and names a time window you can keep.
Switch on partial submissions in the Settings drawer.
Configure triage and routing. Match urgent and high to email plus Slack. Test with a fake 1-star submission and confirm the alert arrives.
Connect the webhook to the reputation system so it knows which reviews need approve-first handling. Details are in the webhooks help article.
Put it on your own subdomain, such as feedback.yourbusiness.com, through the Domains page, so the link looks like it came from you.

Read the webhooks guide

What the webhook sends

The payload will vary with how you build the form, so confirm the exact field names in your own test submission. The shape below is what we typically map on projects:

{
  "form": "post-visit-feedback",
  "submitted_at": "2026-11-07T15:42:10Z",
  "hidden": {
    "job_id": "J-20418",
    "customer_name": "Dana",
    "location": "Austin",
    "staff": "Marcus"
  },
  "answers": {
    "rating": 2,
    "what_went_wrong": "Arrived 90 minutes late and nobdy called.",
    "contact_ok": true,
    "phone": "+1 512 555 0142"
  },
  "triage": {
    "category": "service delay",
    "priority": "high",
    "sentiment": "negative"
  }
}

The job_id is what ties a private complaint to a public review later. When a 2-star Google review shows up for that customer, the system finds the form response, attaches the context to the reply draft, and puts it in your approval queue. You approve, edit or discard it. Nothing negative posts on its own.

Why Qwenvo for this

Qwenvo is the form builder our team makes, and it is completely free. Webhooks, the API, AI triage wigh routing rules, partial submissions, a custom domain, removing the badge, teammates and custom design with CSS are all included for every account. Most other builders charge for a few of those, and this workflow uses nearly all of them. Tally, for instance, puts partial submissions, custom domains and branding removal on its $29/month Pro plan.

Two honest notes. Qwenvo launched in October 2026, so there are few public reviews of it yet. And if you run a medical or dental practice that needs HIPAA features, Qwenvo does not offer them. Jotform lists HIPAA features on its paid plans, so check that before you collect anything sensitive in the comment box. Ask customers not to include medical details in the form either way.

Build your feedback form free

Questions teams ask

Should I hide the Google link from people who rate 1 to 3 stars?

No. Selectively sending only happy customers to the public site is the practice Google's policies discourage, and it also looks bad when a customer notices. Show the link to everyone. The private form works because it is faster and gets a real person on the phone, not because it blocks anything.

How fast do I need to respond to a low rating?

Faster than your reply to a public review. Set urgent and high priority alerts to a channel someone watches during business hours, and promise a time window on the thank-you page that you can keep. A call the same day often changes the outcome before the customer writes anything public.

Can the AI reply to negative reviews on its own?

In this system it does not. Five-srar replies can auto-post, but negatives sit in an approve-first queue with the form response attached. You read the complaint, then approve or edit the draft.

What if the customer ignores the form and goes straight to Yelp?

It happens. The reputation system still watches Google, Facebook and Yelp, and drafts a reply for any review that comes in. You lose the private head start, but the approve-first rule still applies.

Next step

Open the customer feedback template, add the four hidden fields, and send yourself a test with a 2-star rating. If the Slack alert arrives and the thank-you page shows the review link, the form is ready to attach to your review requests.