Work together without losing control
Use owned content to answer visitor questions with less friction.
7-day free trial
What this feature covers
Why it matters
The practical reason to use it.
Teams is the collaboration layer for running a website assistant after launch.
How it works
A step-by-step look at the workflow.
Step 1
Add teammates and assign roles based on what they need to manage: sources, assistants, conversations, leads, support handoff, billing, or client delivery.
Step 2
Scope access to the assistants, conversations, and client workspaces each person should own.
Step 3
Review conversations, content gaps, and handoff outcomes together so support, sales, content, and digital teams stay aligned.
Step 4
Adjust permissions as the assistant expands to more pages, launch paths, or client accounts.
Core job
The main job this feature handles.
Owner and admin control
Keep billing, configuration, and higher-risk actions in the hands of the people who should actually control the workspace.
Manager access
Managers can operate assistants, review performance, and coordinate rollout without needing full unrestricted access to every billing or infrastructure setting.
Client scoping
Client teammates can be limited to assigned assistants and relevant conversations, which is essential for agency delivery and shared-account environments.
Private access
Protect private assistants and keep sensitive workstreams isolated when not every teammate should see every assistant or transcript.
Daily use
How teams use it after launch.
Shared conversation review
Multiple teammates can inspect the same inbox, compare difficult threads, and turn real conversations into operational decisions.
Team analytics
Use leaderboard and usage views to understand how assistants and teammates are performing instead of guessing who is handling what.
Lead and feedback handling
Share captured leads and visitor feedback across the workspace so follow-up lives where the conversation already happened.
Assigned assistant libraries
Map the right people to the right assistants instead of forcing every operator into every deployment regardless of expertise or responsibility.
Control points
What to keep controlled.
What you get
The changes teams should notice first.
- Better collaboration across support, sales, content, and digital teams
- Safer access control as more teammates and clients are invited in
- Cleaner ownership of assistants, inboxes, sources, and follow-up paths
- Less operational friction when AI becomes a team capability instead of a solo project
The facts do the selling
Plan facts, platform capabilities, and worked examples — every claim here is checkable, not a pitch.
White-label included — never a paid add-on. Copyright removal from $98/mo. Full white-label — custom domain, branded portal, your-domain emails — from $198/mo.
The white-label wedge
Platform fact
Training runs on your sitemap, PDFs, docs, and YouTube transcripts. Answers cite the source pages they came from.
Trained on your content
Platform fact
Five clients at $300/mo on a $198/mo Agency plan is $1,300+ of monthly margin before usage.
A 5-client agency on one flat plan
Worked example
Your questions, answered.
Tap any question about the product, pricing, security, or setup to see a straight answer.
InsertChat
Answers about InsertChat
Hi! Tap any question below and I'll answer it for you.
Team workspaces questions
Can client teammates be restricted to specific assistants?
Yes. Client-scoped access is meant to keep people limited to the assistants, sources, and conversations that belong to their website or account. The operational question is whether team workspaces makes the workflow clearer once real conversations, real ownership, and real edge cases show up. That is the bar teams should use before they expand the rollout across more assistants, more channels, or more teams.
Is this useful for agencies?
Yes. The workspace model is designed for shared delivery, client review, source updates, conversation inspection, and agency-style account management. The operational question is whether team workspaces makes the workflow clearer once real conversations, real ownership, and real edge cases show up. That is the bar teams should use before they expand the rollout across more assistants, more channels, or more teams.
Do managers need full admin access?
No. Managers can operate the workspace day to day without being given unrestricted access to every billing or infrastructure setting. The operational question is whether team workspaces makes the workflow clearer once real conversations, real ownership, and real edge cases show up. That is the bar teams should use before they expand the rollout across more assistants, more channels, or more teams.
Ready to get started?
Start your 7-day free trial. Review current trial terms.
7-day free trial