What is live, what is pilot, what is planned

// Platform

• Workflow engine

  ●Live

  Visual workflows with approvals, retries, per-node time limits, structured output and step-by-step traces. A guard against duplicate side effects is built but switched off.

• Knowledge bases

  ●Live

  Upload documents and an AI employee answers from them. Memory that carries across conversations is not built.

• Knowledge search step

  ●Live

  A workflow step that looks up passages in one knowledge base before an AI step answers, so the answer can use what was found. In production since 2026-11-05, for every workspace.

• Text helpers in workflow expressions

  ●Live

  Condition, switch and set-variable steps can check text (for example whether it contains a word or starts with a prefix) without calling a model. In production since 2026-11-05; existing expressions are unchanged.

• Workspaces and tenant isolation

  ●Live

  Each workspace's data is separated at row level. A dedicated-database option is designed for large tenants but not offered yet. Backup and recovery tooling for it is still in progress.

• Long-term memory

  ○Planned

  Remembering a person across conversations is specified, not built.

// Channels

• GraphQL API and web chat SDK

  ●Live

  Build your own interface against the same API we use, or embed a chat widget.

• Telegram

  ●Live

  Connect a Telegram bot to an AI employee.

• Messaging through a partner platform

  ●Live

  Channels such as WhatsApp reach an AI employee through a partner messaging platform that connects over our SDK.

• Smart group messaging

  ◐Pilot

  In Telegram groups an AI employee answers only when mentioned or replied to, with a cooldown and a daily cap. Runs on staging.

• Voice calls

  ◐Pilot

  You can talk to an AI employee by voice from your browser in pilot setups. The option of a live speech engine and a transcript record of that call are in the production code, switched off until enabled for a workspace. Voice calls themselves are not available in production yet, and response delay is still above our target.

• Outbound calls from an AI employee

  ◐Pilot

  A workspace owner can have an AI employee ring their own phone as a test. Calls to anyone else are refused. The code is in production, switched off until enabled for a workspace; no workspace has it on.

• Native WhatsApp and Slack connectors

  ○Planned

  Not built. Today these channels are reached only through a partner platform.

// Workspace and media

• Role templates

  ●Live

  Role templates are published and listed in the catalogue. The hire gallery that presents them is a demo; after a hire it offers buttons to chat with the new employee or see it in the office.

• AI Lead Qualifier

  ◐Pilot

  Asks a few set questions on a connected chat and writes a short lead summary. Runs in the Sales demo workspace; its documents and rules are yours to set.

• AI Follow-up Writer

  ◐Pilot

  Prepares a follow-up message marked as a draft. Nothing is sent until an owner approves it. Runs in the Sales demo workspace.

• AI Sales Coach

  ◐Pilot

  Answers a rep's questions from the playbook documents you upload. It reads only what you give it. Runs in the Sales demo workspace.

• AI Office

  ◐Pilot

  A board and an office view of your AI employees, their tasks and what needs a decision. Runs on staging and demo workspaces.

• Generated files: voice-over, music, explainer video

  ◐Pilot

  Workflows can produce a voice-over, a short jingle or a video script. Video export is recorded in your browser; server-side video rendering is not built.

• AI Hub demo workspace

  ◐Pilot

  A demo workspace for a sample company with several AI employees. A hub on a customer's own domain is not built.

• Team sign-in, password reset and invites

  ◐Pilot

  Workspace owners and members sign in on a shared host. Verified on staging.

• Hub on your own domain

  ○Planned

  Not built.

• Delegation with owner approval

  ●Live

  A General Manager AI employee plans the work, asks the owner to confirm, then hands it to a colleague that drafts and waits for the owner's approval. Drafts only; nothing is sent. The engine support is in production since 2026-11-05: a delegating workflow reports a colleague waiting for approval, and such a workflow can be published. The General Manager and its colleagues are demo employees on the staging-backed app and are not yet hired into production workspaces.

// Control and trust

• Weekly owner digest

  ◐Pilot

  A plain summary of the last seven days for workspace owners: conversations, runs, approvals, files and most active employees. The code is in production, switched off until enabled for a workspace.

• Assisted drafts

  ●Live

  An AI employee drafts a reply or a next step and a person reviews and sends it. New AI employees start in drafts-only mode.

• Owner approvals and member drafts

  ●Live

  A step can wait for a workspace owner to approve or reject it. Members draft; owners decide.

• Request changes on approvals

  ●Live

  An owner can send a draft back with a note instead of approving or rejecting it. The AI employee revises and asks again, up to 3 times. In production since 2026-11-05 through the API; the request-changes button in the workspace app is still on the staging-backed app.

• Run traces and audit log

  ●Live

  Every run is traced step by step. Sensitive changes are written to an audit log. Spend caps and per-key model limits apply.

• Auto-approve under a threshold

  ○Planned

  Let routine work pass without a click below a limit you set. Not built.

• Runs alone with a trace

  ○Planned

  Full autonomy for chosen tasks, with the trace kept. Not built.

• Independent penetration test

  ○Planned

  Not done yet.

// Commercial

• Self-serve billing and pricing

  ○Planned

  Pricing is in design. Usage caps and cost tracking exist; there is no billing yet.