How it works
The mental model — you run AI employees; they serve your customers. What an employee is, where it works, and how customers experience it.
Getting started
Holaboss has two sides, and everything else hangs off the line between them: you run AI employees, and those employees serve your customers. Keep that split in mind and the rest of the product falls into place.
The employee
An employee is the thing that does the work. It's defined by a few parts:
- Mandate — its standing instructions: who it is, what it's responsible for, how it should behave. The mandate is read at the start of every run.
- Model — which model powers it (and separate image / video models where it generates media).
- Abilities & skills — the tools it can use (web search, code execution, MCP integrations) and the reusable skill packs you switch on. A per-employee tool policy lets you turn specific tools off.
- Memory & knowledge — what it carries between runs: durable memory it writes for itself, plus a knowledge base of your documents it can search.
You can shape an employee from the console, or drive it with your own agent over MCP — the same
primitives either way (set_mandate, set_model, set_skills, then publish_employee).
Where it works — channels
An employee shows up wherever your customers already are. Connect a channel once and it's live there:
- Slack, WeChat / WeCom, Discord, or an embeddable web widget.
How customers experience it — the portal
Your customers get a branded portal — the App. They sign in, see their orders, files, and deliverables, and hold a thread with your team (and the employee behind it). You can spin the portal up from a template, or build your own on the SDK.
The loop
The two sides reinforce each other. An employee delivers a service; the customer side captures what happened — the interactions, the outcomes, the corrections; that feedback makes the employee measurably better at the service; better service brings more customers. The employee alone and the customer side alone are each ordinary — the loop between them is the point.
What's built in
You don't assemble the plumbing yourself:
- Billing & credits — every model call is attributed and debited automatically.
- Observability — every run is traced: what the model was asked, what it returned, what it cost.
- Identity & channels — sign-in, connectors, and per-org isolation are handled for you.
Next: the Quickstart walks through building your first employee and giving your customers a portal.