Follow these steps
Complete the workflow, then verify it
- 1
Choose Zendesk as the destination
In Create Flow, select Zendesk for the destination integration and follow the authorization steps shown by ReviewBot.
- 2
Confirm the helpdesk account
Choose the Zendesk account or subdomain that your support team uses. Confirm the connected account belongs to the intended environment before enabling delivery.
- 3
Set triage rules
Route low-star, billing, login, crash, or refund keywords to the support workflow that has an owner. Avoid sending every review into the same queue until the team has tested the volume.
- 4
Decide the response path
Use the review link and source context to decide whether the issue needs a public response, private support, or product follow-up. Keep private account details out of public replies.
- 5
Test the ticket handoff
Save the Flow and send a test alert. Verify the ticket or notification contains the review text, rating, source, app context, and original link.
Quick checklist
- ✓Zendesk authorization is complete.
- ✓The destination queue has an owner.
- ✓Rules map to a real support action.
- ✓A test review can be traced to its source.
If something does not work
The Zendesk destination is not available+
Reconnect the account and check that you returned to the same ReviewBot workspace. If the authorization succeeds but the destination remains unavailable, contact support with the non-sensitive setup details.
Tickets are duplicated or hard to route+
Narrow the Flow rules and separate urgent low-star or keyword work from a scheduled trend report. Keep one owner per queue.
Frequently asked questions
Should every review create a Zendesk ticket?+
Usually not. Use rules for reviews that need a support action and keep the complete stream in ReviewBot or a scheduled report.
Can I connect Zendesk and Slack?+
Yes. Use separate Flows when support needs tickets and product needs channel visibility, with rules that match each team’s action.