Customer operations
Support as one domain
Chat, voice, ticket desk, and refund workflows share one space and one review loop.
Spaces · Company operating surface
Run larger slices of the company in one place.
Spaces organize the agents, workflows, tools, and people responsible for a business domain. See what is live, what needs review, and how work moves across the operation—not as disconnected automations.
What it delivers
Four movements from request to result.
- 01
One surface per domain
- 02
Agents and workflows together
- 03
Clear ownership and review
- 04
Room to grow the operation
Product in motion
See spaces turn an interaction into a result.
An illustrative workflow showing the work, the action and the record returned at completion.
One goal. A crew built for it.
Coordinate a planner and specialist agents through explicit roles, parallel work, review, and one final deliverable.
Illustrative workflow
Build with Zoft Copilot
Describe the domain. Copilot scaffolds the space.
Copilot helps assemble the agents, workflows, desks, and review rules that belong in a space so the domain starts coherent.
From tools to an operating layer
When the work spans teams, it needs a shared place to run.
Most stacks leave agents, tickets, and workflows in separate products. Spaces keep the people, agents, and flows for a domain visible together so the business outcome stays reviewable.
Group the real work
Put the agents, workflows, and handoffs for support, booking, or ops under one space instead of hunting across tools.
Operate, not only configure
Monitor live runs, exceptions, and human desks from the same surface that owns the domain.
Expand without restarting
Add channels, agents, or workflows to an existing space as the operation grows.
How it works
Define the domain, assemble the pieces, run the space.
Start with a bounded business slice. Wire the agents and workflows that already exist, then operate day-to-day from one surface.
- 01
Name the domain
Choose the business slice—customer support, booking, fulfillment—and the outcomes the space must own.
- 02
Assemble agents and flows
Attach chat, voice, workflows, desks, and tools that belong to that domain.
- 03
Operate and expand
Review live work, tighten boundaries, and add capability without rebuilding from scratch.
What a space holds
Teams, agents, and workflows stay connected.
- Spotlight 01
Domain ownership
Know which agents and flows belong together and who reviews exceptions.
Crew topologyDelegating - Spotlight 02
Connected execution
Keep conversation, automation, and handoff inside one operating context.
Shared workContext synced - Spotlight 03
Growth path
Scale from a first win to a broader company operating view as Spaces mature.
Crew deliveryApproved
Where Spaces fit
Use Spaces when one agent is not the whole operation.
Spaces earn their place when multiple agents and workflows must stay aligned under one business owner.
Revenue ops
Booking and reminders together
Qualification, scheduling, and follow-up agents operate as one revenue slice.
Internal ops
Back-office domain
Browser tasks, approvals, and notifications sit under the same operating surface.
Built for controlled expansion
Scope the domain before you widen the surface.
Spaces are designed to grow with the company. Boundaries, ownership, and review stay explicit as more agents and workflows join.
- 01
Clear domain boundaries
Decide what the space owns, what stays out, and how exceptions escalate.
- 02
Human review remains visible
Desks and approvals sit beside agents so sensitive work never disappears into automation.
- 03
Honest maturity
Spaces continue to deepen as an operating layer—start with one domain, then expand.
Questions before rollout
Spaces FAQ
Clear scope is part of production quality. These answers separate the product direction from details that are confirmed for each deployment.
How is a Space different from a single workflow?
A workflow is one automated path. A Space is the operating surface for a business domain—agents, workflows, desks, and review together.
Is Spaces fully shipped?
Spaces are in active product progress. Private beta conversations start with a concrete domain and the agents you need live first; the operating surface expands from there.
Do I need Spaces to launch my first agent?
No. Launch chat, voice, or workflow wins first. Spaces matter when you want those pieces operated as one company slice.
Can multiple teams share a Space?
A Space is scoped to a domain. Ownership and review roles are set for that domain; multi-team access follows your deployment design.
What is a good first Space?
Pick a domain with clear outcomes—support or booking—where chat or voice, a desk, and one or two workflows already need to stay coordinated.
Related products
Keep the operating layer connected.
Product 01Multi-Agent WorkflowCoordinate specialized Zoft agents that plan, delegate, work in parallel, hand off context, and return one reviewable deliverable.Product 02DeskZoft Desk combines support tickets and human-in-the-loop takeover so agents escalate with full context and resume after people resolve sticky cases.
Compare platforms
Decide with the actual operation in view.
Start with one domain
Put the first Space into the private beta conversation.
Join the private beta, or talk with the team about the domain, agents, desks, and workflows the first Space should hold.