Feedback only helps when the right person sees it. ReviewMySites can post every new comment to the place your team already talks, or send it to your own systems. Here is what connects today, and which guide to follow.
Pick where the feedback should go
| Connect | Best for | Plan | Guide |
|---|---|---|---|
| Slack | Teams that live in Slack. One card per comment, updated in place, with a thread for everything after it. | Every plan | Slack guide |
| Microsoft Teams | Teams on Microsoft 365. A card in the channel for each new comment. | Every plan | Teams guide |
| Google Chat | Google Workspace teams. A card and a thread per comment. | Every plan | Google Chat guide |
| Discord | Studios and communities. Each comment as its own forum post. | Every plan | Discord guide |
| Webhooks | Your own systems, or an automation tool. Every event as signed JSON. | Pro | Webhooks guide |
| REST API | Your own code. Read comments, change them and reply. | Pro | API guide |
Where you connect them
Integrations belong to a project, so one client's feedback can go to one channel and another's somewhere else. Open the project's settings, from Settings in the ⋯ on its card or the gear at the top of its board, and choose Integrations. Owners and admins connect things. Members can look but not change them.
A project can post to several places at once, and to several channels in the same app.
You choose what gets sent
Each connection has its own What to send settings:
- Which events. New comments, replies, status changes, assignments.
- Which details. Page, assignee, status, priority, due date, tags, device and more, field by field.
- Only what matters. Urgent comments only, or only comments that @mention someone.
- The screenshot. Turn it off for a channel that clients can see, if you prefer.
What happens when something breaks
If an app is down, the post is tried again later. If a connection keeps failing, it shows as Not working in settings with the reason, and after 5 failed posts in a row it pauses and the workspace owner gets an email. Comments are never lost on our side: they stay on your board whatever happens to the connection.
What is next
Jira, Linear, GitHub Issues and Zapier are on the way. Until then, a webhook can feed any automation tool that accepts one.