Built for teams and agencies
Everything lives in a workspace: agents, knowledge, tools, contacts, conversations, API keys and billing. Invite your team into it with roles, or keep one workspace per client with billing to match.
Clean client separation
One workspace per client keeps knowledge, conversations and invoices apart, with no risk of the wrong agent seeing the wrong documents.
Roles, not shared passwords
Invite by email and set what each member can do - and take it away in one click when they move on.
The workspace owns the work
Agents and transcripts belong to the workspace, not to whoever created them, so staff changes cost you nothing.
Billing that matches the boundary
Plans and usage balances are per workspace, which is what makes per-client invoicing straightforward.
What teams build with it
Three jobs this does the day you turn it on.
One workspace per client
Agencies keep each client's agents, knowledge and conversations separate, with their own billing - instead of one account holding everyone's work and hoping nobody clicks the wrong thing.
Bring the team in properly
Invite colleagues by email with a role, rather than passing round one login that nobody can revoke when someone leaves.
Work that outlives the builder
Agents, knowledge and transcripts belong to the workspace, so when the person who built them moves on, nothing leaves with their account.
Where you set this up
The same build screen every feature is configured from — this row is the one you would touch.
Under the hood
The details you will want before you commit.
How it works
Create a workspace
One per client, per team or per project - your personal one already exists.
Invite the team
Add people by email with the role they should have.
Build inside it
Agents, knowledge, contacts and billing all stay scoped to that workspace.
Where it earns its keep
Industry playbooks that lean on this piece — what to build first, and what to charge.
Frequently asked questions
Because you cannot revoke half of one. A shared password means everyone has every permission, nothing is attributable, and offboarding means changing a password for the whole team.
Yes, with a different role in each. Agencies and consultants sit in every client workspace under one account.
Each workspace carries its own plan and usage balance, so one client's traffic never draws down another's - and each can be invoiced on its own terms.
Remove them from the workspace. The agents, knowledge and conversations stay, because they belong to the workspace rather than to their account.
How it compares
Side by side with the tools people usually weigh this against.
SuperCognit vs Botpress →
Botpress is a developer-oriented platform for building conversational AI with a visual flow editor.
SuperCognit vs Intercom Fin →
Intercom Fin is the AI support agent inside Intercom's customer-service platform, priced per resolved conversation.
SuperCognit vs Zendesk AI →
Zendesk AI adds AI agents and copilots to Zendesk's enterprise customer-service suite.
Ready to ship workspaces & roles?
Free for 7 days — publish your first product this week.
Start building