--- title: "Web chat & booking page 101: help where visitors decide" summary: "Web chat is a conversation window on your own website, answered by people, a bot, an AI agent or a mix; a booking page lets visitors pick a time without a phone call. Both meet people at the moment they decide, and both come with duties: telling people when a bot answers, accessibility, cookie consent and keeping transcripts no longer than needed." canonical: https://cpaas.co/en/learn/webchat-101 kind: explainer depth: foundation origin: original published: 2026-10-13T16:26:18.899Z updated: 2026-10-14T16:26:19.868Z topics: ["Messaging", "Customer Experience", "AI", "Fundamentals"] language: en --- # Web chat & booking page 101: help where visitors decide ## At a glance Web chat is a conversation window on your own website: a button, usually in a corner, that opens a chat answered by people, a [chatbot](/en/learn/glossary#chatbot), an [AI agent](/en/learn/glossary#ai-agent) or a mix. A booking page is its close relative: a page where a visitor picks a free time and gets a confirmation, without a phone call. Both meet visitors at the moment they are deciding. - **What it is:** a chat widget (a small piece of code added to your pages) and, often, a booking page linked from your site, your messages and your profiles. - **Who runs it:** you, usually with a provider's widget and agent inbox. No network owner sits in between. - **Reach:** anyone who visits your site. The ITU counted about 6 billion internet users in 2025, 74% of the world's population.[^1] - **Who may start the conversation:** the visitor, or the business through a prompt shown while the visitor is on the page. - **How it is priced:** usually per agent seat a month; bots and AI agents increasingly per conversation or per resolution. - **Best for:** questions before a purchase, help while the visitor is on the site, and booking appointments. - **Avoid for:** anything that must reach the person after they leave, unless you continue on another channel. - **As of:** October 2026. ```diagram:compare | Live chat (people) | Bot or AI agent | Booking page Who answers | Your team, in an agent inbox | Software, working from your content and rules | Nobody: the visitor picks a time Hours | When staff are on shift | Around the clock | Around the clock Best for | Complex or sensitive questions | Common questions and simple tasks | Appointments, demos and consultations Main risk | Queues and empty hours | Wrong answers and no way to reach a person | Double bookings and no-shows > Three entry points on your own website. Many sites combine them. ``` ## How it works The widget is a script added to your pages. It draws the chat button and window, opens a connection to the provider's service, usually a WebSocket so that messages flow both ways at once,[^3] and recognises the visitor from page to page with a cookie or browser storage. Each conversation lands in an agent inbox, often a [unified inbox](/en/learn/glossary#unified-inbox) that also holds email and chat-app messages. A bot or AI agent may answer first and hand over to a person when it cannot help, passing on what was already said. ```diagram:path # The path of one web chat Visitor's browser | The widget loads and the visitor types a question | The message, with page and session details Chat service | Stores it and routes it: bot first, or straight to a queue | The conversation, with any customer record Bot or AI agent | Answers from approved content, or decides to hand over | A reply, or a handover with a summary Agent inbox | A person picks it up within the promised time | A reply to the visitor; the transcript is kept ``` A booking page works the other way round. It reads free times from the staff calendar, lets the visitor choose one, writes the appointment back and sends a confirmation. The confirmation usually carries a calendar file in iCalendar, the IETF format for events and free/busy information (RFC 5545, September 2009),[^22] and invitations sent by email follow iMIP (RFC 6047), the standard way to carry calendar requests and replies in email so the recipient's calendar can accept, decline or update the event.[^23] Reminders before the appointment reduce [no-shows](/en/ecosystem/use-cases/no-shows). Speed is part of the product. Set a response time you can keep, a service level or [SLA](/en/learn/glossary#sla), and show it; when nobody is available, say so and offer another way to get help. ## A short history Live chat on websites is nearly as old as online shopping. LivePerson, one of the first companies in the field, was incorporated in 1995 and introduced its chat service in November 1998.[^2] Early widgets asked the server every few seconds for new messages; the WebSocket standard of December 2011 gave browsers one always-open, two-way connection.[^3] Bots arrived in force in April 2016, when Facebook opened its Messenger Platform to bots at its F8 conference.[^4] Many of the same tools moved into website widgets, but most early bots followed fixed scripts. OpenAI's release of ChatGPT on 30 November 2022 put a conversational AI model in front of the public,[^5] and since then web chat providers have added generative-AI agents that answer from a company's own content. The rules followed. California's bot disclosure law took effect in July 2019.[^13] WCAG 2.2 became a W3C Recommendation on 5 October 2023,[^6] the European Accessibility Act began to apply on 28 June 2025,[^11] and Article 50 of the EU AI Act, which requires telling people when they are dealing with AI, has applied since 2 August 2026.[^14] ```diagram:timeline # From chat buttons to AI agents November 1998 | LivePerson introduces its chat service | Live chat for websites December 2011 | RFC 6455 standardises WebSocket | Two-way messages without constant polling April 2016 | Bots on the Messenger Platform | Automated conversations go mainstream July 2019 | California's bot disclosure law takes effect | Bots must not pose as people to sell November 2022 | ChatGPT released | Generative AI in conversation October 2023 | WCAG 2.2 published | Consistent help and visible focus June 2025 | European Accessibility Act applies | E-commerce and banking sites covered August 2026 | EU AI Act Article 50 applies | People must be told when they talk to AI ``` ## Where it is used Web chat works wherever people use the web, so internet use sets its reach. The ITU, the UN agency for digital technologies, reports that 74% of the world's population, about 6 billion people, used the internet in 2025, up from 71% a year earlier. Use is near universal in high-income countries, at 94%, but reaches only 23% of people in low-income countries and 36% across Africa.[^1] ```diagram:bars # People using the internet in 2025 (% of population) High-income countries | 94 | Near universal World | 74 | About 6 billion people Africa | 36 | Regional average Low-income countries | 23 | Most people still offline > ITU, Facts and Figures 2025. ``` Where visitors browse mostly on phones and on slower connections, a light widget and a booking page that works on a small screen matter more than features. The rules differ by region: - **Americas:** California requires bots not to mislead people about being bots when selling,[^13] US state and local governments must make their websites and apps accessible under a 2024 federal rule,[^12][^9] and a Canadian tribunal held an airline responsible for its chatbot's wrong answer.[^18] - **Europe:** the AI Act's disclosure duty,[^14][^15] consent for storing data on the visitor's device,[^16] the GDPR for transcripts,[^17] and the European Accessibility Act for e-commerce and banking sites.[^11] - **Middle East and Africa:** the UAE's and Saudi Arabia's data protection laws set conditions for sending personal data, such as transcripts, abroad.[^24][^25] ## What businesses use it for - **[Sales](/en/ecosystem/use-cases/sales):** answering questions on product and pricing pages and capturing leads, asking for contact details only when they are needed. - **[Support](/en/ecosystem/use-cases/support):** help on account and help pages, with the visitor's question and page already in front of the agent. - **[Booking](/en/ecosystem/use-cases/booking):** appointments, demos, viewings and consultations, with confirmations and reminders that reduce [no-shows](/en/ecosystem/use-cases/no-shows). - **[Chatbots](/en/ecosystem/use-cases/chatbot) and AI agents:** answers to common questions outside office hours, with a handover to a person. - **[Unify](/en/ecosystem/use-cases/unify):** continuing the same conversation by email, WhatsApp or SMS after the visitor leaves, with their permission. - **[Video calls](/en/ecosystem/use-cases/video-calls):** moving a chat to a meeting link when seeing the problem is faster than describing it. ## What it costs The common pricing models are: - **Per agent seat a month,** the usual model for live chat and help-desk software, in tiers by feature. - **Limits on conversations or monthly active visitors** in some plans, with charges above the limit. - **Per conversation or per resolution** for bots and AI agents: you pay when the AI handles a conversation, or only when it resolves one. - **Booking pages,** often priced per user who has a calendar, or included in a wider plan. As one official example, Intercom lists its Fin AI agent at US$0.99 per "outcome". An outcome is counted when a customer confirms the issue is resolved, when they ask for no further help after the answer, or when the agent completes a workflow, including a handover to a person; each conversation is billed at most once, and seats on Intercom's own help desk are billed separately, as listed in October 2026.[^21] The definition matters as much as the price: a conversation the bot kept away from people is not always one it resolved. See [AI agents and the containment trap](/en/learn/ai-agents-and-the-containment-trap) and the glossary entry on [containment](/en/learn/glossary#containment). The hidden costs are staff for the hours the button is shown, keeping the AI's content accurate, page speed and accessibility testing. ## Rules and regulation This section describes the rules in plain words; it is not legal advice. ### Telling people they are talking to a bot - **California:** SB 1001 makes it unlawful to use a bot to communicate with a person in California online with the intent to mislead them about its artificial identity, in order to encourage a purchase or sale or to influence a vote. A clear and conspicuous disclosure that it is a bot avoids liability.[^13] - **European Union:** from 2 August 2026, providers must design AI systems that interact directly with people so that those people are told they are dealing with AI, unless it is obvious.[^14] The Commission's July 2026 guidelines keep the "obvious" exception narrow and say that terms and conditions alone are not enough, nor are invisible markings such as metadata.[^15] See [disclosing AI in a conversation](/en/learn/disclosing-ai-in-a-conversation) and [AI Act Article 50 for messaging](/en/learn/ai-act-article-50-for-messaging). - **Responsibility for answers:** in Moffatt v. Air Canada (2024), a British Columbia tribunal rejected the airline's argument that its chatbot was responsible for its own statements and found the airline liable for negligent misrepresentation.[^18] ```diagram:compare | California (SB 1001) | European Union (AI Act Article 50) In force | July 2019 | 2 August 2026 What it covers | Bots used to mislead people in California, to sell or to sway a vote | AI systems that interact directly with people What to do | Disclose clearly and conspicuously that it is a bot | Tell people they are dealing with AI, unless it is obvious What is not enough | A notice nobody can see or understand | Terms and conditions alone, or invisible markings ``` ### Cookies, storage and transcripts A widget usually stores an identifier on the visitor's device. In the EU, Article 5(3) of the ePrivacy Directive governs storing and reading information on a user's device; the European Data Protection Board's Guidelines 2/2023 confirm that it covers browser local storage and tracking pixels, not only cookies.[^16] Ask which parts of your widget need consent and load the rest only after it is given. Transcripts are personal data: under the [GDPR](/en/learn/glossary#gdpr) they may be kept no longer than their purpose needs, with time limits for erasure or review.[^17] The UAE's data protection law, in force since 2 January 2022, sets cross-border conditions,[^24] and Saudi Arabia's law reaches processing of residents' data by parties outside the Kingdom and regulates transfers abroad;[^25] check where your provider stores transcripts ([data residency](/en/learn/glossary#data-residency)). ### Accessibility WCAG 2.2, the W3C's accessibility guidelines, adds "Consistent Help": a help mechanism such as a chat or chatbot that repeats across pages must appear in the same relative order. The W3C's guidance adds that chatbots help many people if they recognise misspelled words, give human contact details after three failed attempts, and can be closed in one action and reopened from a link or button.[^6][^7] "Focus Not Obscured" requires that sticky content, such as a fixed footer or a non-modal window, does not entirely hide the element that has keyboard focus.[^8] A chat log can be marked with the ARIA role "log" so screen readers announce new messages.[^10] The European Accessibility Act has applied since 28 June 2025 to services such as e-commerce and banking.[^11] In the United States, a 2024 Justice Department rule adopts WCAG 2.1 Level AA for state and local government websites and apps,[^12] and an interim rule in 2026 extended its compliance dates.[^9] ```diagram:checklist # What an accessible chat widget does Same place on every page | WCAG 2.2 Consistent Help Never hides the focused element | WCAG 2.2 Focus Not Obscured Announces new messages | A live region such as the ARIA log role Closes in one action and reopens from a button | W3C advice for chatbots Offers a person after three failed attempts | W3C advice for chatbots [!] A widget that covers the page on phones | Hides content and keyboard focus ``` ## Limits and pitfalls - **The conversation ends when the tab closes.** Ask for permission to continue by email or a chat app, and record it: [consent is a data model](/en/learn/consent-is-a-data-model). - **A button with nobody behind it.** Showing "chat with us" when no person or bot can help is worse than a contact form with honest hours. - **Questions before answers.** Asking for name, email and phone before answering a simple question drives visitors away. - **Bots that trap people.** In a Gartner survey published in August 2026, 87% of customers said companies using generative AI for service must offer access to a human agent.[^19] - **Wrong answers are yours.** A tribunal held Air Canada liable for what its chatbot said.[^18] Keep the AI's sources approved and current. - **Page weight and layout.** Chat scripts add to page load, and on phones a widget can cover content and the focused element.[^8] - **Booking clashes.** Without a live link to the real calendar you get double bookings; mind time zones and send reminders. - **Arabic.** The widget must work right to left, and bots must understand Arabic as people type it; see [Arabic-first is not translation](/en/learn/arabic-first-is-not-translation). ## Strengths and weaknesses ```diagram:compare | Strengths | Weaknesses Timing | Help at the moment a visitor is deciding | Ends when the visitor leaves the page Control | Your look, your data, no app to install | Accessibility, speed and consent are your job Automation | Bots and AI agents answer around the clock | Wrong answers and dead ends hurt trust Booking | Appointments without a phone call | Needs a real calendar link and reminders Cost | Seats and usage you can plan | Per-resolution prices depend on definitions ``` ## What comes next - **AI disclosure is now law in the EU.** Article 50 has applied since 2 August 2026, and the Commission published guidelines on it in July 2026.[^14][^15] - **More automation, attributed.** Gartner predicts that by 2029 agentic AI will autonomously resolve 80% of common customer service issues without human intervention, leading to a 30% reduction in operational costs.[^20] - **A human option stays expected.** In the same research firm's 2026 survey, 87% of customers said a route to a human agent is essential, and Gartner advised against making generative AI a mandatory first step.[^19] - **US public-sector accessibility.** State and local governments now work to the compliance dates set by the 2026 interim rule.[^9] ## When to choose it ```diagram:decision # Is web chat or a booking page the right entry point? Do people come to your website before they buy or book? | | Meet them where they are: a chat app, email or the phone Do most of them simply want a time slot? | Offer a booking page, with confirmations and reminders | Can you staff the hours the button is shown, or answer reliably with a bot? | Offer web chat, with a clear route to a person | Show a contact form and the hours when people are available ``` Choose web chat when visitors decide on your website and a quick answer helps them decide, and a booking page when what they want is a time with a person. Plan the follow-up from the start: [email](/en/learn/email-101) for the confirmation and record, and a chat app or SMS for reminders, each with the visitor's permission. For customers who already use your app, [in-app chat](/en/learn/in-app-101) does the same job inside your product. The [web chat channel page](/en/ecosystem/channels/webchat) lists providers; [the support queue as a system](/en/learn/the-support-queue-as-a-system) covers staffing and routing, [measuring a conversational programme](/en/learn/measuring-a-conversational-programme) covers what to count, and [which channel for which need](/en/learn/which-channel-for-what) compares web chat with every other channel. ## Sources [^1]: [Facts and Figures 2025](https://www.itu.int/en/mediacentre/Pages/PR-2025-11-17-Facts-and-Figures.aspx) — International Telecommunication Union (ITU), 2025-11-17 [^2]: [LivePerson, Inc. Annual Report (Form 10-K) for fiscal year 2009](https://www.sec.gov/Archives/edgar/data/1102993/000114420410012703/v176825_10k.htm) — US Securities and Exchange Commission (EDGAR), 2010 [^3]: [RFC 6455: The WebSocket Protocol](https://www.rfc-editor.org/info/rfc6455/) — IETF / RFC Editor, 2011-12 [^4]: [Messenger Platform at F8](https://about.fb.com/news/2016/04/messenger-platform-at-f8/) — Meta Newsroom, 2016-04-12 [^5]: [Introducing ChatGPT](https://openai.com/index/chatgpt/) — OpenAI, 2022-11-30 [^6]: [WCAG 2.2 is a Web Standard "W3C Recommendation"](https://www.w3.org/WAI/news/2023-10-05/wcag22rec/) — W3C Web Accessibility Initiative, 2023-10-05 [^7]: [Understanding Success Criterion 3.2.6: Consistent Help](https://www.w3.org/WAI/WCAG22/Understanding/consistent-help.html) — W3C Web Accessibility Initiative, accessed 2026-10 [^8]: [Understanding Success Criterion 2.4.11: Focus Not Obscured (Minimum)](https://www.w3.org/WAI/WCAG22/Understanding/focus-not-obscured-minimum.html) — W3C Web Accessibility Initiative, accessed 2026-10 [^9]: [28 CFR Part 35: interim final rule extending the compliance dates for web content and mobile app accessibility](https://www.ada.gov/assets/pdfs/2026-ifr.pdf) — US Department of Justice (ADA.gov), 2026 [^10]: [ARIA23: Using role=log to identify sequential information updates](https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA23) — W3C Web Accessibility Initiative, accessed 2026-10 [^11]: [European Accessibility Act (EAA)](https://commission.europa.eu/strategy-and-policy/policies/justice-and-fundamental-rights/disability/european-accessibility-act-eaa_en) — European Commission, accessed 2026-10 [^12]: [Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps Provided by State and Local Governments](https://www.ada.gov/resources/2024-03-08-web-rule/) — US Department of Justice (ADA.gov), accessed 2026-10 [^13]: [SB-1001 Bots: disclosure (bill text)](https://leginfo.legislature.ca.gov/faces/billTextClient.xhtml?bill_id=201720180SB1001) — California Legislative Information, 2018-09-28 [^14]: [Transparency obligations under Article 50 of the AI Act](https://digital-strategy.ec.europa.eu/en/faqs/transparency-obligations-under-article-50-ai-act) — European Commission, accessed 2026-10 [^15]: [Guidelines on transparency obligations for providers and deployers of certain AI systems](https://digital-strategy.ec.europa.eu/en/policies/guidelines-ai-transparency-obligations) — European Commission, 2026-07 [^16]: [Guidelines 2/2023 on Technical Scope of Art. 5(3) of ePrivacy Directive, version 2](https://www.edpb.europa.eu/system/files/documents/2024-10/edpb_guidelines_202302_technical_scope_art_53_eprivacydirective_v2_en_0.pdf) — European Data Protection Board, 2024-10 [^17]: [Regulation (EU) 2016/679 (General Data Protection Regulation)](https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng) — EUR-Lex, 2016-04 [^18]: [Case Comment: Lying Chatbot Makes Airline Liable: Negligent Misrepresentation in Moffatt v Air Canada](https://www.canlii.org/en/commentary/doc/2025CanLIIDocs1963) — UBC Law Review, via CanLII, 2025 [^19]: [Gartner Survey Finds 87% of Customers Say Companies Using GenAI for Customer Service Must Provide Access to a Human Agent](https://www.gartner.com/en/newsroom/press-releases/2026-08-04-gartner-survey-finds-87-percent-of-customers-say-companies-using-genai-for-customer-service-must-provide-access-to-a-human-agent0) — Gartner Newsroom, 2026-08-04 [^20]: [Gartner Predicts Agentic AI Will Autonomously Resolve 80% of Common Customer Service Issues Without Human Intervention by 2029](https://www.gartner.com/en/newsroom/press-releases/2025-03-05-gartner-predicts-agentic-ai-will-autonomously-resolve-80-percent-of-common-customer-service-issues-without-human-intervention-by-20290) — Gartner Newsroom, 2025-03-05 [^21]: [Intercom Pricing](https://www.intercom.com/pricing) — Intercom, accessed 2026-10 [^22]: [RFC 5545: Internet Calendaring and Scheduling Core Object Specification (iCalendar)](https://www.rfc-editor.org/info/rfc5545/) — IETF / RFC Editor, 2009-09 [^23]: [RFC 6047: iCalendar Message-Based Interoperability Protocol (iMIP)](https://www.rfc-editor.org/rfc/rfc6047.html) — IETF / RFC Editor, 2010-12 [^24]: [Data protection laws](https://u.ae/en/about-the-uae/digital-uae/data/data-protection-laws) — The UAE Government portal (u.ae), accessed 2026-10 [^25]: [Guide to the Saudi Personal Data Protection Law, Version 1.0](https://dgp.sdaia.gov.sa/wps/wcm/connect/85a664fd-6e4e-4edb-bab4-1cbdb02ba6d5/Guide+to+the+saudi+PDP+law+HANDBOOK__%D9%90EN.pdf?MOD=AJPERES) — Saudi Data and AI Authority (SDAIA), 2023-12 --- 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.