Module 07 · Video Messages
Ten minutes recorded beats thirty in a call.
Async video messages for teams, sold to companies across the United States as part of the Vebex platform. Record from the browser or the phone app, cut the first fumbling twenty seconds off, and drop the clip into the thread where the work already lives. No link to schedule. No calendar tetris across four time zones.
What async video messages cost.
A video message is a recording of your camera, your screen, or both at once, capped at ten minutes. You press record, you talk, you stop. Before it sends you get a trim bar: pull the left handle past the throat-clearing, pull the right handle in before you start saying goodbye twice. Then it posts into a Team Chat channel or a direct thread as a playable card with a shareable link.
There is no separate line item for it. Every host licence carries video messages, and so does every member seat in a workspace that has at least one host. The part that can cost money is storage, and only if you decide to keep clips past the workspace retention window. Kept clips sit in the same pool as meeting recordings and are billed on the same basis: per GB of retained storage, per month. At 720p a ten-minute clip is around 50 MB. At 1080p it is around 100 MB. A team sending forty clips a month at 1080p adds roughly 4 GB, and at the default 30-day retention it never grows past that.
We do not publish a rate card on this site. You tell us hosts, largest meeting and retention, we send a written proposal with the number in it, monthly first. If you want the arithmetic before you talk to anyone, the configurator runs it in front of you.
The specification, without the adjectives.
| Maximum clip length | 10 minutes. The recorder stops itself and keeps what it has. |
|---|---|
| Capture modes | Camera only, screen only, or screen with a camera bubble in the corner that you can drag. |
| Recording quality | 720p or 1080p, chosen per workspace |
| Storage per clip | ~50 MB at 720p / ~100 MB at 1080p for a full ten minutes |
| Trimming | In the browser, before the upload finishes. Trim points are applied server-side, so the discarded ends are never stored. |
| Where it lands | A Team Chat channel, a direct thread, or a link you paste anywhere. |
| Playback | 1x, 1.25x, 1.5x, 2x |
| Transcript | Available when the workspace has Recording and Transcripts. Without that module the clip plays, and that is all. |
| Retention | 7 / 30 / 90 / 365 days, set per workspace |
| Guest viewing | A link can be opened by someone outside the workspace if an admin allows external links. Off by default. |
| Price basis | Included with any host licence; retained storage per GB per month |
Four meetings that should have been clips.
The status update where one person talks and eleven listen. The design walkthrough that only needs comments, not debate. The Monday handover between a team in Austin and a team eight hours ahead, which currently happens at 7am for somebody. The bug report that takes four paragraphs to write and nineteen seconds to show.
Those four are the ones we see most. The pattern is the same: a meeting booked because there was no other way to put a face and a screen in front of people. A clip does that for a fraction of the time and none of the calendar.
What a clip is bad at is disagreement. If two people need to argue toward a decision, send them to a meeting. Recording a ten-minute monologue at someone who disagrees with you is a way to be ignored politely.
How a clip gets made and read.
Press record, inside the thread
The recorder opens where you are: in a channel, under a message, or from the app's menu bar. Browser capture uses the camera and microphone permissions the browser already holds, so the first time you do it there is one permission prompt and never again. On the phone app the recorder is a full-screen camera with a countdown of three.
Trim before it sends
The trim bar appears as soon as you stop. Most people cut six to fifteen seconds off the front. You can also re-record without sending; nothing leaves the device until you choose to send it, and a discarded take is dropped from the browser buffer rather than uploaded and deleted later.
Post it where the work is
The clip becomes a card in the thread with its length on the face of it, so people can decide whether they have three minutes now or at lunch. Replies thread underneath as text, as another clip, or as a call button if the conversation turns out to need one after all. That button is Team Chat; it lifts the same thread into a live meeting without anyone sending a link.
It ages out on your schedule
Retention is a workspace setting, not a per-clip decision, because per-clip decisions never get made. At 30 days a clip and its transcript are deleted together. An admin can pin specific clips so retention skips them, and the audit log in the admin console records who pinned what. Storage held beyond the window is what the per-GB basis is measuring.
Fair questions before you buy anything.
Teams of four who sit in one room. You do not need async video to talk to someone eleven feet away, and we are not going to pretend otherwise. It also does not suit work that is legally required to happen in a live, minuted session, and it is a poor fit for anything confidential enough that a link sitting in a thread for 30 days is a problem. In that last case, set retention to 7 days and turn external links off.
You see that a clip was viewed and by whom. You do not see a watch-completion percentage, a heatmap, or a list of people who skipped to the end, because that is attendee tracking wearing a different coat. We do not build it. If a vendor is selling you engagement scoring on internal video, ask what they do with the same data in meetings.
Not at the default. Forty clips a month at 1080p is about 4 GB, and with 30-day retention the pool holds steady instead of growing. Storage becomes a real number when a workspace sets 365-day retention and records meetings as well. Run both through the configurator and you will see the held figure before anyone quotes you.
No. You trim the ends and that is the whole editor. We are not writing a video editor inside a meetings product; if you need titles and cuts, record the clip elsewhere and post the file into the thread. Being honest about this saves you finding out in month two.
Yes. A clip finishing fires the same event stream as a finished recording, and the REST endpoints return the playback URL and duration. That is covered on the integrations and API page, including the webhook payload.
Ask for a proposal.
Tell us how many people would send clips and what your largest meeting of the month looks like. We reply with a written proposal, monthly terms first, within one working day.