1. Overview
Sonar is Vivid's enterprise predictive intelligence platform. It helps businesses anticipate what their customers will do next: who is ready to come back, who is drifting away, and when to reach them on the channel they answer. You can see Sonar running on the Sonar page.
The Sonar connector for Claude brings Sonar into your Claude conversations. Once connected, you can ask Claude about your clients, campaigns, templates and audiences in plain language, and have Claude prepare changes in Vivid for you to review. Claude works through the connector as your Vivid account, with that account's permissions, and nothing changes in Vivid until you have seen a preview and said yes.
The connector is a remote MCP (Model Context Protocol) server operated by Vivid Algorithms W.L.L.
2. Who can use it
- Vivid team accounts (platform administrators): available now.
- Client accounts Coming soon: businesses using Sonar, signing in with their own Vivid login and limited to their own business.
Until client access is released, the capabilities below describe what a Vivid team account can do. When client accounts are enabled, each client user will see only their own business and only the actions their role in Vivid allows.
3. Prerequisites
- A Claude plan that supports connectors.
- An active Vivid account. If your organisation uses Claude Team or Enterprise, an organisation Owner may need to make the Sonar connector available before members can connect it.
- Permission in Vivid for the work you want to do. The connector never grants more access than your Vivid account already has.
4. Connecting with OAuth
The connector uses OAuth, so you sign in to Vivid directly and never paste a password or API key into Claude.
- In Claude, open Settings → Connectors and find Sonar.
- Select Connect. Claude opens Vivid's sign-in page in a new window.
- Sign in with your Vivid account.
- Review the access request and approve it. You are returned to Claude.
- Start a new conversation and ask: "Which Vivid account are you signed in as?" Claude replies with your account, what it can do, and any areas of Vivid it cannot reach.
You can turn the connector's tools on or off per conversation from the tools menu in Claude.
5. What you can do
Reading is always free: questions never change anything in Vivid. Anything that would change Vivid is prepared first and only happens after your confirmation (see section 8).
| Area | What you can ask about or prepare |
|---|---|
| Clients | Look up a client's details, status, switches, onboarding progress, message usage and cost; prepare updates to client details and broadcast allowances. |
| Campaigns | List campaigns and compare how each performed (messages attempted, delivered and replied to); prepare a WhatsApp broadcast campaign, or stopping one. |
| Templates | List WhatsApp templates and their approval status, see which templates perform best and which are broken; prepare a new template. |
| Audiences | Age and gender breakdown of a client's customers with reply rates; why a reachable audience is smaller than expected; what the recommendation engine did on a specific generation and why customers were excluded; saved contact lists. |
| Sending rules | The rest period, monthly cap per person and fatigue-safe selection a client sends under, which rules are shared with other branches, and the side effects of changing them; prepare a setting change. |
| WhatsApp health | The live state of a client's WhatsApp number, read from Meta: display name approval, quality rating, registration, and whether Sonar is receiving messages. |
| AI agents (Agent Factory) | A client's AI agent status, knowledge, options and test results; prepare setup, knowledge and business-detail changes and test runs; prepare publishing, rollout, pause and rollback (these also need your approval in Vivid). |
| Platform overview | Which clients need attention, recent background failures and their causes, open support tickets, and recent team activity. Vivid team accounts only. |
| Team workspace | Your own tasks, meetings, follow-ups and inbox; find free time and prepare meetings; create tasks; look up sales leads and stalled deals. Vivid team accounts only. |
6. Example prompts
- "How did Acme's campaigns perform over the last 30 days, and which template got the most replies?"
- "Why is Acme's reachable audience smaller than they expect? What would it look like with a 72-hour rest window?"
- "Prepare a WhatsApp campaign for Acme using the approved eid_offer template, to customers who visited in the last 90 days, scheduled for Thursday at 10:00 Bahrain time." — Claude shows who it would really reach after Vivid's safety rules and the estimated cost. Nothing is sent until you confirm.
- "Is Acme's WhatsApp display name approved, and what is the number's quality rating?"
- "What needs my attention across the platform today?"
7. Permissions and tenant isolation
- The connector acts as you. Every request runs as the Vivid account you signed in with and is checked against that account's permissions in Vivid. Claude cannot reach areas of Vivid your account cannot.
- Tenant isolation. Vivid separates clients' data through tenant-scoped application and database access controls, as described in Schedule C of our Terms of Service. The connector uses those same controls; it does not have a separate path to the data.
- No credentials in the conversation. No connector tool asks for or accepts a password, API key or secret. Access is granted through the OAuth sign-in only.
- High-risk actions stay in Vivid. Some actions need you to press Approve inside Vivid itself, so they cannot be completed from a conversation alone (see section 8).
8. Confirmation of sensitive actions
Every change follows the same three steps:
- Prepare. Claude asks Vivid to prepare the change. Vivid returns a preview: what would change, who it would affect and, for campaigns, how many people it would really reach and what it would cost. Preparing changes nothing.
- Review. Claude shows you the preview.
- Confirm. Only after you clearly say yes does Claude confirm the change, and only then does it happen in Vivid.
Safeguards around that flow:
- A preview can be confirmed once. It expires after 15 minutes, and Vivid refuses it if the underlying numbers have changed since it was prepared. Claude then prepares a fresh one.
- You can tell Claude to cancel a prepared change at any time; cancelling changes nothing in Vivid.
- Some confirmed changes can be undone shortly afterwards: a newly created task (within 10 minutes, if nobody has touched it), a sales-lead change, or a client sending setting. Other changes are reversed by preparing the opposite change.
- Publishing, rollout, pause and rollback of an AI agent, and granting the Odoo bookings permission, carry an approval link. You must press Approve in Vivid before the change can be confirmed, and Vivid may hold it for a second administrator.
- Once a campaign is confirmed, real messages are sent and cannot be recalled. Read the preview carefully.
9. Security and data handling
- Connections between Claude and the Sonar connector are encrypted in transit with TLS.
- The connector returns only what you ask for, within your account's permissions. Results appear in your Claude conversation; how Anthropic handles your conversations is governed by your agreement with Anthropic.
- Vivid processes client data as described in our Privacy Policy and Terms of Service, including the data processing addendum in Schedule C.
- To report a security concern, email support@vividsystems.co.
10. Disconnecting
- In Claude, open Settings → Connectors.
- Find Sonar and select Disconnect.
Claude can no longer reach Vivid on your behalf. Prepared changes you never confirmed expire on their own after 15 minutes. Changes you already confirmed stay in place in Vivid. To have Vivid revoke the connection on its side too, email support@vividsystems.co.
11. Troubleshooting
| Problem | What to do |
|---|---|
| Sonar does not appear in Connectors | Your organisation's Claude Owner may need to make it available. Otherwise contact support. |
| Sign-in fails or your account is not recognised | Make sure you are signing in with an active Vivid account. Client accounts are Coming soon. |
| Claude says it cannot reach part of Vivid | That area is outside your account's permissions. Ask "Which Vivid account are you signed in as?" to see what your account can do, and ask your Vivid administrator if you need more access. |
| A confirmation is refused | The preview expired (after 15 minutes), was already used, or the numbers changed. Ask Claude to prepare it again. |
| A publish, rollout, pause or rollback will not go through | Press Approve on the link in the preview, inside Vivid. It may also be waiting for a second administrator. |
| A client cannot be found | Partial names work. Try the client's reference, or check the spelling. |
| The tools stopped responding | Disconnect and connect Sonar again (sections 4 and 10). If it continues, contact support. |
12. Support
Email support@vividsystems.co. Include what you asked Claude, roughly when, and the Vivid account you were signed in as. Never send a password.
Related documents: Privacy Policy · Terms of Service · Data Deletion Instructions