> For the complete documentation index, see [llms.txt](https://docs.eesel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eesel.ai/integrations/chat-surfaces.md). # Channels Channels where customers talk to your AI agent: a chat widget on your website, an inline embed, a public chat link, your helpdesk's live chat, or a phone call. A channel is a place your customers chat with your AI agent in real time: a chat widget on your own website, a chat inside one of your pages, a page eesel hosts for you, your helpdesk's live chat widget, or your support phone line. Every channel reaches the same agent, with the same knowledge and instructions. Channels are where your customers talk to your AI teammate. On your own site, on a page eesel hosts for you, or in your helpdesk's chat widget. It answers from your site, your help center and everything else you have connected, and links the page it used. On a store it also recommends products, checks stock and looks up an order. | Channel | Where it lives | How you add it | Handing over to a person | Best for | | ----------------------------------------------------------------------------- | ------------------------------------------------- | --------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------- | | [**Chat Bubble**](/integrations/chat-surfaces/chat-bubble.md) | A floating button in the corner of your website | One script tag before ``, on any platform | Opens Zendesk Messenger or Freshchat if you run one, or follows handover rules such as creating a helpdesk ticket | An AI chatbot on every page of your site or store | | [**Inline Embed**](/integrations/chat-surfaces/inline-chat.md) | Inside one page of your site, as part of the page | One iframe pasted into the page | Follows handover rules, such as creating a helpdesk ticket | Contact pages, help centers and docs pages | | [**Public Chat Link**](/integrations/chat-surfaces/public-chat.md) | A page hosted by eesel, shared by link | Nothing to install. Anyone with the link can chat, no sign-in | Follows handover rules, such as creating a helpdesk ticket | Trying your agent out, or sending it to a customer or partner | | [**Zendesk Messenger**](/integrations/helpdesks/zendesk/zendesk-messenger.md) | Your existing Zendesk Messaging widget | Approve eesel for Zendesk Conversations, then pick eesel AI as the bot in Zendesk | Hands the chat to your team as a Zendesk ticket | Teams already on Zendesk live chat | | [**Fresh Chat**](/integrations/helpdesks/freshdesk/freshchat.md) | Your existing Freshchat widget | An API token and a webhook, on top of your Freshdesk connection | Assigns the chat to a group or an agent | Teams already on Freshchat | | [**Phone calls**](/integrations/chat-surfaces/phone-calls.md) | Your support phone line | Not self-serve yet: contact us, and we set up a number with you | Transfers the call to your team's number, or offers a call back | Teams that take support calls | The first three, and Phone calls, are eesel's own and work with any helpdesk, or none. Zendesk Messenger and Fresh Chat reuse the knowledge that helpdesk connection already gave your teammate. If your app is missing, the [integrations overview](/integrations/overview.md) has the full list, and how to ask for one. ## FAQ
What is the difference between the eesel chat bubble, inline embed and public chat link? The chat bubble floats in the corner of every page of your website, the inline embed sits inside one page as part of its content, and the public chat link is a page eesel hosts that you share by link. All three reach the same agent with the same knowledge and instructions, and you can run them together.
Which eesel channel should I use to add an AI chatbot to my website? Use the [Chat Bubble](/integrations/chat-surfaces/chat-bubble.md) to add an AI chatbot to every page of your website. If you want the chat inside one page instead, such as a contact or help page, use the [Inline Embed](/integrations/chat-surfaces/inline-chat.md). If your site already runs Zendesk Messenger or Freshchat, eesel can answer in that widget instead.
Can one eesel agent answer on several channels at once? Yes. One agent can answer in the chat bubble, an inline chat, a public link and your helpdesk at the same time, with one set of instructions. The chat bubble, inline embed and public link each also have an **Instructions for this channel** box for anything that should apply only there.
--- # 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://docs.eesel.ai/integrations/chat-surfaces.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.