What you bought, and how to see it working

You are not buying a chatbot. You are buying a system that turns your sales force's daily conversations into records, follow-through, and organizational intelligence your company owns. This page explains what runs, what you can see, and how it is governed.

The one-paragraph version

Every salesperson gets an AI secretary in the messaging app they already use. After a client meeting they talk to it the way they would text a colleague. The system structures what they said into a client record, schedules the follow-up, and answers product questions from your own approved documentation. Each approved record also compounds into an asset your organization owns: client histories, working playbooks from your best people, and the data foundation for lead prioritisation and next-best-action.

What your people see

• Salespeople work in WhatsApp or Messenger, plus a deliberately simple web workspace with five areas: today's priorities, their prospects and clients, their conversations, advice, and outcomes. No CRM forms, no admin screens.
• Your IT team (or a Sonzai engineer working with them under audited, time-limited access) configures everything in a studio at platform.sonz.ai: branding, which modules appear, knowledge, channels, and team access.
• You see the aggregate view: activation, capture volume, follow-up completion, and pipeline state, reported against the baselines agreed before launch.

What you can measure

The system is instrumented for the questions a sales leader actually asks:

• How many of our people used it this week, and is that growing?
• How many client conversations became records instead of disappearing?
• How fast does a meeting turn into a logged follow-up, and do follow-ups happen on time?
• What is moving in the pipeline, and which recommendations get accepted?

Pilots are measured against a baseline week and pass/fail thresholds agreed in writing before launch, so the readout is evidence, not anecdotes.

How it is governed

• Your data is yours. Raw notes, records, documents, outcomes, and everything derived from them belong to your organization, are exportable in open formats, and are never used for another customer or to train shared models.
• Salespeople trust it because the rules are written down. They approve every record; managers see aggregates with minimum group sizes; nothing captured feeds individual performance evaluation during a pilot; raw-note access is named, logged, break-glass only.
• Privacy is designed before live data. Lawful basis, consent, retention, and deletion are worked through with your data-protection officer up front. The system never records live client conversations; it structures what your salesperson dictates afterward.
• Humans decide. The system drafts, structures, reminds, and recommends. It does not make underwriting, eligibility, pricing, or any adverse client decision.
• Access is separated and audited. Salespeople cannot reach administration. Your IT cannot reach Sonzai's operator console. When a Sonzai engineer works inside your tenant, the session is time-limited, tenant-bound, visibly bannered, and audited.

Procurement facts

• Vendor: Sonzai Labs Pte. Ltd. (Singapore). Applied AI company; the platform is the Sonzai Mind Layer; delivery is by forward-deployed engineers from Singapore and Manila.
• Deployment: a dedicated tenant provisioned by Sonzai, on your own workspace address. Nothing for your team to host. Dedicated placement options exist for organizations that require them.
• Model usage: your own provider keys are supported; provider charges are paid by you directly to the provider. Sonzai does not resell compute.
• Commercials: engagements start with a fixed-fee design sprint and a gated pilot, then a production subscription (an annual platform license plus per-seat pricing for monthly active users, so inactive seats cost nothing). Figures live in your pricing schedule.
• Exit: full export in open formats within 30 days of request, and deletion with a certificate, including backup expiry.

How an engagement runs

1. Design sprint (weeks, not months). Channel and privacy architecture settled with your DPO and IT, a working prototype in the hands of a friendly group, and a budget-ready readout.
2. Pilot (12 live weeks). A named cohort, measured against the baseline, with a written go or no-go gate before it starts.
3. Production. Rollout in tranches, with the intelligence layer (prioritisation, next-best-action, after-sales triggers) switching on as your outcome data supports it.

Questions or a walkthrough of the dashboard on your own data: [email protected].