Plan workspaces, roles, seats and handoff shifts for your AI support team, then set them up in AI SNS CHAT without giving anyone more access than needed.
Most support teams start with one person and one chatbot, then add a colleague, a part-time helper and an agency, and nobody decides who can touch what. The result is a shared login, an accidental deletion or a customer chat that waits because no one knew it was theirs. This article walks through how to structure workspaces, roles and handoff shifts so your website chat, WhatsApp and Messenger channels stay safe as the team grows.
Why workspace structure matters before you add people
A workspace is the container for your agents, knowledge, channels and team. How you split it decides who sees which customer conversations and who can change which settings.
Three problems show up when this is left to chance:
- Shared credentials. When five people use one login, you cannot tell who edited an answer or removed a data source.
- Over-broad access. A person who only reads chat logs ends up able to change channel connections.
- Unclear ownership. Nobody knows who is responsible when a handoff alert fires at 2 a.m. in another timezone.
Decide the structure first, then invite people. It takes about an hour and avoids months of cleanup.
One workspace or several?
AI SNS CHAT lets one account hold several workspaces, which you switch between from the header. The question is when to split.
Keep a single workspace when one team runs one brand, with the same people answering for every agent. Split into several when any of these is true:
- You run separate brands or regional businesses with different teams.
- You are an agency or consultant managing work for clients.
- You want a staging area where a new agent can be built and tested before it goes near live customers.
- Different groups should not see each other's conversations.
Agents can be moved between workspaces, so the decision is not permanent. You can build in a test workspace and move the finished agent across when it is ready.
Roles: matching access to the job
AI SNS CHAT uses five roles: Owner, Co-owner, Member, Support and Viewer. On top of the role, you can override permissions for an individual member. The product materials describe 42 permissions in total, so there is fine-grained control when a role is close but not exact.
A practical way to think about it is by intent:
| Person | Starting role to consider | Why |
|---|---|---|
| Founder or account holder | Owner | Ultimate responsibility, including billing |
| Operations lead who shares admin work | Co-owner | Helps run the account without being the sole owner |
| Person who builds and tunes agents | Member | Works on agents and knowledge |
| Frontline person who answers handed-off chats | Support | Needs conversations, not configuration |
| Manager, auditor or stakeholder who only reviews | Viewer | Looks without changing anything |
Treat this table as a starting point and check the actual permission list for each role in your workspace before inviting people. Custom roles exist only as a Corporate-plan option and are hidden, so plan around the five standard roles plus per-member overrides.
The overrides rule
Start from the least access that lets the person do their job, then add permissions one at a time. Removing a permission someone is already relying on creates friction; granting an extra one later takes seconds.
Seats, agents and plan limits
Your plan sets how many people and agents a workspace can have. Using the shipped defaults (an admin can change them at runtime, so confirm on the pricing page):
| Plan | Agents | Seats |
|---|---|---|
| Free | 1 | 1 |
| Hobby | 2 | 2 |
| Standard | 3 | 3 |
| Pro | 5 | 5 |
| Corporate | 10 | 10 |
| Private AI | Unlimited | Unlimited |
An extra agent is available as an add-on at $10 per agent per month. Seats follow the plan, so count them before you design the team. If you have four people but a three-seat plan, decide who needs a seat and who can rely on alerts and reports instead.
Here is a hypothetical to make this concrete. Suppose a small shop has an owner, one product specialist and one part-time support person. Three seats cover them. If they later hire a fourth person, they either move up a plan or consolidate who logs in. Knowing this before hiring avoids surprises.
Handoff: who takes the chat when the AI steps back
Roles control access. Handoff controls responsibility. When the AI agent cannot or should not answer, a human has to pick up, and that human should be determined in advance.
- 01Customer asks for a person
- 02Agent escalates the chat
- 03Alert reaches the person on shift
- 04Human takes over and replies
In AI SNS CHAT, the Helpdesk section includes Scheduling, where you set shifts per person and timezone. Handoffs are auto-assigned to whoever is on shift. Alerts can be sent to Slack, Teams, LINE WORKS, WhatsApp, email or a webhook, so people are notified where they already work.
The customer also sees a message about what happens next. The server reads the rota and builds that line itself, and it never invents a wait time. That matters: promising "a reply in five minutes" when nobody is on shift damages trust faster than saying nothing.
Design your shifts around real coverage:
- List the hours each channel is active (website chat may run all day, WhatsApp only in business hours).
- Assign people by timezone so someone is on shift in each major market.
- Choose an alert channel each person actually watches.
- Test with a real handoff before announcing the setup to the team.
Accountability, security and handing over work
Once several people edit the same agents, you need a record of changes. AI SNS CHAT keeps a workspace activity log under Workspace settings → Activity, visible to owners and admins. It records every create, edit, delete or upload, with the name, email, feature and time. Each data source also shows who added it and who last edited it, so when an answer goes wrong you can trace the source in seconds.
Pair that with a few safety habits:
- Turn on two-factor authentication. Users can use TOTP, and admins can force it for everyone.
- Use API keys sparingly. They live under Workspace settings → API keys, are shown only once, can be revoked, and need Hobby or higher. Create one per integration so you can revoke a single key without breaking everything.
- Know your safety nets. Agents have restore points (up to 40 per bot), deleted agents wait in Trash for 30 days, and nightly downloadable backups keep the last seven snapshots.
- Review leavers promptly. When someone leaves, remove their access the same day and revoke any keys they created.
If you work with an agency, note how sub-admins are scoped: they are limited to their assigned clients, can open dashboards and run backups or restores, and deleting something requires a code emailed to the client. That gives the client the final say on destructive actions.
On compliance wording, be honest with your own customers: AI SNS CHAT practices are designed with reference to GDPR and APPI, and the site states it is not SOC 2, ISO 27001 or HIPAA certified. Do not promise your clients certifications the platform does not hold. Also, do not build your rollout around single sign-on, since it is not something you can rely on today.
Doing this in AI SNS CHAT
Here is the setup in order, from an empty account to a working team.
- Create your workspaces. Use the workspace switcher in the header to add one per brand, region or client. If you want a test area, create it now.
- Build or move agents. Create agents with the guided wizard, or move an existing agent across workspaces. Duplicate copies persona, model and training data but not conversations, which is handy for turning a proven agent into a regional variant.
- Invite people with the right role. Assign Owner, Co-owner, Member, Support or Viewer, then apply per-member permission overrides only where the standard role does not fit. Check your plan's seat count first.
- Secure the account. Ask everyone to enable two-factor authentication, and have an owner force it for admins. Create API keys under Workspace settings → API keys only if you have an integration that needs one.
- Set up shifts. If you are on Standard or higher, open Helpdesk → Scheduling and define shifts per person and timezone. Choose where handoff alerts go: Slack, Teams, LINE WORKS, WhatsApp, email or a webhook.
- Connect channels. Under Channels, deploy the chat widget on your website and connect WhatsApp or Messenger. See /connections for what is available.
- Test the handoff. Start a chat on each channel, ask for a person, and confirm the right teammate is alerted and can take over. When a human takes over a chat, the bot pauses.
- Review the activity log. After a week, open Workspace settings → Activity and check that the edits match what you expected.
If you get stuck at any step, Synthia, the AI fleet manager, is available from the sidebar and as a bubble on every dashboard page. She can give guided screen tours, navigating to the screen and highlighting the control. For plan details, see /pricing, and for the full capability list, see /features. When you are ready to start, go to /signup.
Frequently asked questions
Can one account manage several businesses?
Yes. One account can hold several workspaces, and you switch between them from the header. Agents can be moved between workspaces, so you can build in one and relocate the result.
What is the difference between Support and Viewer?
Support is intended for people who answer handed-off conversations, while Viewer is for people who only need to look. Check the permission list for each role in your workspace, and use per-member overrides if either one is not quite right.
Can I create my own custom roles?
Custom roles are a Corporate-plan option and are hidden by default. On other plans, use the five standard roles together with per-member permission overrides, which cover most teams.
How do I find out who changed an answer?
Open Workspace settings → Activity as an owner or admin. It lists every create, edit, delete or upload with name, email, feature and time, and each data source also shows who added it and who last edited it.
Do handoff shifts work on every plan?
Helpdesk, which includes Scheduling, needs Standard or higher. On lower plans, you can still take over chats manually, but automatic assignment by shift is not available.


