Separate client workspaces
Configure the right business, channels and permissions in each workspace. Keep one client’s knowledge and customer records out of another’s answers.
Built around your business
Different clients. Clear boundaries.
Keep each client’s customer support, approved knowledge and team access in the right workspace. Give the people doing the work a connected Inbox.
A connected support dayThe next person
The next person
gets the whole story.
Two clients have different return policies and brand voices. The support team needs the correct context for each business, every time.
Related history and a shared working Inbox help the team pick up the request with context. Internal Team conversations keep colleagues close to the answer.
Explore this part of Message →For AgenciesUseful work.
Useful work.
Clear next steps.
Build around the requests your team already handles. Start with the knowledge, channels and handoffs that make those conversations easier.
Build the client’s knowledge
Start with their website or an onboarding interview. Have the client review the content and policies before publishing them for AI.
Coordinate the delivery team
Discuss difficult requests in internal Team conversations. Give the colleague the customer thread and the specific question that needs an answer.
Make handover practical
Document the configured channels, knowledge ownership and next steps. Price each workspace and any additional services clearly in your client arrangement.
Teach it your businessGood answers start
Good answers start
with your knowledge.
Scan your website or answer the onboarding interview. Review the drafts, publish approved answers and set company-specific guidance for AI. Connect only the sources that belong in this workspace.
See how Message AI learns →“Which policy applies to this client?”
“Who should approve this answer?”
“What still needs attention before handover?”
Connected context
Bring the relevant tools.
Choose connections for your workflow. Open each guide to see its actual capabilities, required permissions and setup.
Start with one real requestMake the trial
Make the trial
look like your workday.
Connect one channel, publish a small set of approved answers and invite the people who will use the workspace. Test the experience from both sides of the conversation.
- Ask a routine question your team answers every day
- Try a request that needs customer verification
- Ask for a person and review the handoff
- Continue the request through a second channel
Before you start
A few useful answers.
Does AI arrive knowing our agencies business?
No. Build its knowledge from your approved information and connected sources. Review generated articles, configure company guidance and test your actual questions before enabling customer-facing replies.
Can a person take over?
Yes. Your team can handle requests that need judgment, authorization or information AI does not have. Use assignments, internal discussion and customer history to give the next person the context.
Does every connected system allow AI to make changes?
No. Read-only connections provide permitted information; they do not authorize refunds, cancellations, account changes or other actions. Check each connector’s capabilities and keep decisions with the appropriate person or system.
What does a workspace cost?
Chat, Tickets or Phones start at $5/month each with five human support agents included. Support is $10 and Business is $15. Additional services, AI add-ons and usage can be charged separately. The pricing page explains the starting costs.