Better conference calls aren’t about being charismatic—they’re about running a repeatable system: a clear agenda, the right host controls, and disciplined follow-up.
This how-to guide is built for beginner to intermediate teams that want meetings people don’t dread (and that actually ship decisions).
Quick take (read this first)
- If your call has no agenda, you don’t have a meeting—you have a group chat with a calendar invite.
- If your call has no host controls, one noisy mic can derail the entire session.
- If your call has no follow-through, you’re paying meeting time for nothing.
Step 1: Pick a tool that supports basic host control (and confirm your settings)
You don’t need a “perfect” conferencing tool, but you do need predictable control over audio and participation.
- In Google Meet’s participant mute guidance, Google notes you can mute participants, but for privacy reasons you can’t unmute another person—so your process must rely on clear turn-taking and requests to unmute.
- Zoom documents that admins can enable auto-muting participants when they join, and that the host can control whether participants can mute or unmute themselves during a meeting.
How to verify (2 minutes): Open your tool’s meeting settings and confirm: “mute on entry,” “who can present,” “screen share restrictions,” and whether the host can lock audio/video for attendees.
Step 2: Design an agenda that forces outcomes (not updates)
A good agenda is the simplest way to stop meetings from drifting and to keep participants prepared.
Harvard Business Review explains that an effective agenda sets expectations for what needs to occur before and during a meeting, helps people prepare, allocates time wisely, and clarifies when discussion is complete—use that as your baseline for every recurring call.
A practical agenda template (copy/paste)
| Section | Time | Owner | Output (required) |
|---|---|---|---|
| Context + goal | 2–3 min | Host | One sentence: “We are here to decide X / align on Y.” |
| Decision #1 | 10–15 min | DRI | Decision + owner + deadline |
| Decision #2 (optional) | 10–15 min | DRI | Decision + owner + deadline |
| Risks / blockers | 5 min | Group | Top 1–3 blockers + next step per blocker |
| Recap + assignments | 2–3 min | Host | Read back action items and confirm owners |
Step 3: Assign roles (so the host isn’t doing everything)
- Facilitator/host: Keeps the call moving, enforces the agenda, and uses host controls when needed.
- Timekeeper: Gives time warnings and calls out scope creep.
- Notes + actions owner: Captures decisions and action items in real time.
If your team uses Teams, Microsoft documents that meeting notes in Microsoft Teams can include an agenda, notes, and tasks, and that notes are saved automatically—use that to make action items harder to “lose.”
Step 4: Run the call like an operator (tight opening, controlled discussion)
Open strong (first 60 seconds)
- Restate the meeting goal in one sentence.
- State the decision(s) you expect to make.
- Set one participation rule (example: “One speaker at a time—use raise-hand or chat to queue.”).
Use mute as a quality control tool (not a power move)
If you’re hearing feedback, barking dogs, or side conversations, mute is the fastest way to restore focus.
In Google Meet, the help documentation explicitly notes you can mute participants, but you can’t unmute them for privacy reasons—so you should pair muting with a clear cue like, “Unmute when you’re ready to speak.”
For larger or higher-risk calls: consider “locks”
Google Workspace Updates explains that Google Meet added Audio and Video Lock so hosts can prevent participants from turning their microphones/cameras back on until the host unlocks them.
When not to use this: For small, collaborative meetings—hard locks can reduce participation and can feel adversarial if you don’t explain why you’re using them.
Step 5: End with receipts (decisions + action items + owners)
- Read back decisions, then ask: “Is anyone strongly opposed?”
- Read back action items with owner + deadline.
- Confirm what happens if an action item slips (who gets pinged, and when).
To make follow-through repeatable, add a standard recap email format at meeting recap email template.
Implementation checklist (print this)
- Agenda sent with goals, timeboxes, and owners.
- Roles assigned: host, timekeeper, notes/actions owner.
- Tool settings verified (mute on entry, screen share permissions, presenter rules).
- Live notes captured with decisions + action items.
- Recap sent the same day with owners + deadlines.
Troubleshooting
Problem: The call derails into random topics
- Fix: Put “parking lot” at the bottom of the agenda and move off-topic items there.
- Fix: Timebox discussion and force an output (“decision” or “next step”).
Problem: Background noise ruins the meeting
- Fix: Enable “mute on join” where your platform supports it; Zoom documents an admin option to auto-mute participants when they join.
- Fix: Use platform mute controls and a clear speaking queue (raise-hand/chat).
Problem: People stay quiet and you get no engagement
- Fix: Ask binary questions (“Option A or B?”) instead of open-ended prompts.
- Fix: Assign one person to speak first on each agenda item (remove the “awkward silence tax”).
FAQ
Do I really need an agenda for a 15-minute conference call?
Yes—especially for short calls. HBR notes an effective agenda helps people prepare, allocates time wisely, and identifies when discussion is complete.
Why can’t I unmute someone in Google Meet?
Google Meet’s help documentation states that for privacy reasons, you can’t unmute another person—you can only ask them to unmute.
What’s the simplest way to stop “hot mic” chaos?
Start the meeting with participants muted by default when your platform supports it; Zoom documents an admin setting to mute all participants when they join.
How do I keep action items from disappearing after the call?
Use a single place for meeting notes and tasks. Microsoft documents that Teams meeting notes let you add an agenda, notes, and tasks, and that meeting notes are saved automatically.

💬 Comments