Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.eluu.ai/llms.txt

Use this file to discover all available pages before exploring further.

A colleague is an AI teammate. You give them a name, a role, and access to the tools you use. They do work for you across all of those tools — drafting emails, updating CRMs, building reports, watching for things you care about. Each colleague owns one role. Sofia might run sales operations. Max might handle customer support. Aria might do meeting intelligence. The same way you’d hire a person for a function, you create a colleague for it.

​
How tightly to scope them

How focused a colleague should be depends on the size of the work. There’s no rule — just pick what makes sense:
  • Small team or solo: one colleague does a whole function. A “sales colleague” handles prospecting, outreach, pipeline, and reporting.
  • Bigger teams: split functions into focused colleagues. One does outbound prospecting. Another does renewals. Another does meeting notes.
You build colleagues as you grow. You don’t add tools.

​
What each colleague replaces

A single Eluu colleague can replace what you’d otherwise buy as a focused AI SaaS product:
  • A sales colleague does what specialised sales-AI products do.
  • A customer support colleague does what an AI inbox-triage product does.
  • A meeting-intelligence colleague does what a meeting-notes product does.
  • A research colleague does what a research-AI product does.
Except: it’s the same platform, the same memory, and the same set of tools across all of them. One bill instead of five.

​
What you can give them

When you create a colleague, you set:
  • Identity — name, role, photo, who can use them (just you, or your whole team).
  • Personality — how they talk and how they refuse.
  • Skills — packaged workflows you import or write.
  • Custom commands — slash commands like /morning-brief they run on demand.
  • Integrations — which tools they can use, and whether each tool runs automatically or asks you first.
  • Memory — files and notes that build up over time. They get sharper the longer you work with them.

​
Personal or Shared

Each colleague is either yours alone or Shared with your team. Personal colleagues are good for experiments and individual workflows. Shared colleagues are how the team gets value at scale — once Sofia is good at running pipeline reviews, everyone benefits.

​
Where to next

The hard disk

Where each colleague’s memory lives.

Build a colleague

Step through the configuration.