eesel alternative with the inbox included and actions on your API
Compare Eesel with Intake if your team keeps answering the same questions and the answer depends on each customer's data.
In short
Intake or Eesel?
Eesel fits if you resolve fewer than 200 conversations a month: it is the closest competitor to us, with the same per-conversation model, and at that volume it comes in cheaper. Intake fits if you want the same tool to be the inbox as well: 200 conversations for 49 EUR a month and 800 for 129 EUR, on annual billing, with no per-user charge.
Trusted by teams at:
- and 20+ more companies
Three reasons to look for a Eesel alternative
They weigh most when the team is small and the answers depend on each customer’s data.
It sends articles instead of checking the data
A standalone chatbot answers with what the docs say. If the question is “why was I charged this”, the article does not know.
Documentation is not enough when it depends on the customer
The order, the plan or the booking change the answer. Without checking them, the bot gets the general part right and the important part wrong.
You do not know how many were fully resolved
A “resolved” percentage does not say how many conversations ended up with a person the next day.
Receiving the question is easy. The hard part
is resolving it.
How do I invite someone to the team?
Where can I change the billing details?
Can someone help me set this up?
I cannot access the dashboard.
Why do I not have permission for this?
The integration is throwing errors.
Is this included in my current plan?
How do I connect this to Slack?
Can you explain how this flow works?
Can I change the billing contact?
The difference is in the questions that repeat. With Eesel, the ones that depend on each customer’s data usually end up with someone on your team. Intake answers them by checking that data and passes to a person only what it cannot resolve.
Having your conversations organized helps, but it does not close them. What matters is how many a person still has to answer.
01
Checks the account before answering
Before replying, the agent looks at that customer’s plan, settings, usage and history, as well as your documentation.
See the inbox
02
Gets the task done in the conversation
Connected to your API, the agent does what the customer asks, like extending a trial or changing a plan, instead of explaining how.
See actions03
Passes to a person what it cannot resolve
The conversation reaches your team with the history, the account data and an internal note on what has already been tried.
See the handoff
The decision
When switching pays off
It pays off if your team answers the same questions every week and the answer depends on each customer's data: their plan, their invoice, their order. If that is not you, Eesel still does the job and there is no reason to replace a tool that works. To find out, look at how much of your queue repeats. A ten-day trial with no card is enough to see it.
See pricing
Comparison
Intake and Eesel, point by point
Row by row, from what Eesel publishes on its own site. Each row is a sentence, because a yes or no rarely tells you enough.
| Criterio |  Intake | |
|---|---|---|
| The model | Sí: A flat plan from 49 EUR a month, with 200 conversations inside. | No: $0.40 per task, where a task is a whole ticket or chat session. No platform fee and no monthly minimum. |
| Where they win | Sí: Our minimum is 49 EUR a month even if you resolve twenty conversations. | No: No minimum, so at low volume you pay only for what you use. At twenty tickets a month that is $8, and we still charge 49 EUR. |
| What the price includes | Sí: The agent and the inbox: you do not need another tool underneath. | No: The AI layer. Their task catalogue goes beyond support and includes things like drafting blog posts, at $4 each. |
| What the agent does | Sí: Reads account state through your API and takes the action before answering. | No: Answers over the knowledge and the tools you connect to it. |
| When the other is the better fit | — | Sí: It is the closest competitor to us in this whole catalogue and there is no point pretending otherwise: same model, per conversation. If you resolve fewer than 200 conversations a month they come in cheaper and you should start with them. Above that volume the comparison turns on something else: whether you want an AI layer over what you already have, or a tool that is also the inbox. |
Based on what each product publishes, as of October 2026. The row with no Intake mark is the case where Eesel is the better fit.
Step by step
How to move from Eesel
You do not have to switch everything at once. Start with the questions that repeat most, connect the account data needed to answer them and decide when a person should step in.
See how Intake fits SaaS teams
Your customers’ data,
in the EU and under your control.
Intake runs on AWS in the European Union and complies with GDPR. The agent only reads and does in your systems what you allow, and your team can review every answer.
- GDPR
- Data in the EU
- AWS with SOC 2
Questions about Intake and Eesel
How much does Intake cost?
A flat plan by conversations: 200 a month for EUR 49 on annual billing (EUR 59 monthly), 800 for EUR 129 and 2,000 for EUR 289. Month to month, EUR 59, 159 and 359. VAT excluded, and there is no per-seat charge.
What counts as a conversation?
One conversation thread, however many messages it takes. A customer who asks three follow-up questions in the same thread counts once.
What happens if I go over the limit?
The agent pauses until the next cycle and your team keeps answering. There is no overage charge or service cut, and the invoice does not change.
What data does the agent read?
Your documentation and the account data you expose through your API: plan, settings, usage and whatever else you decide. You choose which lookups it can make and how far it goes.
Which languages does it answer in?
It answers in the language of the question, even when the article is written in another one.
How long does it take to get running?
You connect the help center you already have and it starts answering from there. Actions against your API take a little longer because you choose what the agent can do, but nothing needs rewriting to start.
Why choose Intake instead of Eesel?
Because when your customers ask about their invoice or their permissions, a generic article does not solve it. Intake checks the data, takes the action and passes to your team what it cannot resolve.
Do I have to drop Eesel to try Intake?
No. The usual way is to keep Eesel and start Intake on the questions that repeat most. If it does not resolve them, you have lost ten days and no money.
Is there any case where Eesel is the better choice?
Yes, and the table above says which. It is usually a team with settled processes and few repeated questions. If yours is the opposite, with the same question twenty times a month and answers that depend on each customer's plan, Intake is the better fit, and the ten-day trial lets you check.
