Features
Assistants
Esan isn't one assistant — it's a roster. An assistant is a named agent you shape for a specific role: a researcher, an editor, a sales assistant, an analyst. Each one keeps its own context and gets better at its job over time.
Why use assistants
- Sharper results. An agent told it's "a B2B SaaS researcher" frames work the way that role would.
- Separate memory. Each assistant remembers its own work, so your researcher's context doesn't bleed into your writer's.
- Reusable. Set one up once and delegate to it again and again.
Create an assistant
- Go to Assistants and create a new one.
- Give it a name and a short role ("a financial analyst for early-stage startups").
- Optionally add a persona — tone, focus areas, and things it should avoid — so its output matches your expectations.
Configure an assistant
Open any assistant to tune it:
- Persona — name, role, tone, focus areas, and limits.
- Knowledge — a long-term document the assistant always has on hand (style guides, background, rules of thumb).
- Connectors — which of your connected apps this assistant may use.
- Skills — which reusable playbooks it can run.
- Memories — its own pool of remembered facts, separate from your other chats.
- Files — documents every session with this assistant can read.
- Voice — the voice and style used when reading its replies aloud.
Talking to an assistant
Open an assistant and start a chat, or mention it from the composer to hand a task to the right teammate. Bring another assistant into a conversation for a second opinion when you want one.
Tips
- Keep each assistant focused. A few sharp roles beat one do-everything agent.
- Put durable context in Knowledge, not in every message.
- Use per-assistant connectors to keep access tight — give your researcher web access without handing it your email.