diff --git a/docs/outreach/mentoring.md b/docs/outreach/mentoring.md
index 4c54d7f023..41bc3685f0 100644
--- a/docs/outreach/mentoring.md
+++ b/docs/outreach/mentoring.md
@@ -14,6 +14,10 @@ and help make sure that everything is on track. You are also expected to help
 program administrators keep an eye on your mentee's progress, and flag any
 concerns you might have.
 
+Mentors can refer to the excellent [GSoC Mentor
+Guide](https://google.github.io/gsocguides/mentor/) for detailed guidance,
+including GSoC's expectations, and best practices that can apply to any program.
+
 ## Who can mentor
 
 In order to mentor with Zulip, you need to have spent significant time working
@@ -74,6 +78,24 @@ is a good chance others would also find it confusing. Asking your
 mentee for an explanation will itself be valuable feedback on what
 parts of the PR need to be commented or rewritten in a more clear way.
 
+### Establishing communication patterns
+
+Over the course of the program, you will interact with your mentee both
+synchronously (e.g., on calls, pair programming, and/or via chat in the
+development community), and asynchronously (in the development community and on
+GitHub).
+
+It's important to ensure that there are regular opportunities for synchronous
+interactions, which are the best way to resolve some types of questions and
+concerns, and will help your mentee feel supported.
+
+Please schedule at least one synchronous interaction opportunity with your
+mentee per week. A weekly call is highly recommended, as calls can be especially
+helpful for getting a feel for how your mentee is doing, and lowering the bar
+for asking questions and sharing concerns. A good pattern might be a weekly
+call, plus 1-2 other regular time slots when you and your mentee check in in the
+development community.
+
 ## Managing challenges
 
 We rely on you to proactively flag your concerns to Zulip's program