Setup overview
Configure a ClientSphere workspace in the order the features depend on each other, and know which steps are optional.
These pages are for the person who administers the workspace. Most need a role with Manage integrations or Manage company settings; if a Settings section is missing for you, that is why.
The order that matters
Five steps depend on each other, and doing them in this order means nothing waits on something later. They are the same five as the Quick start, with the full detail behind each.
- Create your workspace and invite your team. Roles decide what people can see, so set them before inviting.
- Set up email sending. Verify a domain and add a sending address. Broadcasts, sequences, transactional email, and ticket replies all wait on this, and DNS takes time, so start it early.
- Connect a support inbox and a sales inbox. Forwarded mail becomes tickets and sales conversations.
- Working hours, SLAs and assignment. Without working hours, every overnight ticket breaches before anyone is in.
- Import your data, so the team starts with real accounts and contacts rather than an empty CRM.
Everything after that can be done in any order, when you need it.
Workspace
Create your workspace and invite your team
Sign up, create the company, invite people with a role, and what a role shows and hides.
Customise your CRM
Pipeline stages, account and task statuses, and ticket modules. Set them before the data arrives.
Import your data
Accounts and contacts from a CSV with column mapping, or from Zoho CRM.
Audit trails
What changed, who changed it, and how to search the record.
Email and inboxes
Set up email sending
Verify a domain, publish its records, create a sending address. Everything that sends waits on this.
Connect a support inbox
Turn a support address into tickets: create the channel, forward mail to it, confirm.
Connect a sales inbox
The same for inbound sales email, so it lands in the Sales Inbox with an SLA.
Working hours, SLAs and assignment
The hours the SLA clocks run, response targets per channel, and how new items get an owner.
Connect Gmail
Link a personal mailbox to send from it and log conversations, and control what is synced.
Your site and product
Put the Support Hub on your site
Create a support channel, choose the cards visitors see, and get the embed code.
Put the floating launcher on your product
The pill button and its menu, installed with the user's identity so Product Analytics fills up.
Publish your knowledge base
Public access, who can publish, branding, and your own domain.
AI and developers
Turn on AI
Every AI switch in one place, and the order to turn them on so it answers well and stays quiet when it should.
API keys, logs and MCP
Issue and scope keys, watch their requests, and connect an AI assistant to your data.
Sandbox mode and test data
What sandbox is, how to get a test API key, and how to clear test data.
When something is not working
Every guide ends with a When it goes wrong section listing the exact messages the screen shows and what each means. If a page in the app is unexpectedly empty, the usual causes are a missing prerequisite from the list above or a role without the permission; the guide for that screen says which.