Skip to main content

An unhappy review is a support case

Send Low Ratings to Your Helpdesk

When a customer leaves two stars in your testimonial form, the person who can fix their problem usually works in the helpdesk, not in the testimonial queue. StoryProof can send every new review to your own tools through a webhook. Route that into a middleware step that keeps the low ones and opens a ticket, and the complaint gets an owner, a queue position and a reply history.

  • Webhook in, filter on the rating, ticket out
  • Built from a real test delivery, not a guess
  • Support replies; marketing stays out of it

The problem, solved

Why low ratings never reach support

Situation 1 of 5

The two star review sat unread

Testimonial queues get checked when someone needs a quote for the website. A complaint can wait there for a week.

How StoryProof solves it

From Pro, a webhook sends every new review to your own tools as it arrives, so a middleware step can see it within minutes.

Wiring checklist

Connect low ratings to a helpdesk ticket

Zendesk is the worked example because its ticket API is short and public. Other helpdesks have their own ticket creation step; follow their docs for that part. Middleware steps use Zapier’s Catch Hook, read on 2026-11-17.

Catch the webhook
Read the real delivery
Filter and open the ticket
Agree who does what

Ticks stay in your browser. Nothing you tick is stored or sent.

What one ticket might look like

Illustrative ticket, not a real customer

Subject: Low rating from testimonial form (2 of 5)

Tags: testimonial-low-rating

Priority: high

Comment: the review text exactly as the customer wrote it, followed by a note that it came from the StoryProof webhook and is not public.

In StoryProof

Set it up end to end

  1. 1

    Add the receiving URL

    Create the catching step in your middleware, copy its URL and add it where the StoryProof app lists webhooks.

  2. 2

    Send a low test review

    Submit one review through your own form with a low rating, then inspect what the middleware received before writing any filter.

  3. 3

    Filter, then create the ticket

    Keep only low ratings and map the review text into the ticket comment. In Zendesk that is a POST to the tickets endpoint with a comment body.

  4. 4

    Switch on the team alert as a backstop

    On Pro, turn on the low rating alert so your team hears about a 2 star review even if the ticket link fails.

  5. 5

    Tag the review once it is handled

    When the ticket closes, tag the review in StoryProof, for example "handled in support", so nobody approves it for the website by mistake.

What happens next: Once a month, compare the number of low ratings in StoryProof with the tickets tagged testimonial-low-rating. A gap means the link dropped something.

Before you start

What to know before you rely on it

  • No native helpdesk integration

    StoryProof is not claimed to connect to Zendesk or any helpdesk directly. The webhook is the only link, and middleware or your own endpoint does the rest.

  • Payload details are not published here

    Field names, event names, retries and signatures are not documented on this page. Build only from a test delivery you have inspected.

  • Webhooks need a paid plan

    Webhooks start on Pro. The in-app alert for a new review is on every plan, but it does not open tickets.

  • Vendor steps as of 2026-11-17

    The Zapier and Zendesk details follow their official docs as read on 2026-11-17 and have not been followed on a live account by us. Menus and plan limits change.

  • Middleware costs and limits are yours

    Zapier, Make or your own endpoint carry their own plans, task counts and failure handling.

FAQ

Questions people ask

Short answers to what usually comes up next.

Can I skip middleware and point the webhook straight at Zendesk?

Zendesk’s ticket endpoint expects its own request shape and authentication. Unless you have checked that the StoryProof delivery matches it, put a middleware step or a small endpoint in between.

What threshold should count as low?

Two stars or fewer matches StoryProof’s own low rating alert, which keeps the ticket and the alert in step. Some teams add 3 stars as a lower priority.

Should the review still be considered for the website?

Usually not while the ticket is open. If the issue is resolved and the customer later says something kinder, ask for a new testimonial rather than editing the old one.

Does this work with Freshdesk or Help Scout?

The same pattern does: catch the webhook, filter, create a ticket. The ticket step follows that helpdesk’s own docs, which this page has not covered.

Still have a question? Ask the StoryProof team or book a demo.

Give every unhappy rating an owner

Collect reviews in StoryProof and send each new one to your own tools, so the low ones reach support fast.

Sources

  1. Trigger Zaps from webhooks, Zapier. Checked 2026-11-17.
  2. Ticketing API: Tickets (Create Ticket), Zendesk. Checked 2026-11-17.

Last updated 2026-11-17.