Set up Review Router
Route GitHub pull requests into Slack in about three minutes.
Activate Team access
An organization owner or admin opens Billing and completes secure Checkout before routing or setup test deliveries can start. Checkout shows the seat total and first charge date. Existing customers retain access until the deadline in their migration notice; completing Checkout starts their full 30-day trial.
Then connect your tools and create the first route below.
Install the GitHub App
Connect your GitHub organization or personal account. Tenpace only needs read access to pull requests and repository metadata. During install you choose which repositories to grant access to — you can restrict it to specific repos.
Start Review Router setup →Authorize Slack
Connect your Slack workspace and choose which channel receives PR notifications. Tenpace posts one message per PR and updates it in place — no flood of notifications.
You can configure multiple channels for different repositories or teams.
Link team members
Each team member links their GitHub and Slack accounts once, via their profile page. After that, @mentions and DMs route automatically — no configuration needed per-PR.
Team members who haven't linked yet still appear in PR messages, but won't receive direct Slack mentions.
How notifications work
- PR opens — One message posted to your configured channel with PR details, reviewers @mentioned.
- Review submitted — PR author notified directly via Slack DM.
- Changes pushed — Reviewers notified, message status updated in place.
- PR merged or closed — Status updated, no new message to keep the channel clean.
- Daily digest — Optional daily DM summarizing PRs that need your attention.