diff --git a/contributors/guide/contributor-cheatsheet/README.md b/contributors/guide/contributor-cheatsheet/README.md
index d5e2f4609..b44e7a9b8 100644
--- a/contributors/guide/contributor-cheatsheet/README.md
+++ b/contributors/guide/contributor-cheatsheet/README.md
@@ -218,6 +218,8 @@ other forms of work that would be stored within a git repository.
   till the `[WIP]` or hold is lifted.
 - If you have not had your PR reviewed, do not close and open a new PR with the
   same changes. Ping your reviewers in a comment with `@<github username>`.
+- If your PR isn't getting enough attention, post a link to the PR in the
+  `#pr-reviews` channel on Slack to find additional reviewers.
 
 
 #### Example PR Description
diff --git a/contributors/guide/pull-requests.md b/contributors/guide/pull-requests.md
index c403c9741..f676c1e3c 100644
--- a/contributors/guide/pull-requests.md
+++ b/contributors/guide/pull-requests.md
@@ -172,6 +172,8 @@ things you can do to move the process along:
 
    * If you have fixed all the issues from a review, and you haven't heard back, you should ping the assignee on the comment stream with a "please take another look" (`PTAL`) or similar comment indicating that you are ready for another review.
 
+   * If you still don't hear back, post a link to the pull request in the `#pr-reviews` channel on Slack to find additional reviewers.
+
 Read on to learn more about how to get faster reviews by following best practices.
 
 # Best Practices for Faster Reviews