Verify 7 meeting settings before sales coaching starts

A

Schedule cross time zone sales coaching meetings by reviewing time zones and setting up dial-in and reminder details

Key Takeaways

• Review all participants’ time zones before confirming a necessary meeting, as noted in GitLab guidance.
• Verify the seven specific settings: time zone review, recording decision, agenda naming, dial-in number, reminder creation, channel visibility, and event creation.
• Use the time zone check to respect remote participants across different regions during recurring coaching sessions.
• Confirm dial-in details and reminder mechanisms to ensure reliable access for your sales team members.
• Apply these checks before sending invites to maintain consistency in your remote coaching schedule.

Open your calendar, select a recurring coaching slot, and verify the time zones of all attendees before sending the invite. This initial step aligns with the principle that when a meeting is determined to be necessary, you must review all participants’ time zones, according to GitLab. Your coaching sessions often span multiple regions, so this review is the first of seven settings to verify. The other six settings cover recording decisions, agenda naming, dial-in numbers, reminders, channel visibility, and event creation. Each setting addresses a specific part of the scheduling process.

Start by listing every attendee and their local time zone. Do not assume a single time zone applies to the whole team. The GitLab handbook emphasizes this review as a prerequisite for necessary meetings. Your B2B software sales team likely includes reps in different geographic areas. A coaching session that works for one region may fall outside working hours for another. Checking time zones first prevents scheduling conflicts that disrupt coaching continuity.

B

Review time zones and decide on recording

Start by acknowledging the geographic reality of your remote team. A meeting with team members will usually traverse multiple time zones, according to GitLab. This baseline assumption shapes how you structure the session. You cannot assume a single local time works for everyone. The All-Remote Meetings | The GitLab Handbook documentation frames this as a standard condition for distributed groups. Your scheduling process must account for this variance from the first step.

When you identify that your coaching session involves participants across different regions, you must make a specific decision about recording. For group meetings where there are multiple time zones, consider recording the meeting to allow for async participation, according to GitLab. This is not a mandate for every single interaction. If your coaching session is a one-on-one within the same time zone, this specific GitLab guidance does not apply. However, if you are running a team drill or a group review that spans three or four regions, the recording option becomes a critical tool for inclusion.

Do not treat this as a universal rule for all meeting types. The scope of this advice is strictly limited to group meetings with multiple time zones. Applying it to a simple two-person sync in the same time zone is unnecessary and potentially intrusive. The value here is asynchronous access. A rep who is in a time zone where the live session falls at 11 PM can watch the recording at 9 AM the next day. This aligns with the goal of reliable access for your B2B software sales team.

C

Set up the meeting details in Teams and Google

When configuring the agenda for your coaching sessions, ensure that both the first and last names of every team member are displayed when referencing them, according to GitLab. This specific naming convention applies to the meeting agenda context described in the All-Remote Meetings handbook section. While GitLab provides this rule for agenda references, you must verify how this aligns with your own internal documentation standards for sales coaching logs.

To create the actual calendar entry for these cross-time zone sessions, you can use Google Calendar. According to Google, you begin the process by clicking Create, then Create event, and finally More options at the top left of the interface. This sequence opens the detailed view where you can input specific scheduling parameters. Once the event details are populated, you must fill in the details of your event and click Save to finalize the creation, as instructed by Google.

For managers coordinating across different regions, visualizing the time differences is critical.

When integrating these steps into your broader coaching workflow, consider how the agenda naming and event creation interact with your existing tools. If you are using Microsoft Teams, note that the specific dial-in and channel visibility rules are covered in a separate section of this guide. The Google Calendar steps outlined here provide a neutral foundation for the event creation phase. You should ensure that the agenda text you paste into the description field adheres to the full-name requirement noted by GitLab, even if the calendar platform itself does not enforce this format automatically.

The key is to maintain consistency in how attendees are named and how the event is structured across all platforms you use.

D

Add dial-in numbers and channel visibility

When configuring a remote coaching session, you must verify how participants will join the call. For Microsoft Teams, the documentation states to include a dial-in number and conference ID so that participants can call in to the Teams meeting Microsoft. This requirement ensures that attendees have a reliable phone-based access method if their internet connection is unstable or if they are traveling. You should confirm that these specific details are present in your meeting invitation before sending it to your sales team.

If you create the meeting directly from Outlook, the process for adding these details is automated. According to Microsoft, if you schedule the meeting from Outlook, the dial-in number and conference ID automatically appear in the scheduled meeting invite. This behavior applies specifically when the scheduling action originates from the Outlook interface. If you are using a different method to create the Teams meeting, you must manually check that the dial-in information is included, as the automatic population is tied to the Outlook workflow described in the source.

Visibility of the meeting within your team structure is another critical setting to verify. Microsoft explains that when you have a meeting in a channel, everyone in the team will be able to see it and join it in that channel Microsoft. This rule defines the scope of access for channel-based meetings. If your coaching sessions are private and should only be visible to specific individuals, you must ensure the meeting is not placed in a public channel where the entire team can see and join it. Conversely, if you want the whole team to have visibility and access to the coaching session, placing it in a channel aligns with this documented behavior.

E

Create reminders and manage async agenda items

Slack provides a specific method for setting up automated nudges to keep your coaching schedule on track. To begin, you must select a date and time for your reminder, as described in the "Set a reminder" guide according to Slack. This step anchors the notification to a precise moment in your team's calendar. For example, the documentation illustrates the command structure with "/remind #marketing-team to submit expenses every Thursday," showing how a recurring prompt can be directed to a specific channel according to Slack. While this example uses a marketing team, the same syntax applies to sales coaching channels where you might remind reps to review call notes or prepare demo scripts.

When choosing where to place these alerts, consider the complexity of the task. Channel reminders work best for simple team reminders, according to Slack. This distinction is critical for front-line managers who balance high-stakes coaching sessions with routine administrative tasks. If your agenda item involves a multi-step review process, such as analyzing a recorded demo or preparing a detailed feedback report, a simple channel reminder may not provide the necessary context or structure.

For your sales coaching workflow, map your reminder types to their complexity. Use channel reminders for straightforward prompts, like "Submit your weekly pipeline update" or "Review the shared scorecard." These are low-cognitive-load tasks that benefit from the visibility of a public channel. For more nuanced coaching follow-ups, such as "Review the timestamped notes from Tuesday's call and draft three improvement points," consider a different notification method that allows for richer context. This approach aligns with the guidance that channel reminders are optimal for simple tasks, ensuring that your team does not overlook critical, complex actions due to a lack of detail in the notification itself.

F

Reference table of scheduling rules by publisher

The following table lists the seven settings to verify before your coaching session begins. Each row attributes the specific rule to the publisher that documents it.

These rules come from distinct documentation sources. GitLab provides the guidance on time zone reviews, recording decisions, and agenda naming conventions. According to GitLab, the handbook advises reviewing time zones for necessary meetings and considering recording for multi-zone groups. It also specifies that full names should appear in the agenda.

Microsoft documents the technical requirements for dial-in access and channel visibility. According to Microsoft, you must include a dial-in number and conference ID for Teams meetings. The same source notes that channel meetings are visible to everyone in the team.

Slack offers a simple method for setting reminders. According to Slack, the process involves selecting a specific date and time for the reminder.

G

FAQ: How to schedule cross time zone sales coaching meetings with reminders

What should I check regarding time zones before scheduling a necessary meeting?

According to GitLab, when a meeting is determined to be necessary, review all participants’ time zones. This applies even though the organization has a bias toward asynchronous communication.

How should I format names in the meeting agenda?

According to GitLab, ensure that both the first and last names are displayed when referencing a team member’s name in the meeting agenda.

Can I use a dial-in number for Teams meetings?

According to Microsoft, include a dial-in number and conference ID so that participants can call in to the Teams meeting.

How do I set a reminder for a specific date and time?

According to Slack, select a date and time for your reminder.

Should I record meetings that traverse multiple time zones?

According to GitLab, consider recording the meeting to allow for async participation for group meetings where there are multiple time zones.