> For the complete documentation index, see [llms.txt](https://help.calshare.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.calshare.net/calshare-user-manual-overview.md). # Calshare User Manual - Overview Understand the core architecture, concepts, and structure of Calshare. ## Introduction and Overview **Calshare** is an ecosystem designed to eliminate friction between service providers and their clients when booking appointments. Unlike traditional scheduling platforms that require clients to navigate complex booking flows, Calshare combines an aesthetically pleasing public booking page with an **autonomous virtual assistant powered by WhatsApp (AI)**. ### Key Concepts * **Calendars (Agendas):** These are your public booking pages (if the URL is shared). Each calendar has its own availability rules, session duration, timezone, and instructions for the AI assistant. * **AI Assistant:** A smart bot that simulates human interaction on WhatsApp. It chats with your clients in natural language, checks your availability in real-time, and schedules appointments automatically. * **WhatsApp Session:** A direct connection established between your phone and the Calshare platform by scanning a QR Code (similar to WhatsApp Web), ensuring that all messages are sent and received through your own number. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.calshare.net/calshare-user-manual-overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.