> 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/getting-started/readme.md). # Welcome to eesel AI agent for customer support that works in your helpdesk, website chat, Slack and inbox. Start here to connect your first app and put eesel to work. eesel is an AI agent for customer support and for the rest of your team. It answers tickets, website chats, Slack questions and email, using your own help center, past tickets and docs. With eesel AI you hire an AI teammate. You plug it into the tools your team already uses, and it works in them like a colleague does. There is no new app for your team to learn: it shows up in your helpdesk, your website chat, your Slack and your inbox.
A support ticket assigned to eesel AI with a drafted reply and the help center articles it used, shown across Freshdesk, Intercom and Zendesk

Your teammate working a ticket in Freshdesk, Intercom and Zendesk, naming the help center articles it used.

{% hint style="info" %} **Using Claude Code, Codex or Cursor?** Ask it to set up eesel with [eesel CLI](https://docs.eesel.ai/apis-and-developer-resources/cli). Point it to the [setup guide](https://docs.eesel.ai/getting-started/set-up-from-a-coding-agent). **Using Claude.ai or ChatGPT?** Use the eesel connector (MCP). See [Claude and other assistants](/apis-and-developer-resources/use-eesel-from-claude-and-other-assistants.md) or [ChatGPT](/apis-and-developer-resources/use-eesel-from-chatgpt.md). If the eesel connector is already linked to the correct workspace, keep using it. For steps it cannot complete, use the dashboard. **CLI details for your coding tool:** Start a new trial with `npx @eesel/cli init` (no account needed). For an existing workspace, run `npx @eesel/cli login` first. You can also set up eesel yourself in the dashboard. {% endhint %}
For AI agents and scripts For the user's requested eesel setup, use the terminal or an existing eesel MCP connection: 1. **Starting with terminal access? Use the CLI.** Follow [Set up from Claude Code or the terminal](/getting-started/set-up-from-a-coding-agent.md). `eesel init` can start an anonymous trial without login; use the intended existing workspace when applicable. Read the real connection links, snippets and status output, then verify knowledge and an answer in the requested channel. 2. **eesel MCP already connected to the intended workspace? Use it.** Its tools can chat, connect integrations and manage automations without another setup. To add a new MCP connection, see [Claude Code and MCP clients](/apis-and-developer-resources/claude-code-and-mcp-clients.md). The token route also works with an anonymous workspace created through the CLI; OAuth connectors require sign-in. 3. **A person still approves external access.** If the connect command returns a link, give it to the person authorized in that tool. If it returns a held receipt with no link, ask for one: `eesel chat "give me the connect link for "`. Do not retry a held action. Confirm the connection with `eesel status`; workspace permissions and action approvals still apply. Trigger keys are listed in a Key column on each integration page. Use that page's checks to verify the requested setup.
## Start anything by talking to it You do not configure eesel, you brief it. Open the chat in your dashboard and say what you want done. Connecting a tool, teaching it your business, changing how it replies, setting up an automation: it is all the same conversation. It does the setup, asks when it needs something from you, and confirms when it is done. The one step it cannot do for you is a sign-in. It hands you a link and you approve eesel in the tool itself. Here is what that looks like. You ask, and it lays out the options and takes it from there.
A dashboard chat where the user asks the agent to connect a helpdesk, and the agent lays out the ways to connect

A setup conversation in the dashboard chat.

Prefer to click through it yourself? Open **Integrations** in the left sidebar and add the tool there. ## Pick a starting point Most people start with one job in mind. Pick the closest and follow its guide. | Starting point | What it does | Guide | | ------------------------ | -------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- | | **Helpdesk** | Resolves support tickets. Drafts or sends replies, tags, escalates. | [Helpdesk guide](/use-cases/helpdesk.md) | | **Content writing** | Writes SEO-aware blog posts in your brand voice. | [Content writing guide](/use-cases/content-writing.md) | | **Internal operations** | Answers your team's questions from your docs, inside Slack, and acts across your tools when asked. | [Internal operations guide](/use-cases/internal-operations.md) | | **E-commerce sales rep** | Looks up orders and products, handles returns with your approval. | [E-commerce sales rep guide](/use-cases/e-commerce-sales-rep.md) | | **Browser extension** | Puts the same agent in a Chrome side panel, beside whatever page you have open. | [Browser extension guide](/use-cases/browser-extension.md) | These are starting points, not separate products. One agent can hold more than one role and connect to as many integrations as you like. Add a second agent when you want a genuinely separate job. ## Popular integrations Each integration gives your teammate up to three things: sources it can read, triggers that wake it up, and actions it can take in that tool. These are the ones most teams start with. The [Integrations overview](/integrations/overview.md) lists every integration. {% tabs %} {% tab title="Helpdesks" %} | Tool | What your agent gets | Guide | | ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------- | | Zendesk | Help center, macros and tickets as knowledge. Replies, internal notes, tags and routing on tickets. | [Zendesk](/integrations/helpdesks/zendesk.md) | | Freshdesk | Help center, canned responses and tickets as knowledge. Replies, private notes, tags and routing. | [Freshdesk](/integrations/helpdesks/freshdesk.md) | | Salesforce | Cases, contacts, accounts and knowledge articles as knowledge. Case comments and record updates. | [Salesforce](/integrations/helpdesks/salesforce.md) | | Intercom | Help center, macros and past conversations as knowledge. Replies, internal notes, tags and assignment. | [Intercom](/integrations/helpdesks/intercom.md) | | Gorgias | Help center, macros and tickets as knowledge. Replies, internal notes, tags and ticket fields. | [Gorgias](/integrations/helpdesks/gorgias.md) | | HubSpot | Knowledge base and past tickets as knowledge. Replies on inbox conversations and ticket updates. | [HubSpot](/integrations/helpdesks/hubspot.md) | | Help Scout | Docs site and past conversations as knowledge. Replies, notes and tags, and Beacon live chats. | [Help Scout](/integrations/helpdesks/help-scout.md) | | Front | Help center and past conversations as knowledge. Replies or internal comments, tags, assignment and archiving. | [Front](/integrations/helpdesks/front.md) | | Zoho Desk | Help center and past tickets as knowledge. Replies, private comments, tags and routing to departments. | [Zoho Desk](/integrations/helpdesks/zoho-desk.md) | | Re:amaze | Response templates, past conversations and help center articles as knowledge. On a schedule, replies or internal notes, tags, assignee and status. | [Re:amaze](/integrations/helpdesks/reamaze.md) | Also: [Jira Service Management](/integrations/helpdesks/jira-service-management.md). {% endtab %} {% tab title="Knowledge" %} | Tool | What your agent gets | Guide | | ------------ | ---------------------------------------------------------------------------- | ------------------------------------------------------------- | | Website | Pages crawled from a URL you give, as knowledge. | [Website](/integrations/knowledge/website.md) | | Confluence | Your wiki, read live, with the page linked. | [Confluence](/integrations/knowledge/confluence.md) | | Notion | The pages you share, with their properties, as knowledge. | [Notion](/integrations/knowledge/notion.md) | | Google Drive | The Docs, Sheets, Slides, PDFs and folders you pick, as knowledge. | [Google Drive](/integrations/knowledge/google-drive.md) | | Files | PDF, text, Markdown and CSV files you upload, plus notes you write in eesel. | [Uploading files](/integrations/knowledge/uploading-files.md) | | {% endtab %} | | | {% tab title="Chat" %} | Tool | What your agent gets | Guide | | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- | | Slack | Wakes when someone @mentions it in a channel, or when a message in a channel it is in is something it can help with. Answers in the thread. Searches Slack live. | [Slack](/integrations/communication/slack.md) | | Discord | Answers @mentions in a thread, and messages it can help with in channels it can see. | [Discord](/integrations/communication/discord.md) | | Chat Bubble | eesel's own chat bubble on your website. Answers from your knowledge and hands over to a person. | [Chat Bubble](/integrations/chat-surfaces/chat-bubble.md) | | Zendesk Messenger | Answers live chats in the Zendesk widget, and hands over by creating a ticket. | [Zendesk Messenger](/integrations/helpdesks/zendesk/zendesk-messenger.md) | | Fresh Chat | Answers Fresh Chat live conversations. | [Fresh Chat](/integrations/helpdesks/freshdesk/freshchat.md) | | Google Chat | Answers @mentions in your spaces and direct messages, in the thread. | [Google Chat](/integrations/communication/google-chat.md) | | WhatsApp Business | Answers your customers on your own WhatsApp Business number. | [WhatsApp](/integrations/chat-surfaces/whatsapp.md) | | WhatsApp for your team | Answers your team on eesel's shared WhatsApp number, from their phones. | [WhatsApp](/integrations/chat-surfaces/whatsapp.md#set-up-whatsapp-for-your-team) | | Microsoft Teams | Answers in your Teams channels and chats, and keeps answering follow-ups in a thread. | [Microsoft Teams](/integrations/communication/microsoft-teams.md) | | {% endtab %} | | | {% tab title="Stores and tools" %} | Tool | What your agent gets | Guide | | ----------------- | -------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------ | | Shopify | Products, pages and policies as knowledge. Live order, customer and product lookups, returns and refunds. | [Shopify](/integrations/e-commerce/shopify.md) | | Magento | Live order, tracking, payment and stock lookups. Refunds, cancellations and customer notices. | [Magento](/integrations/e-commerce/magento.md) | | BigCommerce | Live order, customer, product and stock lookups. Answers on your storefront, in your helpdesk and in Slack. | [BigCommerce](/integrations/e-commerce/bigcommerce.md) | | Gmail | Wakes on new mail. Drafts and sends replies, changes labels, searches threads. | [Gmail](/integrations/communication/gmail.md) | | Asana | Projects and tasks as knowledge. Creates and updates tasks and comments. Contact us to switch it on. | [Asana](/integrations/project-management/asana.md) | | Browser extension | Your agent in a Chrome side panel on any page. Drafts from the page you have open and saves tabs as knowledge. | [Browser extension](/use-cases/browser-extension.md) | | {% endtab %} | | | | {% endtabs %} | | | Knowledge is not kept separate per integration. An agent with a helpdesk, Confluence and your website connected searches all three at once. ## What makes eesel different * **It works in the tools you already have.** A real agent in Zendesk, Freshdesk, Gorgias or Intercom, a chat bubble on your website, a teammate you @mention in Slack. * **It learns your business.** Connect your help center, past tickets, internal docs and website. * **You stay in control.** Start with the agent drafting for review, then widen what it does on its own once you have seen how it does. * **You pay for the work it does.** A monthly plan of credits, where one ticket your agent handles is 1 credit however many replies it takes. No per-seat fees, no limits on integrations. See [Pricing](/pricing/overview.md). ## Start supervised, then hand over 1. **Test.** Chat with your agent in the dashboard. No customer impact. 2. **Review.** Create your first automation, then let it work on real tickets while you approve every reply before it sends. 3. **Hand over.** Let it handle routine work on its own while it escalates the tricky cases. Nothing runs until you create an automation. For each action you then choose: run on its own, ask you first, or stay off. An action set to ask you first waits in the dashboard with three buttons: **Approve** runs it once, **Always allow** stops asking for that action, and **Deny** discards it. ## Where to go next | Section | What it covers | Link | | --------------------------------------- | ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Instructions and Memory | The rules your agent follows, and how it saves your corrections. | [Instructions and Memory](/instructions-and-memory/instructions-and-memory.md) | | Actions and Approvals | How to set each action to run on its own, ask you first, or stay off. | [Actions and Approvals](/instructions-and-memory/actions-and-approvals.md) | | Automations and Schedules | The events and schedules that start your agent. | [Automations and Schedules](/automations-and-schedules/automations-and-schedules.md) | | Skills | Extra workflows on top of the day-to-day work, run on demand or on a schedule. | [Skills](/skills/skills.md) | | Integrations | Sources, triggers and actions explained, plus how to connect and uninstall. | [Integrations overview](/integrations/overview.md) | | Pricing | The free trial, credit plans, and what uses credits. | [Pricing](/pricing/overview.md) | | Set up from Claude Code or the terminal | The same setup as terminal commands, for Claude Code and Cursor. | [Set up from Claude Code or the terminal](/getting-started/set-up-from-a-coding-agent.md) | | Use eesel from Claude or ChatGPT | Talk to your agent and change its setup from a chat assistant. | [Claude and other assistants](/apis-and-developer-resources/use-eesel-from-claude-and-other-assistants.md), [ChatGPT](/apis-and-developer-resources/use-eesel-from-chatgpt.md) | ## FAQ
What is eesel AI? eesel AI is an AI teammate you plug into the tools your team already uses: your helpdesk, your website chat, your Slack and your inbox. It learns from your help center, past tickets, internal docs and website, and works in those tools like a colleague does.
Do I need to switch helpdesks to use eesel? No. eesel works inside the tools you already have, such as Zendesk, Freshdesk, Gorgias or Intercom, so there is no new app for your team to learn. See the [Integrations overview](/integrations/overview.md) for every tool it connects to.
Will eesel start replying to customers as soon as I connect my helpdesk? No. Nothing runs until you create an automation. You can connect everything, test your agent in the dashboard chat, and turn on work only when you are ready. See [Automations and Schedules](/automations-and-schedules/automations-and-schedules.md).
How do I set up eesel? Open the chat in your dashboard and tell your agent what you want. It does the setup, asks when it needs something, and confirms when it is done. The one step you do yourself is a sign-in, when you approve eesel in the tool you are connecting.
Can one AI agent handle support, Slack and more? Yes. One agent can hold more than one role and connect to as many integrations as you like, and it searches all of its knowledge at once. Add a second agent when you want a genuinely separate job.
Can I use eesel from Claude or ChatGPT? Yes. You can add your eesel workspace to Claude, Cursor or another MCP client, and use eesel from ChatGPT. See [Use eesel from Claude and other AI assistants](/apis-and-developer-resources/use-eesel-from-claude-and-other-assistants.md) and [Use eesel from ChatGPT](/apis-and-developer-resources/use-eesel-from-chatgpt.md).
Can I set up eesel from Claude Code or the terminal? Yes. Everything on this site can be done from the terminal with the eesel CLI, starting with `npx @eesel/cli login`. See [Set up from Claude Code or the terminal](/getting-started/set-up-from-a-coding-agent.md).
--- # 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/getting-started/readme.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.