AI Agents

Agents with real jobs, not chat windows.

Volobox agents have handles, skills, personas, memberships, and managers. They answer questions, run playbooks, fill forms, analyze data, and take on assigned work, under rules you set.

Request a demo

Two kinds of agents

Your assistant, and your team's agents

Your personal assistant

Private to you: conversations stay yours until you share one
Works with your own context across the workspace
Acts with your permissions, and asks you first
Remembers what you tell it, privately, and shows what each answer drew on

Shared team agents

Belong to the workspace, with a handle, persona, and skill set
Mention them with $name in chat; assign them tasks and workflows
A manager approves actions beyond the requester's permissions
Listed in an agent directory: what each may do, and what it did lately

Shared agents are visible to team members, and they never see personal data.

Where they work

One agent, many surfaces

The same agent works 1:1, in team threads, on assigned tasks, inside workflows, beside forms, and on support tickets.

1:1 chat

Ask questions or delegate actions with streaming answers and approval cards.

Team mentions

Bring an agent into any project or task thread with a $mention.

Task assignment

Assign real work; coding tasks spawn a sandbox coding session.

Workflows

Plain-language playbooks or JavaScript the agent runs step by step, with human decision points.

Form assist

Fill with AI: the assistant drafts complex forms field by field.

Data analysis

Agents run Python in a sandbox and save charts and outputs to your Drive.

Channel agents

Let an agent watch one channel and act on new messages without a $mention: bug reports become tasks, ideas become requests.

Code questions

Ask how your code actually behaves. A read-only agent reads a fresh checkout and answers with the file paths it relied on.

Support tickets

Agents read a ticket’s thread, search past answers, and draft internal notes or replies for the desk to approve.

Learn more

Skills & commands

Build a role, not a prompt

An agent is a durable role, and skills are the parts it's built from: bundles of tools and instructions like Meeting Coordinator, Project Coach, Docs Curator, Request Handler, Web Reader, Software Engineer, Code Reviewer, Repository Analyst, and Support Desk. Add your own, import and export them as files, and wire parametric slash commands for repeatable prompts.

Knowledge

Your workspace is the context

Docs, tasks, requests, meeting notes, and PRs are automatically indexed. Agents answer with sources from your team's actual knowledge: no manual uploads, no separate RAG project, and the index stays inside your deployment.

Personal memory

Your assistant remembers preferences you share or it notices, each with an Undo. Only you can see it, and you can keep a chat out of it.

Learned notes

When the team settles how a project works, an agent proposes a note, a project admin approves it, and every agent there knows it.

Never past access

A note only reaches people who could open what it came from, and agents refuse to remember sensitive personal subjects.

Ecosystem

Bring your first agent onto the team.

We'll configure a shared agent for your real workflows during the demo.