Video meetings

What this shelf covers

Calls with other people, and what remains afterwards: group meetings, one-to-one calls, screen sharing, recording and the notes a model now writes for you.

Most organisations already have a meeting tool bundled with something else. The reason to look at this category is usually a specific irritation: quality, joining friction, recording limits, or notes nobody takes.

Webinars with registration belong in events and webinars. Day-to-day chat sits in team communication.

Joining is the feature people judge you on

Every meeting product works when everything is configured. The difference shows in the first ninety seconds with an outside participant.

Browser joining without an install is now the baseline, and it matters most on locked-down corporate laptops where installing anything is impossible. Test that path specifically, with a colleague at another company, before deciding.

Then check the ordinary friction: whether a guest needs an account, how a phone dial-in works when the connection fails, and whether the link changes when a meeting is rescheduled. Those three cause most late starts.

Quality, and what happens on a bad connection

Marketing pages show ideal conditions. Real calls happen on hotel networks and mobile connections.

Ask how the product degrades. Good ones reduce video quality and protect audio. Weaker ones stutter both, and a call where half the sentences are lost is worse than a phone conversation.

Bandwidth handling, echo cancellation and background noise suppression are where the engineering difference actually lives. Test with somebody in a noisy room rather than in a quiet office.

Recording, transcripts and automatic notes

• Cloud recording with a storage allowance and a retention limit.
• Transcripts, searchable and usually editable.
• Summaries and action items, generated automatically after the call.
• Speaker separation, which decides whether a transcript is readable.
• Sharing controls, since recordings contain more than the participants expect.

Automatic notes have improved to the point of being useful and are still wrong often enough to need a check. They handle structure well and misplace names, figures and anything said over someone else. Treat the output as a draft the meeting owner corrects.

Recording carries legal weight. Consent rules differ by country and sometimes within one, so announce it, keep the indicator visible, and decide who may access the archive afterwards.

Fitting into the working day

The calendar connection matters more than any in-call feature.

Look at how meetings are created from your calendar, whether the link is stable, and how a room resource is booked alongside it. Then look at what happens afterwards: whether notes reach the place your team actually reads, and whether a recording can be attached to a customer record without a manual upload.

Meeting rooms with hardware are a separate purchase and a separate headache. If that applies, check certified devices rather than assuming compatibility.

How plans are structured

Per host per month is the norm, with participant caps, meeting length, recording storage and administration features setting the tiers.

Free plans are generous and limited in one specific way, usually a forty to sixty minute ceiling on group calls. That limit, rather than any feature, is what drives most upgrades.

Watch storage for recordings, which fills faster than expected, and check whether webinar capability is a separate product rather than a higher plan. The same pattern of quiet meters across categories appears in what pricing pages hide.

Which product suits which team

A team already paying for a productivity suite usually has a meeting tool included, and the honest starting position is to use it until something specific hurts.

Sales and customer-facing teams outgrow bundled tools first, because they need recording, notes reaching the customer record, and guests who join without friction from any company.

Distributed teams care most about connection quality and about what the product does when the network is poor. That is worth testing from the worst connection anyone on the team has, rather than from the office.

Regulated organisations look at retention, access to recordings and where the data is processed before anything else, and those questions frequently narrow the list to two products before quality is even discussed.

Small teams with occasional external calls are usually best served by whichever tool their counterparts already use, since the person joining should never have to install anything to talk to you.