Why a forecast call needs set-up before reps join
Before a Teams forecast call, set attendee audio and video permissions, check lobby access, and agree on a speaking rule for phone callers.
Key takeaways
- Check attendee mic and camera permissions before reps join.
- Give phone callers a clear cue for when to speak.
- Check lobby access, including forwarded invites.
- Assign a co-organizer to handle interruptions and arrivals.
It falls apart quickly when the room is noisy, when someone who was not invited is waiting to get in, or when a rep's microphone picks up the road noise from a car. Teams has settings that address several of these problems, and checking them before reps join helps avoid interruptions. Once the call is running, you end up muting people in front of their peers, and nobody enjoys that.
The revenue leader who runs the weekly forecast review for a sales team usually faces this problem. The call pulls in reps from several cities, a few of whom dial in from their phones, plus two finance partners who only need to listen. Last quarter the call opened with a dog barking, a rep typing with an open microphone, and a former colleague who had been forwarded the invite and walked straight in. The leader spent the first stretch of the call on cleanup and never reached the deal reviews that mattered most.
Those first minutes cost more than they look like they do. The forecast review is where a leader decides which deals get support and which get pushed out of the quarter. When the call starts late or fills with noise, the discussion gets shorter, and the deals that need the most time are often the ones that get cut. A few minutes of setup before the call is the cheapest help you can give those deals.
Use this sequence for your next call. Your team's names and deals will differ, but the decisions are the same: who joins muted, who waits in the lobby, and who can speak. Each section below picks up the same example so you can see the settings working together.
Setting 1: Keep attendee mics and cameras off
The first setting is the default for attendees. Microsoft's support page on attendee audio and video permissions says: "All attendees (but not presenters) will join the meeting with mic and camera off." For a forecast call, that default fits. Reps are there to report numbers. The leader and a small group of presenters need to speak freely, and everyone else should listen until they are asked to talk.
The rule in this example is simple. The people who need to speak are set as presenters, which means they are not covered by the mic-and-camera-off default. The leader picks presenters on purpose: the sales leaders who own the deals under review, and the deal desk lead who answers pricing questions. Adding everyone who might possibly need to talk defeats the purpose, because then the default does nothing.
The finance partners are the simplest case. They are attendees, not presenters, so the attendee controls apply to them. When the finance team needs to answer a question about revenue timing, the leader can change their mic permission before asking them to unmute. That keeps the default doing its job while still giving them a clear route to speak.
The default also protects the review itself. When the room is quiet, the leader hears each rep's answer clearly, and questions about close dates and deal stages go to the people who own those deals. The leader noticed that a quieter room made it easier to catch the moment when a rep hesitated on a close date, which is exactly what the review is for. Use a close date change log to keep the reason for a changed date beside the discussion.
The leader also tells the reps what to expect. The invite explains the attendee controls and says they can message the host directly if they want to speak. Without that note, a rep who joins muted can assume something is broken and start poking at settings during the first minute of the call. A clear line in the invite stops that confusion before it starts.
You do not have to get this exactly right when you write the invite. The same page says: "After scheduling the meeting and sending out the invite, the meeting organizer can disable the mics and cameras so that attendees can't use them during the meeting." The leader used this after a rep had already received the invite and the team asked for quieter joins. Still, do not rely on remembering to fix it later. Check the meeting options once after the invite goes out and again before the call starts. A setting you changed earlier in the week can be easy to forget by the time the call begins.
The organizer also has control during the call. The same page says: "Organizers, co-organizers, and presenters can turn off the mic or camera of all the attendees, or of individuals, at any time during the meeting." This is the fallback. If a rep's microphone starts picking up a kitchen or a television, the host can mute that one person without stopping the discussion. The host also names a co-organizer ahead of time. When the host is sharing a deal review screen, the co-organizer can handle interruptions, so the call does not stall while someone looks for the right control. Because co-organizers and presenters have that power too, naming them is a decision, not an afterthought. Review the forecast call co-organizer roles before assigning that responsibility.
Phone dial-in: Agree on a speaking rule
The attendee settings do not cover everyone. The same Microsoft page says: "Currently attendees who call in to a meeting using the phone number provided in the meeting details won't be prevented from turning on their mic and camera." In plain terms, a rep who joins by dialing the number in the invite can unmute, even when the rest of the attendee settings are locked down.
This is the gap that caught the leader in the example. Two reps were on the phone from their cars. The attendee settings did their job for the attendees joining through the app, but the callers could still speak whenever they wanted. That is how road noise got into a forecast review. The fix was not a Teams setting. It was a rule, written into the invite and enforced by the people running the call.
The approach has three parts. First, every rep who will dial in is told to join by phone with their microphone muted, and the invite says so in plain words. Second, the host has a clear signal for when to mute someone. The host uses a short chat message to the co-organizer, who turns off the caller's mic. Third, the host calls phone callers by name when their deal comes up, so they know when to unmute. A rep who hears their name is far less likely to talk over the room by accident.
Phone callers also need a little planning before the call. The host asks each dial-in rep to confirm the number they will call from, so the co-organizer can match the caller to the list. A caller who is hard to identify takes longer to match to the list, and that delay is exactly what the host wants to avoid on a call with a tight agenda.
When a phone caller needs to speak in the middle of a deal review, the host treats it like any other request. The caller agrees beforehand how to request a turn, and the host opens the floor for that deal. The rule is not to block people from speaking. The rule is that speaking is a decision made by the host, not an accident made by background noise.
Be careful about relying on the dial-in behavior staying the same. The Microsoft page describes what happens "currently," which means the behavior may change. Before each new call type, check the current page, and plan for the case where a phone caller can still speak.
Setting 2: Control who waits in the lobby
The lobby decides who gets in and who waits outside. Microsoft's lobby options page for IT admins says: "The Teams meeting lobby prevents certain types of participants from joining a meeting until a meeting organizer, co-organizer, or presenter admits them." For a forecast call, the lobby is your first check. Reps and finance partners should be in the room, and anyone else should wait until someone who knows them lets them in.
The bypass option is where the setting gets tricky. The same page describes the option this way: "Only people who were invited applies only to participants who were sent an invite directly, who are part of an invited distribution list (of up to 10,000 users), or to whom an invite was forwarded." Read that carefully. That is how the former colleague got in last quarter. A rep forwarded the invite, the setting treated that person as invited, and the person went straight into the meeting.
The leader changed three things. First, the invite now goes to a named list of reps and finance partners, not to a broad sales alias. A named list is easier to check against the people expected at the review. Second, the invite asks reps not to forward it. A forwarded copy is a route in, and reps can tell a colleague to ask the host for an invite instead. Third, the leader checks the selected bypass option rather than assuming a named invite list keeps everyone else waiting.
The admit step needs an owner too. The leader decided that the co-organizer handles the lobby, so the leader can stay on the deals. Before the call, the co-organizer gets a short list of expected names taken from the invite. A person who appears in the lobby can then be checked against that list in seconds. Anyone who is not on the list waits, and the leader decides later whether that person should join for one specific deal.
Timing matters here too. If your company's IT admin controls the lobby options, the same page says: "Changes can take up to 24 hours to take effect." Do not ask for a change an hour before the call. The leader asked for the change the week before, tested it with a colleague from outside the company, and confirmed the result the morning of the call. If you cannot get a change in time, pick the lobby setting you already have and handle the exceptions by hand.
Run the order before reps join
This sequence runs from the week before the call to the call itself. It is written as a checklist because the order of the steps matters.
- Before the week of the call: Ask the IT admin about the lobby options. Leave enough time for changes to take effect and for a test. Confirm which lobby rules apply to your organization.
- When writing the invite: List the named attendees, not a broad alias. Include the phone speaking rule and the request not to forward the invite.
- After sending the invite: Open the meeting options and set attendee mics and cameras to off.
- Name the roles: Choose one co-organizer and the presenters. Keep the presenter list short. Make sure the co-organizer knows how to use the mute controls.
- Before the first rep is due: Open the meeting early. Check the lobby, check that the attendee settings are still in place, and confirm the co-organizer is already in the meeting.
- During the call: Follow the speaking rule, and have the co-organizer check lobby arrivals against the expected-names list before admitting them.
On the morning of the call, the leader repeats the check in the same order. The lobby setting is confirmed, the attendee settings are checked once more, and the co-organizer confirms that their mute controls work. If anything has changed overnight, the host posts a short note to the invite and reminds people who dial in to join muted. A last check costs little and keeps the first minutes of the call clean.
Illustrative example: Test the joining routes
In an illustrative test, 3 reps join: 2 through the app and 1 by phone. The app attendees join with mic and camera off. The phone caller mutes before the host calls on them, then unmutes to speak. The co-organizer practices muting that caller. A forwarded invite is tested separately to check whether it bypasses the lobby under the selected option; it is not assumed to wait.
What these settings don't fix
These controls handle who gets in, who speaks, and who is muted. They do not produce a good forecast. The leader still needed the deal data to be current before the call, and the owners of each deal still needed to prepare their numbers. The settings only protect the time the group has for the review itself. A clean meeting with stale numbers still produces a bad forecast.
The settings also do not handle the follow-up. The leader still sends a summary of changed deals after the call, and that summary is written from the notes the presenters made during the review. Any decision made in the room needs a written record somewhere else. Keep that record in the tool your team already uses for forecasts.
The settings also help only when the people running them know where the controls are. A co-organizer who has never muted anyone during a live call will hesitate at the wrong moment. Before the call, walk the co-organizer and presenters through the mute controls and the lobby admit step. A short practice run is worth more than a long list of settings nobody has used.
After the first call with these settings, the leader reviews what happened in the room. Did anyone speak who was not expected? Did a phone caller unmute without being called? Did anyone wait in the lobby longer than they should have? Each answer points to the attendee controls, phone rule, or lobby options, so the fix is usually a single change to the invite or the meeting options, not a rewrite of the whole process.
Keep the limits of this guidance in mind. The lobby timing is written for IT admins, so your organization's policy may differ, and the admin's setting is the one that counts. This post describes what Microsoft's pages say and how one team applies them. It does not replace your own tenant's policy or your company's rules about recording and sharing forecast data.
Today, open the next forecast call's meeting options with your co-organizer and run a short joining test before relying on the controls.
Related guides: AI call scorecard checks: 5 rules before the forecast · AI call summary: 5 fields to check before a review · Call transcript record: 4 fields before a deal review.
Questions
Does a forwarded invite guarantee a lobby wait?
No, a forwarded invite can qualify for bypass under the invited-people option. Test the selected option before relying on it.
What should you do if the test fails?
Identify which joining route behaved differently than expected, then adjust the meeting options or call instructions and test again.