Setting up and running your workspace

This guide explains what your organization's Sonzai workspace is, how it gets configured, who can touch what, and how to explain the system to your staff.

What you have

Sonzai provisions a dedicated tenant for your organization. That means:

• Your own workspace address (for example, yourcompany.sonz.ai).
• Your own data: conversations, client records, knowledge, and configuration are scoped to your tenant and are never shared with, or derived into, anyone else's.
• A configuration studio at platform.sonz.ai where authorized people shape what your team sees.
• A runtime your salespeople actually use: messaging channels (WhatsApp Business, Messenger) plus a simple web workspace.

There is nothing to install or host. Infrastructure, deployment, and monitoring are handled by Sonzai operators.

Who does what

Three kinds of people interact with the system, with strictly separated access:

1. Your salespeople use the runtime only: their secretary in the messaging channel, and the web workspace with their own prospects, conversations, advice, and outcomes. They never see integration credentials, agent configuration, or administration screens.
2. You (IT administrator), or a Sonzai FDE working with you, use the configuration studio. You can do everything listed in this guide. You cannot reach Sonzai's operator console; direct navigation to it returns access denied.
3. Sonzai operators provision tenants, manage deployment and licensing, and monitor platform health from a separate operator console. When an FDE works inside your tenant on your behalf, the session is delegated: it is time-limited, tenant-bound, audited, and shows a visible banner naming the operator, the tenant, and the reason. You can see these sessions in your audit view.

Signing in and adding your team

• Administrators sign in at platform.sonz.ai with your organization's single sign-on or a managed account.
• From Team & governance you can invite teammates, assign roles (administrator or member), reset passwords, and disable accounts.
• Salespeople get runtime accounts bound to their verified channel identity: each person messages the corporate bot from their own WhatsApp or Messenger identity, and the system binds that identity to exactly one advisor identity and record owner. One corporate number serves the whole team; nobody shares conversations or memory.

The configuration studio

The studio keeps to five destinations. Everything you can configure lives under one of them:

1. Home. Setup progress, runtime preview, health, and recent changes. The setup path is guided: choose the experience, apply branding and terminology, add knowledge, configure the copilot, connect a channel, invite your people, define outcomes, preview as a salesperson, go live. Every step shows its state and the next action.
2. Experience. Brand, terminology, which modules appear, forms and qualification fields, and a live preview. The platform carries more modules than any one team needs (CRM and pipeline, lead intake and qualification, conversations, knowledge, analytics, and others); you choose what your people see, what it is called, and in what order.
3. Intelligence. Knowledge and playbooks. Upload approved material (drag and drop), connect governed sources (website or sitemap, SharePoint, Google Drive, or an API/warehouse source), and manage the content lifecycle: draft, needs review, approved, published. Runtime answers cite the effective approved source, and public research can never create approved product or policy facts on its own.
4. Connections. WhatsApp Business and Messenger channel setup, CRM and external source connections, field mappings, and sync health. Credentials are write-only: once entered, secrets are never displayed back, and they never appear in anything a browser can read.
5. Team & governance. Users, roles, delegated access, approvals, audit, and releases.

Data and governance facts to relay to your staff

• Salespeople approve their own records; managers see aggregates, not raw notes, unless a named, logged, break-glass access is used for support or compliance.
• Each salesperson's conversations and memory are private to them; assignment rules control who sees which prospects.
• Your organization owns its data and everything derived from it. Nothing from your tenant trains models for anyone else.
• Consent handling, retention, and deletion behavior are configured with your data-protection officer before live client data flows.

Getting help

Your Sonzai FDE is the first line for configuration questions, with a named backup engineer. Operational issues are monitored by Sonzai; report anything you notice to your FDE or [email protected].