Most virtual meeting etiquette guides are still solving 2020's problem. Mute yourself. Test your webcam. Don't eat on camera. Tidy the bookshelf behind you. All fine, all settled, and none of it is what teams actually fight about anymore.
The arguments that burn real political capital now are three: whether cameras are mandatory, whether an AI bot may sit in and transcribe, and who is allowed to put things on your calendar. Two of the guides currently ranking for this topic were published in 2018 and 2020. They cannot help you with any of it.
So this covers the settled basics quickly, then spends its time on the contested rules where getting it wrong actually costs you something.
Key Takeaways
- Camera policy belongs to the team, not the individual. The conflict happens when nobody decided, so every participant applies a private rule and reads everyone else's choice as a signal. Write the default down and the friction disappears.
- An AI notetaker is a recording device. Announce it before it joins, not after. Recording law splits by jurisdiction, and in a call with external attendees you rarely know which rules apply to everyone on the grid.
- Calendar access is etiquette, not admin. Sending a booking link with real buffers respects the other person's day more than a "does Tuesday work?" email chain that takes four replies.
- The close matters more than the opening. A meeting that ends without a named owner and a date has to be repeated. That, not a messy background, is the expensive failure.
- The classic rules still apply, they just stopped being interesting. Mute, punctuality, and a working microphone are table stakes, not a policy discussion.
What virtual meeting etiquette actually covers now
It helps to split the topic in two. One half is genuinely settled: nobody in your organisation is going to argue that background noise is fine. The other half has no consensus at all, which is exactly why it generates conflict.
| Settled (just do it) | Contested (needs a written default) |
|---|---|
Mute when you are not speaking | Whether cameras are required |
Settled (just do it)Mute when you are not speaking Contested (needs a written default)Whether cameras are required | |
Test audio and video before you join | Whether AI notetakers may join |
Settled (just do it)Test audio and video before you join Contested (needs a written default)Whether AI notetakers may join | |
Join on time, end on time | Whether multitasking is acceptable |
Settled (just do it)Join on time, end on time Contested (needs a written default)Whether multitasking is acceptable | |
Use a headset in shared spaces | Who may book time without asking |
Settled (just do it)Use a headset in shared spaces Contested (needs a written default)Who may book time without asking | |
Don't talk over people | Whether meetings are recorded by default |
Settled (just do it)Don't talk over people Contested (needs a written default)Whether meetings are recorded by default | |
The right-hand column is where your etiquette effort should go. A rule in the left column enforces itself socially. A rule in the right column, left undecided, turns into someone quietly resenting a colleague for six months.
Rule 1: Decide your camera policy before the meeting, not during it
Camera policy is the most reliably contentious item on this list, and the reason is structural. When there is no stated default, every participant invents one, then reads everyone else's choice as a statement about engagement, seniority, or respect.
A 260-comment thread in r/remotework shows the mechanism: the original poster describes having landed at a cameras-off workplace by accident and being relieved by it. They did not choose the norm, they discovered it after joining, and it happened to suit them. Someone else discovers the same norm and reads it as a disengaged culture. Both readings are available because nobody wrote anything down.
What a workable camera policy looks like
The policies that hold up in practice are conditional rather than blanket. A blanket "cameras always on" collapses the first time someone takes a call from a hospital waiting room. A blanket "cameras off" makes new-hire onboarding genuinely harder.
Three conditions worth writing into your default:
- Cameras on for meetings under six people where you are expected to contribute. Small groups depend on reading the room, and there is nowhere to hide anyway.
- Cameras optional for all-hands, training sessions, and any call where you are primarily listening. Requiring video from forty passive attendees produces performance, not attention.
- Camera off without explanation is always acceptable. No note in chat, no apology. The moment people have to justify it, you have a surveillance policy wearing an etiquette costume.
The neurodiversity argument is the strongest one here and the least often raised in the meeting itself. Continuous self-view and sustained eye contact are meaningfully more tiring for some people, so a mandatory-camera rule taxes them specifically. A conditional policy removes that tax at almost no cost.
Skip this section if you run a team of three who already have a shared habit. Camera policy only needs writing down at the point where people stop being able to read each other's defaults.
Rule 2: Ask before an AI notetaker joins
This is the newest rule and the one with the widest gap between how often it comes up and how rarely it appears in etiquette guides. An AI notetaker is a recording device. Treat every question about it as a recording question.
The friction is current. A 90-comment thread in r/sales works through the middle ground created by transcription features that capture a call in real time without producing what the platform formally classifies as a recording, leaving participants unsure whether they were notified of anything. In a 30-comment thread in r/Zoom, the complaint is sharper: tools that connect to a calendar and start joining meetings without a per-meeting decision.
IT teams see it from the other side. A 120-comment thread in r/sysadmin describes an admin-consent control being routed around because the request came from an executive, and a separate 130-comment r/sysadmin thread covers external meetings where an unfamiliar notetaker link circulates mid-call.
The etiquette here is simple to state and slightly uncomfortable to perform:
- Say it in the invite. One line in the calendar description that notes a transcription tool will be used. This is the step that removes almost all of the awkwardness, because it moves the disclosure out of the live call.
- Say it again in the first thirty seconds. Name the tool, say what happens to the transcript, and pause. A pause is the difference between disclosure and consent.
- Make declining costless. If someone asks you to turn it off, turn it off and don't ask why. If your notes depend on nobody objecting, they were never consented to.
- Check the jurisdiction before you default to always-on. Recording consent requirements differ between US states, and calls with EU participants bring GDPR obligations around personal data in transcripts. A call with external attendees frequently spans more than one regime.
A design answer sidesteps part of this. A notetaker running locally on your own machine puts no bot in the participant grid and sends no audio anywhere, which changes what you are disclosing. meetergo's local AI meeting notes app transcribes on the device, and local transcription and dictation are free to use; speaker diarization and custom summary templates need an account on the Light tier at €9.90 per user per month. There is a longer version of the compliance argument in meetergo's piece on GDPR-compliant AI meeting notes, plus a roundup of meeting transcription software.
Local capture removes the bot from the room. It does not remove your obligation to tell people you are taking notes.
Rule 3: Treat someone else's calendar as theirs
Booking etiquette gets filed under admin, which is why it is done so badly. Every "does Tuesday at 3 work for you?" email costs the recipient a context switch and usually four replies to resolve. Across a week of external calls that is a real tax on somebody who never agreed to pay it.
Three rules that hold across almost every context:
- Send availability, don't request it. A booking link that shows real open slots is more respectful than making the other person audit their own calendar for you. meetergo's scheduling and booking pages are one route; the point is the pattern rather than the vendor.
- Build buffers into the link, not into your apologies. Back-to-back calls guarantee you arrive at the second one late and unprepared. Fifteen minutes between slots fixes it structurally.
- Never book across time zones from memory. Confirm in both parties' local time in writing. A time zone meeting planner takes ten seconds, and there is a longer guide on scheduling across time zones for remote teams if this is a recurring problem rather than an occasional one.
Recurring meetings need their own review cadence. A weekly sync that nobody has questioned in a year is not a ritual, it is an unreviewed standing charge on eight calendars. Whoever owns a recurring meeting series should be cancelling it about twice a quarter to see if anyone notices.
Cancelling well is part of this too. Late cancellations are normal, silent ones are not, and there is a short guide on responding to a meeting cancellation professionally that covers the wording.
Rule 4: Run the call so people don't have to interrupt
Interruption is the most common complaint about virtual meetings and the one most often misdiagnosed as rudeness. On a call with any latency, the conversational cues that let people take turns arrive too late to work. The medium removed the mechanism.
The host owns the fix:
- Circulate the agenda before the call, not during it. If you need a starting point, meetergo maintains a set of meeting agenda templates.
- Name the person you want to hear from. "Priya, does that match what you saw in the numbers?" outperforms "any thoughts?" by a wide margin, because an open invitation in a video call is an invitation to a two-second standoff.
- Give the chat a job. Questions in chat, decisions on audio. Without an assigned role, chat becomes a parallel meeting that half the participants miss.
- Use the raise-hand control and actually watch it. A queue only works if someone reads it.
Rule 5: Close with an owner and a date
A meeting that ends without a named owner and a deadline has to happen again. That repeat is the most expensive etiquette failure in this entire article, and it is the one nobody frames as etiquette.
Reserve the last three minutes. Read the actions back out loud, with a name and a date attached to each one. Then send them in writing the same day, because the version people remember is the written one. A meeting minutes template is enough structure for most teams.
The basics that are still non-negotiable
These do not need a policy discussion. They need doing.
- Test your microphone, camera, and connection a few minutes early rather than in the first ninety seconds of the call.
- Mute by default. A headset in any shared space, always.
- Join on time and end on time. Running over is a decision to spend other people's calendars.
- Look at the camera when you are the one speaking, not at your own thumbnail.
- Close the tabs that generate notifications. Screen sharing has published more private messages than any other feature in the category.
- Frame yourself with the light in front of you rather than behind. A window at your back is why you look like a witness in silhouette.
If you want a fuller comparison of what the platforms themselves handle, meetergo has a rundown of video conferencing tools.
Common mistakes
- Writing an etiquette policy nobody can find. A rule living in one manager's head is not a rule, it is a preference people get punished for missing. One page, linked in the onboarding doc.
- Treating camera-off as a performance signal. It is the single fastest way to convert a reasonable accommodation into a grievance, and it is usually wrong about who is paying attention.
- Disclosing a recording after it started. Retroactive disclosure is not consent, and in some jurisdictions it is not legal either.
- Applying internal norms to external calls. Your team may be relaxed about bots and cameras. A client, a candidate, or a regulator's counsel has not agreed to any of it.
- Inviting people to meetings as insurance. Adding six optional attendees so nobody feels excluded produces six people who cannot leave. Send them the notes instead.
Where tools help, and where they don't
Tools fix the mechanical half of this well and the social half not at all. No product will decide your camera policy for you.
What they do handle: booking without the email chain, reminders that cut no-shows, transcripts that survive the call, and a video room that needs no download from the person you invited. meetergo covers those in one place, with a browser-based video meeting room that includes waiting rooms and end-to-end encryption, automated email and SMS reminders, and local AI notes. There is a free forever plan, paid tiers from €9.90 per month, and the full app bundle at €29.90 per month on meetergo's pricing page.
Two honest limits. Cloud recording and transcripts inside the video product are still marked as coming soon, so if you need server-side recording today this is not the tool for it. And the local notes app runs on macOS and Windows only, capturing calls you are personally in rather than acting as an organisation-wide recording layer.
Neither of those is a reason to skip the policy work. A team with clear rules and mediocre tools outperforms a team with excellent tools and no agreement about when to use them.
Try meetergo free and send your next meeting a booking link instead of an email chain.
Booking + video conferencing in one tool.
Booking + video conferencing in one tool.
Frequently asked questions
Is it rude to keep your camera off in a virtual meeting?
Not by itself. It becomes a problem only when the team has a stated expectation and you ignore it without a word. If no default exists, camera-off is a neutral choice and anyone reading it as disrespect is filling in a gap the organisation left open.
Do you need consent to use an AI notetaker?
Assume yes and disclose every time. US states differ on whether one party or all parties must agree, and EU participants add GDPR obligations covering the personal data in a transcript. External calls frequently span more than one set of rules, which makes disclosure the only reliable default.
What is the 40/20/40 rule for meetings?
It splits meeting effort across three phases: 40% preparation, 20% the meeting itself, and 40% follow-up. The useful part is the proportion. Most teams invert it, spending nearly everything on the live call and little on the agenda or the follow-up.
How long should a virtual meeting be?
Shorter than the calendar's default. Tools offer 30 and 60 minutes because those are round numbers, not because they are the right lengths. Try 25 and 50 to build in a gap, and cut anything that could have been a written update.
Should you eat during a video call?
On a large listening-only call with your camera off, nobody minds. On a small call where you are contributing, or any external call, it reads as inattention regardless of intent.
What should you avoid saying at the start of a virtual meeting?
Skip "can everyone hear me?" as a greeting and check your audio before you join. Also skip narrating lateness. Starting with two minutes of apology spends the time you were late by a second time.
Who is responsible for virtual meeting etiquette, the host or the attendees?
The host sets and enforces the rules; attendees follow them. Most etiquette failures are host failures wearing a different label: no agenda, no time discipline, no stated camera policy, no disclosure about recording.
