Internal Operations

Set up your agent to answer your team's questions in Slack from your wiki, documents and other connected apps, with the source linked in the thread.

Your AI teammate answers your team's questions in the chat app they already use. It reads your wiki, your documents and every other app you connect to it. Answers come back in the thread, with the source.

You stay in control the whole way. Nothing runs until you create an automation. For each action you then choose: run on its own, ask you first, or stay off.

In this example a teammate asks about SSO in Slack, and the answer cites the Confluence page it came from.

A Slack question answered in the thread, with the source page linked.

Works with: Slack, Microsoft Teams, Confluence, Notion, Google Drive, uploaded files.

Ideal for: hard-to-navigate knowledge bases, onboarding new hires, policy lookups, and the repeat questions every team fields (IT, HR, ops).

Quick start

1

Create an agent

Open the agent dropdown at the top left and choose Create Agent. We recommend a separate agent for internal knowledge. Its instructions then stay focused on your team, not your customers. One agent can hold both roles if you prefer.

2

Tell it about your business

There are two ways to give it your team's knowledge.

Connect the apps where the knowledge lives. Ask your agent to add your wiki pages, for example Confluence. It posts a connect link, and a person approves it in the browser.

The agent posts the Connect Confluence link.

The integration page then shows the connection and how many documents it read.

The Confluence integration page, with the source and its document count.

Upload or create files. Upload the documents you would hand a new starter.

The upload area, opened from the chat, with files ready to go.

You can also ask your agent to write a document. It saves the file in the Files editor.

A file your agent wrote and saved, open in the Files editor.

3

Connect it to your team chat

Ask your agent to connect Slack, then tell it which Slack channels to be active in. Microsoft Teams is available on request, so contact us.

The agent posts the Add to Slack link in the chat.

Open the link. A person approves this in the browser.

Slack's permission screen, with the workspace picker and the permission list.

4

Brief it on the job

Tell it what tone to use, which sources to trust first, and when to escalate to a person. Ask for a standing rule in chat and it saves the rule to its own instructions.

Ask in chat for a habit, and your agent saves it to its instructions.

Open the Instructions page to read or edit the saved rule yourself.

The saved instruction on the Instructions page.

5

Ask it in a channel

Anyone on your team can @mention the eesel app in a Slack channel and ask a question. It answers in the thread and links the source page.

A Slack thread answered from your wiki, with the source page linked.

It stays in the thread after that. Ask it to change how it answers, for example to keep answers short.

The same thread, where it takes feedback and answers again.

From Claude Code, Cursor or a terminal. The same setup works as commands: eesel login, then eesel integrations connect slack, which prints the approval link for a person to open. The approval is a human step: print the link for a person, wait for the connection status to change, and do not retry the link. eesel files uploads your documents, and eesel automations lists your automations. Turning the mention automation on has no command, so use the dashboard chat for that. Full command reference: The eesel CLI. Step-by-step: Set up from Claude Code or the terminal. From an MCP client: Claude Code and MCP clients.

What it can do

Answer

It searches everything it is connected to at once, and every answer links its source. If it cannot find something, it says so.

It can	For example
Answer from your knowledge	"What is our refund policy for orders under $50?"
Search every app at once	Pulls from Confluence, Notion and Drive in a single answer
Summarise a thread or channel	"Catch me up on what I missed here"
Find old decisions	"Did we ever decide how to handle this?"

Act

It can	For example
Create and route tickets	"Raise a ticket for this and assign it to billing"
Write content	"Write a blog post about this feature"
Run skills and reports	"Run the ticket trends report and post it here"
Look up records	"What is the status of order 4821?"
Combine apps	"Find this week's tickets about this bug and summarise them"

One request can cross apps that do not talk to each other.

Notice

Put it on a schedule or hook it to an event, and it works without being asked.

It can	For example
Watch your SLAs	Pings the channel before a ticket breaches, not after
Flag spikes	Tells you when a topic starts trending in support
Post recurring summaries	A digest every Monday, before your meeting
Chase what is slipping	Tells the person who owns it, not the whole channel

Extend

Skills are packaged workflows, such as a simulation, a trend report or a blog post. They run on demand, on a schedule, or off a trigger. Build your own by describing it in chat. Custom API access lets your agent reach internal apps eesel does not integrate with.

Example use cases

• New hire onboarding. "What is our PTO policy?" and "How do I set up VPN?"

• Sales enablement. "What integrations do we support?" and "Do we have a SOC 2 cert?"

• IT support. "How do I reset my email password?"

• SLA watch. Pings the channel before a ticket breaches.

• Project manager. Pulls status from every app, checks it against your goals, and pings the owners of anything slipping.

• Scheduled reporting. Collects the numbers, writes the summary, posts it every Monday.

Related pages

• Slack

• Confluence

• Notion

• Google Drive

• Uploading Files

• Integrations

• Set up from Claude Code or the terminal