Triage 1 and 2-star Trustpilot reviews into Zendesk and Slack
When a low-rated review lands on Trustpilot, we open a support ticket, alert your team in Slack, and draft a reply for someone to approve.
Watch Trustpilot for new service reviews posted about our business unit, and triage the bad ones automatically so they never sit unnoticed until someone happens to open the dashboard. Use a poll trigger on Trustpilot for a new review.
First, check the star rating. If the review is 3 stars or above, stop immediately and do nothing at all: no ticket, no Slack message, no reply. Only 1 and 2-star reviews continue past this point. This gate matters, because the whole value of the workflow is that the Slack channel stays signal only and every message in it is worth reading.
For a 1 or 2-star review, pull the full record with the Trustpilot Get Private Review operation using the review id from the trigger. This gives the reviewer's email address and the reference id alongside the review title, text, star rating, and the link to the public review.
Open a support ticket with the Zendesk Create Ticket operation. Set the subject to something scannable that names the rating and the reviewer, for example "1-star Trustpilot review from Dana W.". Put the full review text and the star rating in the ticket body, along with the reference id and the link to the public review. Set the reviewer as the requester using the email from Get Private Review, add a trustpilot tag, and set priority to high. Keep the ticket number that comes back.
Then draft a suggested public reply in our brand voice. It should acknowledge the specific problem the reviewer described rather than being generic, apologize plainly, and state the concrete next step we are taking. Keep it short, two to four sentences, the length a real support lead would actually post. Hard rule: the suggested reply must never promise a refund, credit, discount, replacement, or compensation of any kind, and must never imply one is coming. Any goodwill gesture is a decision a human makes, not something the draft commits us to in public.
Post a single message to our customer experience channel with the Slack Send a Message operation. Include the star rating, the reviewer name, the review text, a link to the public review, the Zendesk ticket number just created, and the suggested reply. Label the suggested reply clearly as a draft that needs approval, and say that a human should post it back to Trustpilot with Reply to Review once they are happy with it.
Do not post the reply automatically. Never call Reply to Review as part of this workflow. The agent drafts, Slack carries the draft, and a person approves and publishes. Keeping the human in the loop on anything that appears on our public review page is the point.
One resilience note: Get Private Review and Reply to Review are private Trustpilot endpoints that require a paid Trustpilot Business plan and may return a 403 if the account is not licensed for them. If Get Private Review fails, do not abandon the run. Create the Zendesk ticket from the public review data instead, leave the requester unset, and say in the Slack message that the reviewer's email could not be retrieved so someone can follow up manually.
Example output
What does this prompt do?
- Watches your Trustpilot page and picks up each new review as it is posted, so nobody has to sit on the dashboard.
- Only acts on 1 and 2-star reviews. Anything 3 stars and above is skipped entirely, so the channel stays signal only.
- Opens a Zendesk ticket with the review text and star rating, the reviewer as the requester, a trustpilot tag, and high priority.
- Posts one Slack message with the rating, a link to the public review, the new ticket number, and a suggested reply your team can approve and post back.
What do I need to use this?
- A Trustpilot Business account for your company.
- A paid Trustpilot Business plan, since seeing a reviewer's email address and posting replies are paid features.
- A Zendesk account the workflow can create tickets in.
- A Slack workspace, plus the channel your customer experience team actually watches.
- A few notes on your brand voice so suggested replies sound like your team wrote them.
How can I customize it?
- Change the star threshold. Some teams also want 3-star reviews flagged, others only care about 1-star.
- Send alerts to a different Slack channel, or split them by product line or region.
- Adjust the ticket priority, tags, and assignment, and tune the brand voice used for suggested replies.
FAQs
Will this reply to reviews automatically?
What happens to 3, 4, and 5-star reviews?
Can the suggested reply offer a refund or a discount?
Do I need a paid Trustpilot plan for this?
How fast will we hear about a bad review?
Related templates
When your flight moves, your calendar times get corrected automatically and you get a Slack note naming the meetings you're about to miss.
Every 15 minutes, forwarded phishing reports get traced back to the server that really sent them, with a verdict in Slack and the worst senders reported.
Every weekday at 7am, sign in to the tender portals you track, filter new notices against your bid criteria, and open a deal for the ones worth chasing.
Every Monday, rank the week's matches by expected demand, put the big ones on your venue calendar, and post a rota-ready summary to Slack.
Every Tuesday we pull your best new reviews, draft social captions, email testimonials and product page quotes, then stage them in Notion for approval.
Every weekday morning, unfulfilled orders get an address check: harmless typos fixed automatically, risky addresses held with a note to the customer.
Stop finding out about 1-star reviews a week late.
Every low-rated Trustpilot review becomes a high-priority ticket and a Slack alert with a ready-to-approve reply, while good reviews stay out of your way.