For the complete documentation index, see llms.txt. This page is also available as Markdown.

Welcome to eesel

eesel gives you an AI teammate that works inside your helpdesk, website chat, Slack and inbox. Start here to connect your first app and put it to work.

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.

Using Claude Code, Cursor or another AI coding agent to set this up? Everything on this site can be done from the terminal: npx @eesel/cli login, then follow Set up from Claude Code or the terminal. Using eesel from a chat assistant instead? See ChatGPT and Claude and other assistants.

For AI agents and scripts

If you are an AI agent setting eesel up on someone's behalf, do not drive the dashboard in a browser. Use one of these instead, in this order:

  1. MCP. If your client supports MCP, connect to eesel's MCP server and use its tools to chat, connect integrations and manage automations. See Claude Code and MCP clients.

  2. CLI. Otherwise use the eesel CLI. eesel login, eesel integrations connect <platform>, eesel integrations download start, eesel automations. See The eesel CLI and Set up from Claude Code or the terminal.

  3. A person for the sign-in. A full connection needs a person to approve it in the tool itself. If the connect command returns a link, print it for them. If it returns a held receipt with no link, ask for one: eesel chat "give me the connect link for <app>". Either way, do not retry it, and check eesel status until the integration shows as connected.

Trigger keys are listed in a Key column on each integration page. Every page states what "connected" and "automation running" look like, so you can check your work.

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.

Content writing

Writes SEO-aware blog posts in your brand voice.

Internal operations

Answers your team's questions from your docs, inside Slack, and acts across your tools when asked.

E-commerce sales rep

Looks up orders and products, handles returns with your approval.

Browser extension

Puts the same agent in a Chrome side panel, beside whatever page you have open.

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.

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 lists every integration.

Tool
What your agent gets
Guide

Zendesk

Help center, macros and tickets as knowledge. Replies, internal notes, tags and routing on tickets.

Freshdesk

Help center, canned responses and tickets as knowledge. Replies, private notes, tags and routing.

Salesforce

Cases, contacts, accounts and knowledge articles as knowledge. Case comments and record updates.

Intercom

Help center, macros and past conversations as knowledge. Replies, internal notes, tags and assignment.

Gorgias

Help center, macros and tickets as knowledge. Replies, internal notes, tags and ticket fields.

Also: Front, HubSpot, Help Scout, Jira Service Management.

Tool
What your agent gets
Guide

Website

Pages crawled from a URL you give, as knowledge.

Confluence

The pages you pick, as knowledge.

Notion

The pages you share, with their properties, as knowledge.

Google Drive

The Docs, Sheets, Slides, PDFs and folders you pick, as knowledge.

Files

PDF, text, Markdown and CSV files you upload, plus notes you write in eesel.

Tool
What your agent gets
Guide

Slack

Wakes when someone @mentions it in a channel, and answers there. Searches Slack live.

Chat Bubble

eesel's own chat bubble on your website. Answers from your knowledge and hands over to a person.

Zendesk Messenger

Answers live chats in the Zendesk widget, and hands over by creating a ticket.

Fresh Chat

Answers Fresh Chat live conversations.

Microsoft Teams

Answers in your Teams channels. Contact us to switch it on.

Tool
What your agent gets
Guide

Shopify

Products, pages and policies as knowledge. Live order, customer and product lookups, returns and refunds.

Magento

Live order, tracking, payment and stock lookups. Refunds, cancellations and customer notices.

Gmail

Wakes on new mail. Drafts and sends replies, changes labels, searches threads.

Asana

Projects and tasks as knowledge. Creates and updates tasks and comments.

Browser extension

Your agent in a Chrome side panel on any page. Drafts from the page you have open and saves tabs as knowledge.

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 only pay for what it does. You pay per task, and one ticket your agent handles is one task however many replies it takes. No per-seat fees, no limits on integrations. See Pricing.

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.

Actions and Approvals

How to set each action to run on its own, ask you first, or stay off.

Automations and Schedules

The events and schedules that start your agent.

Skills

Extra workflows on top of the day-to-day work, run on demand or on a schedule.

Integrations

Sources, triggers and actions explained, plus how to connect and uninstall.

Pricing

Per-task rates, the annual commitment, and Enterprise.

Set up from Claude Code or the terminal

The same setup as terminal commands, for Claude Code and Cursor.

Last updated