--- title: "Video 101: calls and meetings as a business channel" summary: "How live video reaches customers through a link or inside your own site and app, where businesses use it from support to telehealth and video identity checks, what it costs, and the rules for recording." canonical: https://cpaas.co/en/learn/video-101 kind: explainer depth: foundation origin: original published: 2026-10-13T16:26:18.899Z updated: 2026-10-14T16:26:19.880Z topics: ["Voice & Video", "Customer Experience", "Fundamentals"] language: en --- # Video 101: calls and meetings as a business channel ## At a glance Video is the business channel where people see each other live: a doctor and a patient, a bank officer and a new customer, a support agent and a broken appliance. It comes in two shapes. **Embedded video** runs inside your own website or app. A **meeting link** opens a call in a meeting product that someone else runs. As of October 2026, both mostly rest on [WebRTC](/en/learn/glossary#webrtc), the open standard for live audio and video built into modern browsers.[^1][^2] ```diagram:compare | Embedded video | Meeting link What it is | A call inside your own site or app | A link that opens a meeting product Who runs it | You, on a video platform or your own servers | The meeting product's owner What the customer needs | A browser or your app, often no account | A browser or the meeting app Who starts it | Either side, usually from a booking or a button | Whoever sends the link How it is priced | Per participant-minute, recording extra | Usually per host seat, or inside a workplace suite Best for | Consultations, identity checks, support that needs to see | Sales demos, business meetings, interviews Avoid for | Quick questions that text answers faster | Anything that must stay inside your brand and your records > As of October 2026. Prices and plans vary by provider; see What it costs. ``` In one line: video is the richest channel and the most demanding. It needs a steady connection on both sides, a person's full attention for a few minutes, and a clear rule for recording. It earns its place when a situation needs eyes, not just words. ## How it works A video call is three jobs, done one after another. 1. **Signalling.** The two sides exchange who they are and what they can send, through a server the application provides. 2. **Connecting.** Each device looks for a network path to the other. Most devices sit behind home or office routers that hide their real address, so a small public service called STUN tells each device what its address looks like from outside. Where no direct path exists, a relay called [TURN](/en/learn/glossary#turn) carries the media instead. 3. **Media.** Audio and video flow, encrypted, directly between the devices or through the relay.[^2] WebRTC defines the browser's share of this work: access to the camera and microphone with the user's permission, the connection itself, and encrypted media. It deliberately leaves signalling, rooms, waiting areas and recording to the application.[^1][^2] Beyond a handful of people, a **media server** (often an SFU, a "selective forwarding unit") receives each person's stream and forwards it to the others, so that no phone has to send its video to everyone. ```diagram:path # A customer joins an embedded video consultation Booking or button | The customer taps a link from a reminder or your site | A join request Your signalling server | Checks who may join, then exchanges call details | Connection details STUN and TURN | Find a route through routers and firewalls, or relay the media | A working path Media server | Forwards each stream to the other participants | Encrypted audio and video Agent or clinician | Joins from a desk app or a browser | The call, and a recording if agreed > Signalling, relays and media servers are the parts with a running cost. ``` A **meeting link** follows the same path inside someone else's product: the meeting service runs the signalling and media servers, and the guest opens the link in a browser or in the service's app. Many meeting products and contact-centre platforms also connect to the phone network through [SIP](/en/learn/glossary#sip), so a guest without a camera can dial in by voice. Suites that bundle meetings, calling and chat for staff are usually called [UCaaS](/en/learn/glossary#ucaas); customer-service platforms that add video to calls and chats are called [CCaaS](/en/learn/glossary#ccaas). For the technical detail, read [WebRTC in plain terms](/en/learn/webrtc-in-plain-terms). ## A short history Video calling is older than the web, but it became an everyday business channel in two steps: phones with front cameras, then browsers that could place a call with no plug-in. Apple introduced FaceTime with the iPhone 4 in June 2010, presenting video calling as something that needed no setup.[^6] In May 2011, Microsoft agreed to buy Skype, founded in 2003, for US$8.5 billion.[^7] Google released the real-time engine that came with its purchase of Global IP Solutions as the open-source WebRTC project, and in 2020 marked ten years of that work.[^3] Apple's Safari added WebRTC in June 2017, bringing browser video calls to the iPhone.[^5] The pandemic turned video into a habit. Zoom reported about 10 million daily meeting participants in December 2019 and more than 200 million in March 2020,[^9] then more than 300 million in April 2020.[^10] In January 2021, WebRTC became a W3C Recommendation together with a set of IETF standards;[^4] the Recommendation was most recently updated in March 2025.[^1] Consumer services then consolidated: Microsoft retired Skype on 5 May 2025 and moved its users to Teams Free.[^8] ```diagram:timeline # From phone cameras to a browser standard June 2010 | Apple introduces FaceTime with the iPhone 4 | Video calling with no setup May 2011 | Microsoft agrees to buy Skype | Skype was founded in 2003 June 2017 | Safari adds WebRTC | Browser video reaches the iPhone April 2020 | Zoom reports more than 300 million daily participants | Up from about 10 million in December 2019 January 2021 | WebRTC becomes a W3C Recommendation | Alongside a set of IETF standards March 2025 | WebRTC Recommendation updated; WHIP published by the IETF | Live streaming on the same technology May 2025 | Microsoft retires Skype | Users move to Teams Free ``` ## Where it is used Video is used everywhere, but unevenly, and it follows bandwidth. The ITU estimates that 74% of the world's population was online in 2025, with use ranging from 94% in high-income countries to 23% in low-income ones, and averaging 36% in Africa.[^13] A channel that needs a steady connection at both ends reaches fewer people where connections are thin or expensive. There, a voice call or a message often does the same job. - **Americas.** In the United States, Pew Research Center found in April 2021 that 81% of adults had talked with others by video call since the pandemic began.[^11] Daily use differed sharply by age: 27% of adults aged 18 to 49 made video calls at least daily, against 7% of those aged 65 and older.[^12] - **Europe.** Video is common in bank and trust-service onboarding, where the European identity-proofing standard ETSI TS 119 461 covers remote checks that use a camera.[^17] - **Middle East and Africa.** Saudi Arabia's Ministry of Health runs Seha Virtual Hospital, which Guinness World Records recognised in October 2024 as the largest virtual hospital.[^14] - **Asia-Pacific.** India's national telemedicine service, eSanjeevani, had served more than 10 crore (100 million) patients by February 2023,[^15] and India's central bank allows banks to identify new customers over a live video session.[^16] ```diagram:bars # US adults making video calls daily or more, April 2021 Aged 18 to 49 | 27% | Pew Research Center Aged 65 and older | 7% | Pew Research Center > Source: Pew Research Center, The Internet and the Pandemic, September 2021. ``` The audience matters as much as the region. Younger adults are used to video; older customers may need a link that opens in one tap, with no account and a phone number to call if it fails. ## What businesses use it for Video earns its cost when someone needs to see something, prove something, or build trust face to face. - **Support that needs eyes.** A customer points the phone at a boiler, a router or a damaged parcel, and the agent sees the problem in seconds. See [customer support](/en/ecosystem/use-cases/support) and [when video belongs in support](/en/learn/when-video-belongs-in-support). - **Consultations.** Doctors, therapists, lawyers, tutors and financial advisers meet clients without a trip. See [video consultations and meetings](/en/ecosystem/use-cases/video-calls). - **Identity checks (video KYC).** A regulated firm verifies a new customer during a live session: the person shows an identity document and their face, and an officer or a system checks that they match. India's central bank allows this as a consent-based "video-based customer identification process" (V-CIP), with checks that the person is live and located in India.[^16] ETSI's TS 119 461 covers attended remote identity proofing with a camera and the risk of **injection attacks**, where a recorded or generated video is fed in place of the live camera.[^17] - **Sales and business meetings.** Demos and account reviews, usually by meeting link. See [sales and lead follow-up](/en/ecosystem/use-cases/sales). - **Booking-led services.** Inspections, interviews and classes: the link goes out with the confirmation and the reminder. See [appointment booking](/en/ecosystem/use-cases/booking) and [reminders and fewer no-shows](/en/ecosystem/use-cases/no-shows). - **Contact centres.** An agent upgrades a phone call or a chat to video when words are not enough. See [contact centre](/en/ecosystem/use-cases/contact-center) and the glossary entry for a [contact centre](/en/learn/glossary#contact-centre). ```diagram:matrix # Four situations where video earns its cost Show me the problem | Support that needs to see a device, a damage or a document Prove who you are | Video identity checks for accounts and contracts Meet without travelling | Consultations in health, law, finance and education Close a complex sale | Demos and reviews with the people who decide ``` ## What it costs Video platforms charge per **participant-minute**: each person connected counts for each minute they stay in the call. Recording, storage, transcription and live streaming are usually billed separately. Meeting products are more often sold per host seat per month, with video included. Two official examples, as the platform owners publish them, accessed in October 2026: - **Microsoft Azure Communication Services** prices group calls at US$0.004 per participant per minute, the same for voice, video and screen sharing, and lists mixed audio-and-video recording at US$0.01 per minute. Microsoft notes that its examples are illustrative and may not reflect the latest prices.[^23] - **Amazon Chime SDK** prices its examples at US$0.0017 per attendee-minute, billed in six-second increments, with media capture and live streaming charged on top.[^24] A worked example at the first rate: a 30-minute consultation between two people is 60 participant-minutes, or US$0.24 before any recording. A one-hour team review with six people is 360 participant-minutes. Check the current rate card before you budget, because both pages change. ```diagram:blocks # What adds to a video bill Participant-minutes | Every person, every minute connected Relays | Bandwidth for calls that cannot connect directly Media servers | Needed once a call has more than a few people Recording and storage | Per minute recorded, and per month kept Transcription and AI | Often per minute of audio Phone dial-in | Charged at voice rates ``` If you run video yourself rather than on a platform, the browser parts are free but relays and media servers are not, and support tickets about cameras and microphones are a real cost. See [peer-to-peer video](/en/learn/video-without-a-vendor). ## Rules and regulation Three sets of rules meet in a video call: data protection, recording consent, and the rules of your sector. This is a summary, not legal advice; check the rules where you and your customers are. **Data protection.** A video of a person is personal data. Under the EU's [GDPR](/en/learn/glossary#gdpr), facial images processed to identify someone uniquely are biometric data, a special category that may be processed only under specific exceptions, so a video identity check needs a clear legal basis.[^18] Where media servers and recordings are hosted is a [data residency](/en/learn/glossary#data-residency) question that regulated buyers ask early. **Recording consent.** The UK regulator, the ICO, says organisations may record video calls where they have a valid purpose that less intrusive methods, such as taking minutes, cannot achieve; before recording, they should tell people why, what for and how long the recording will be kept.[^19] In the United States, federal law allows a recording when one party to the conversation consents,[^20] but some states go further: California requires the consent of all parties to record a confidential communication.[^21] Rules elsewhere differ again. A safe default everywhere is to announce recording at the start, show a visible indicator, and let people decline. **Sector rules.** In US healthcare, the temporary flexibility that let providers use everyday video apps during the COVID-19 emergency expired on 11 May 2023, with a transition period to 9 August 2023, so telehealth video must now meet HIPAA rules in full.[^22] In banking, video identity checks follow central-bank rules such as India's V-CIP[^16] and, in Europe, identity-proofing standards such as ETSI TS 119 461.[^17] ```diagram:checklist # Before you press record Purpose | A reason that less intrusive methods cannot meet Notice | Tell people why, for what and for how long, before recording Consent | From everyone on the call where the law or your policy requires it Indicator | A visible sign while the recording runs Storage | Where recordings sit, who can open them, when they are deleted [!] Recording just in case | Hard to justify, and a liability if it leaks ``` ## Limits and pitfalls - **The weakest connection sets the quality.** One participant on a poor mobile signal degrades the call for everyone. Offer an audio-only option and a phone dial-in. - **Delay matters more than sharpness.** People talk over each other when [latency](/en/learn/glossary#latency) grows. Media servers near your users help more than higher resolution; see [latency you can actually feel](/en/learn/latency-you-can-actually-feel). - **Most failures are not the network.** Blocked camera permissions, the wrong microphone and a browser that remembers an old refusal cause most "it doesn't work" calls. - **Strict networks.** Company firewalls can block direct paths, so calls need a TURN relay, which costs bandwidth.[^2] - **Attention.** Video asks both people to stop what they are doing. For a simple question, a message is kinder. - **Faked video.** For identity checks, a camera feed can be replaced by a recording or a generated face; current standards ask for detection of injected streams.[^17] - **Recording sprawl.** Recordings pile up in storage nobody reviews, long after their purpose has passed. - **Accessibility.** Offer captions and a text chat alongside the picture. ## Strengths and weaknesses ```diagram:compare | Strengths | Weaknesses Trust | Face to face, the closest thing to a visit | Feels intrusive for simple questions Showing | The agent sees the problem, the document, the face | Needs light, a camera and a steady hand Reach | Opens from a link in any modern browser | Needs a good connection on both sides Brand | Embedded video stays in your own site and app | Meeting products show their own brand Cost | Cheaper than a visit or a field trip | Grows with every participant and every minute Records | A recording can settle a dispute | Recording brings consent and storage duties ``` ## What comes next Only announced work and published standards are listed here. - **The standard keeps moving.** W3C updated the WebRTC Recommendation in March 2025, and the working group continues to extend it.[^1] - **Live streaming on call technology.** The IETF published WHIP as RFC 9725 in March 2025: a simple way to send WebRTC video into streaming services, so broadcasts can use the same low-delay technology as calls.[^25] - **Consolidation.** Consumer calling keeps folding into workplace suites, as Skype's retirement in favour of Teams Free in 2025 showed.[^8] - **Defences against faked video.** Version 2 of ETSI TS 119 461, published in February 2025, defines detection of injection attacks for remote identity proofing.[^17] ## When to choose it ```diagram:decision # Is video right for this moment? Is it a regulated identity check? | Use video, under your regulator's rules | Does someone need to see a thing, a document or a face? | | Text or voice will be faster Do both sides have a steady connection and a few free minutes? | | Start with voice; offer video if the line holds Does the call follow a booking? | Send the link with the confirmation and the reminder | Offer a call button where the customer already is ``` - **By need.** Choose video for consultations, inspections, identity checks and support that must see; avoid it for status questions, codes and alerts. - **By location.** Where connectivity is strong, video can be the default for consultations; where it is thin or costly, lead with voice and keep video optional.[^13] - **By audience.** For business buyers, a meeting link is normal. For consumers, embedded video that opens in one tap, with no account, is easier, especially for older customers.[^12] See the [video channel page](/en/ecosystem/channels/video) for providers, [Voice 101](/en/learn/voice-101) for when a phone call is enough, and [which channel for which need](/en/learn/which-channel-for-what) to compare video with every other channel. ## Sources [^1]: [WebRTC: Real-Time Communication in Browsers](https://www.w3.org/TR/webrtc/) — W3C, 13 March 2025 [^2]: [RFC 8825: Overview: Real-Time Protocols for Browser-Based Applications](https://datatracker.ietf.org/doc/html/rfc8825) — IETF, January 2021 [^3]: [Celebrating 10 years of WebM and WebRTC](https://opensource.googleblog.com/2020/05/celebrating-10-years-of-webm-and-webrtc.html) — Google Open Source Blog, May 2020 [^4]: [Web Real-Time Communications (WebRTC) transforms the communications landscape; becomes a W3C Recommendation and multiple IETF standards](https://www.w3.org/2021/01/pressrelease-webrtc-rec.html.en) — W3C, 26 January 2021 [^5]: [Announcing WebRTC and Media Capture](https://webkit.org/blog/7726/announcing-webrtc-and-media-capture/) — WebKit, 7 June 2017 [^6]: [Apple Presents iPhone 4](https://www.apple.com/newsroom/2010/06/07Apple-Presents-iPhone-4/) — Apple Newsroom, 7 June 2010 [^7]: [Microsoft to Acquire Skype](https://news.microsoft.com/source/2011/05/10/microsoft-to-acquire-skype-3/) — Microsoft, 10 May 2011 [^8]: [Skype is retiring in May 2025: What you need to know](https://support.microsoft.com/en-us/skype/skype-is-retiring-in-may-2025-what-you-need-to-know) — Microsoft Support, accessed 2026-10 [^9]: [A Message to Our Users](https://blog.zoom.us/a-message-to-our-users/) — Zoom, 1 April 2020 [^10]: [Zoom Q1 FY21 earnings: prepared remarks](https://investors.zoom.us/static-files/cb76de11-5579-4d09-94b0-a61344d410d6) — Zoom Video Communications, June 2020 [^11]: [The Internet and the Pandemic](https://www.pewresearch.org/internet/2021/09/01/the-internet-and-the-pandemic/) — Pew Research Center, 1 September 2021 [^12]: [How the internet and technology shaped Americans' personal experiences amid COVID-19](https://www.pewresearch.org/internet/2021/09/01/how-the-internet-and-technology-shaped-americans-personal-experiences-amid-covid-19/) — Pew Research Center, 1 September 2021 [^13]: [Facts and Figures 2025](https://www.itu.int/itu-d/reports/statistics/facts-figures-2025/) — ITU, November 2025 [^14]: [Seha Virtual Hospital Receives Guinness World Record as Largest Virtual Hospital During Global Health Exhibition](https://www.spa.gov.sa/en/N2192705) — Saudi Press Agency, October 2024 [^15]: [Union Health Minister hails the eSanjeevani milestone of providing telemedicine services to more than 10 crore patients](https://pib.gov.in/PressReleseDetailm.aspx?PRID=1899855) — Press Information Bureau, Government of India, February 2023 [^16]: [Master Direction – Know Your Customer (KYC) Direction, 2016](https://www.rbi.org.in/commonman/english/scripts/notification.aspx?id=2607) — Reserve Bank of India, accessed 2026-10 [^17]: [ETSI TS 119 461 V2.1.1: Policy and security requirements for trust service components providing identity proofing of trust service subjects](https://www.etsi.org/deliver/etsi_ts/119400_119499/119461/02.01.01_60/ts_119461v020101p.pdf) — ETSI, February 2025 [^18]: [Regulation (EU) 2016/679 (General Data Protection Regulation)](https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng) — EUR-Lex, 27 April 2016 [^19]: [Data sharing advice (advice for small organisations)](https://ico.org.uk/for-organisations/advice-for-small-organisations/information-security/data-sharing-advice/) — Information Commissioner's Office (ICO), accessed 2026-10 [^20]: [18 U.S. Code § 2511: Interception and disclosure of wire, oral, or electronic communications prohibited](https://www.law.cornell.edu/uscode/text/18/2511) — Legal Information Institute, Cornell Law School, accessed 2026-10 [^21]: [California Penal Code § 632](https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=PEN§ionNum=632) — California Legislative Information, accessed 2026-10 [^22]: [HHS Office for Civil Rights announces the expiration of COVID-19 public health emergency HIPAA notifications of enforcement discretion](https://www.hhs.gov/about/news/2023/04/11/hhs-office-for-civil-rights-announces-expiration-covid-19-public-health-emergency-hipaa-notifications-enforcement-discretion.html) — U.S. Department of Health and Human Services, 11 April 2023 [^23]: [Pricing scenarios for Calling (Voice/Video) and Chat](https://learn.microsoft.com/en-us/azure/communication-services/concepts/pricing) — Microsoft Learn, accessed 2026-10 [^24]: [Amazon Chime SDK pricing](https://aws.amazon.com/chime/chime-sdk/pricing/) — Amazon Web Services, accessed 2026-10 [^25]: [RFC 9725: WebRTC-HTTP Ingestion Protocol (WHIP)](https://www.rfc-editor.org/rfc/rfc9725.html) — IETF / RFC Editor, March 2025 --- Published by the company behind five products in this category. Those products appear in this site's directory alongside competitors under the same published criteria and are labelled as its own. Editorial content does not recommend them.