# Live Chat ## Ebbot Live chat Live chat is the primary workspace where operators (chat users) manage real-time interactions with end users. The interface is built for efficiency, allowing operators to handle multiple conversations simultaneously across various platforms. ### Key examples of how Live chat is utilized include: * Skill-based management – chat users in Ebbot see and manage conversations based on specific skill configurations. * Unified channel management – from a single interface, chat users can respond to chats originating from the Ebbot Chat widget, Microsoft Teams, Slack, or other integrated channels. * Enhanced productivity with Power-ups – chat users can leverage "Power-ups" and integrations to perform complex actions without switching systems. A common example is converting a live conversation directly into a ticket within an external ticketing system to ensure a seamless handoff. Note: The Live chat area is designed for teams using Ebbot as their primary interface. Clients who utilize a channel integration to handle conversations in an external third-party system will not need to use the Ebbot Live chat interface. ## Explore how to use Live chat To learn more about how to use the Ebbot Live chat, read about [Live chat](https://customer.ebbot.ai/knowledge/live-chat) in our customer center. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ebbot.ai/ebbot-docs/core-capabilities/chat/live-chat.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.