How Pazi works

Pazi is an AI agent platform for building and managing your business. Each business has one Main Chat where you work with Pazi, while specialists carry out longer work in the background.

Businesses organize the work

A business is the top-level context for Business Pulse, Email Inbox, Opportunities, Tasks & Calendar, Business Setup, shared memory, team access, and shared credentials. Switching businesses changes the company plan and active work you see.

Each account can own one or more businesses according to its plan. A business shared with you belongs to its owner and does not use one of your business slots.

Agents provide durable roles

An agent has a name, voice, avatar, selected model, private memory, skills, workspace, and integrations. New accounts receive a protected primary operating officer automatically. You can create additional agents for specialist roles on every plan. The business owns one shared email address and Inbox, while each outbound message records the acting agent.

The operating officer coordinates company-level decisions and delegates substantial work. Specialist agents perform focused work such as research, design, development, QA, or outreach.

Main Chat keeps work together

Each business has one visible Main Chat. Opportunities, specialist questions, progress, and results return there, so you do not have to manage separate task chats.

Slack and email keep their own channel history. Scheduled and delegated work use hidden runtime sessions so they can run independently without blocking Main Chat. Agents in the same business share business memory and user-facing created files, while each agent keeps its own private workspace and memory.

What happens after you send a message

01.Pazi identifies the selected business and Main Chat.

02.It checks access and whether the billed account has enough funding.

03.It starts or resumes the runtime needed for the work.

04.Pazi receives the latest 30 Main Chat messages by default, plus relevant memory, skills, and available integrations. It can retrieve older history in pages when needed.

05.The agent plans and executes the work, calling Pazi-approved tools when needed.

06.Progress streams into chat and Live View; completed files and action cards become available in the dashboard.

07.The final response, state, and usage are saved so the work can continue later.

Long-running and delegated work

Long jobs continue as durable runs even when the browser request has finished. Pazi can call specialist agents, run multiple opportunities independently, and return their questions and results to Main Chat.

Messages sent during a run

Background opportunity work does not block Main Chat. If a conversational response is already running, Pazi queues follow-ups in order. Send now interrupts that response for one queued message; Stop cancels it and clears the remaining queue.

Where results persist

Main Chat history is stored by Pazi. Use Files in the chat header to review the selected agent's workspace, or expand Main Chat to focus on the conversation and collapse it to return to the split business view. Agent files, skills, memory, and runtime state persist in private or business-scoped storage.

Slack remains the visible history for Slack threads, while the agent keeps the runtime session needed to continue. Email is stored in the selected business's shared Email Inbox.

Models and funding

Pazi-billed agent work uses the responsible account's Cash Balance. For business agents, the business owner is billed even when a team member starts the work.