Filmed on the real product, never on slides. Three tracks: what an AI employee is, what each capability does, and how a whole business runs on it.
Search a keyword, or filter by track.
The very first step, before any hire: deploy your workspace and choose how it runs, All-Inclusive or bring your own keys (BYOK). About two minutes, start to finish.
What it is, and above all what it is not. A chatbot waits to be prompted. An employee has its own address, its own channels, a memory, limits, and it works while you are closed.
The whole first day, start to finish: hire, give it a job and your instructions, connect one channel, and get a first real task done. The only episode that follows a path end to end.
Workspace settings on one side, an employee’s own configuration on the other. Short and structural: it is the single most common confusion, and knowing which level you are on saves every later question.
Sarah writes on WhatsApp, emails two days later, then calls. One thread, one employee, and she is never asked twice for something she already said.
The office is closed. The call is answered anyway, the request is qualified, a slot is offered, and the morning after there is something usable waiting.
A request becomes a card, stalls because one person is away, moves to Needs attention, and restarts on a one-line answer. Arrival, blockage, resolution — the shortest complete scene in the season, which is why it is filmed first.
Install a skill from the catalogue, then use it in the same sitting on a real document. Installing alone proves nothing, so the episode does not stop there.
The 07:30 recap and tomorrow’s appointment reminders, both prepared overnight. You read the result before the first coffee.
A quote left unanswered, a deadline getting close: the employee notices on its own. The contrast with scheduled work is the whole episode — one follows a clock, the other follows a situation.
An out-of-scope request arrives and never reaches the employee. Then what the administrator sees in Guardrail Blocks — and what the sender, deliberately, does not.
Your house procedure — who calls back, within what delay, in which words — written once and applied from then on without being restated.
One full day at a practice, end to end: the call after closing, the WhatsApp message next morning, the card that stalls on an absent practitioner, the reminders that go out on their own.
A quote goes out, nobody replies, and the follow-up happens anyway — at the right moment, in the right tone, and it stops the second the client answers.
The most repeated question in ecommerce, handled on three channels without a human rereading it — and the exact moment the employee hands it back.
For partners: the same product under another name, and a clear line between what the end client sees and what stays yours.
Four employees pointed at acquisition: one writes articles and visuals every day, one keeps the website moving, one publishes to social, one runs the Google Ads. Taken from a real customer setup.
The night round on a demo VM: CPU, memory, disk, errors in the logs, attack attempts in NGINX, odd processes, whether last night’s backup actually ran, image sizes, pending updates. Then an incident lands live from the monitoring — outside the round.
Ready to try it?
Open the productYou are not meant to watch the season in order. Pick the track that matches where you are.
You have never opened the product. What an AI employee is, where things live, and how the first hire actually goes.
One capability per episode, always inside a real situation. Channels, voice, kanban, skills, automation, monitoring, guardrails, memory.
Sorted by situation rather than by feature. Find the one that looks like yours and watch it run from the first message to the finished job.
Every employee in this series can be hired in about a minute, on a free trial.
