Today, what we provide is a way to handle code review without context-switching between Github and Slack/calls. Axolo helps to unstuck dangling pull requests in centralizing notifications in one place and let them be top of mind as a "to-do list" in your Slack.

> Where do you see the difference in a private message to someone that says "hey, can you check out this Pull Request?" and a Slack channel that automatically says "hey, can you check out this Pull Request?"

In case 1, you need to write in dm to your reviewers and ping them again if you did not receive any news. In the other case, Axolo will do it automatically and remind them about it. We believe it's easier to have specific channels because if you're requesting a review at the same time as your reviewer might, different conversations will happen in the same dm channel. And that's only regarding someone asking someone else for a review, there are other informations that have importance in your worklfow regarding pull requests (Github actions, comments & reviews)

Referring to the lack of time, we think that might be addressed in motivating engineers do more code reviews. We try to foster better practices with our "leaderboard" but we're still iterating to find the best answer.