AI ASSISTANTS
Can I just ask Claude what my team told the customer?
Yes. Connect Claude, ChatGPT, Claude Code or Cursor to WAOversight and ask it, in your own words, what is waiting, what a customer was told and who read what. It signs in as you, it reads what you can read, it never sends, and every read is written to the access audit under your name.
WAOversight is an MCP connector: Claude, ChatGPT, Claude Code, Cursor and any assistant that speaks MCP can sign in with your own WAOversight login and read what you can read: conversations, deleted messages, the queue, analytics and the access log. It cannot send a message or change anything, and every read is in the access audit under your name.
WHAT YOU CAN ASK
The questions you already type, answered from the record.
Each of these is a prompt as a manager types it. The assistant chains the reads it needs, every one audited, and answers in the chat you are already in.
Daily oversight
- “What is waiting on my team right now, worst first, and who has had it longest?”
- “Give me the morning review for the showroom team: the queue, the escalations nobody answered, and yesterday against last week.”
- “Which missed calls from customers were never returned this week?”
The queue, the escalation notices, the team scorecard and the call log. Drafting the 3 reminders you should send your reps today is the assistant's job. Sending them is yours.
Customer history
- “Everything we have ever said to Hudson Cotton, across all 3 reps who handled them, with the deleted messages.”
- “Before my call with Jordan M.: summarise the last 40 messages and anything Nora flagged.”
- “Which of our top customers had no reply from us for 3 days?”
Contacts, each thread with its deleted originals and its edits, Nora's assessment of it, and the coverage board.
Disputes, HR and audit
- “Show me every message that mentions a discount above 20% in October, and which rep sent it.”
- “Export the Jordan M. thread for the dispute, with proof it has not been altered.”
- “Who has read Marcus Webb's conversations in the last 30 days, and from where?”
Search, the evidentiary export with its hash chain, and the access log, which owners, admins and auditors can read. When a rep resigns, ask which customers they were talking to, which threads are open and who holds the number now.
Coaching
- “Prepare my one-on-one with Hannah: her reply times against the team, coverage of her book, the rules she tripped, and one good and one bad example thread.”
- “Which reps answer outside business hours, and is it helping?”
The rep profile, the trends, the hour-by-hour pulse, rule analytics and the threads themselves.
Routines across your connectors
- “Every weekday morning, run the morning review and post it to the sales-ops channel.”
- “For the deals closing this month, which have had no WhatsApp reply in the last 3 days?”
- “Put this month's scorecard per rep in my team sheet.”
The assistant's own scheduled tasks and its Slack, HubSpot or Sheets connectors do the posting; ours only reads. A thread carries its CRM record, so the assistant can join deals to chats without anything being written into the CRM.
WHAT IT READS, AND WHAT IT NEVER DOES
As you, read-only, on the record.
An assistant is a second way of reading the archive, with the same login, the same limits and the same audit as the dashboard. These are the rules it runs under.
| What happens | When | |
|---|---|---|
| Who it reads as | Your own login. A manager's assistant sees that manager's teams, an auditor's reads, an owner's sees the workspace. There is no workspace key and no account for the assistant itself. | Every call |
| What it can read | Conversations with deleted originals and edit history, search, contacts and groups, the queue, cases, coverage, analytics, calls, Nora's findings, rules, escalations, exports and the access log. Files as a list with a sign-in link, never the file itself. | 31 read-only tools |
| Sending | Never. There is no tool that sends, replies, assigns, dismisses or escalates. A reply is still written by the rep on their own phone. | Never |
| Changing anything | Never. It cannot triage an item, change a setting or mark a customer. It reads. | Never |
| The access audit | Every read is written first, as the dashboard writes it, naming the assistant and you. If the row cannot be written, the assistant gets an error and no content. | Before any data |
| What leaves, and to whom | What you ask for goes to your assistant's provider under your own account's terms with them. Nothing is redacted: you asked for the customer by name. WAOversight keeps nothing the assistant asked or answered. | Your provider |
| Who switches it on | An owner or admin, at Settings › AI assistants, after accepting what that means. Off ends every connection at once. | Owner or admin |
| How much it may read | A daily cap the owner sets, 5,000 calls by default, and a rate for each connection. Past either, the assistant is told to wait. | You set it |
| Ending a connection | You, from Your account, or an owner or admin from Settings › AI assistants. It ends on the assistant's next request. So does a password change. | Any time |
HOW YOU CONNECT
One address, your own sign-in, in the assistant you already use.
Every assistant takes the same server address and then sends you to WAOversight to sign in and allow it. Each person connects their own; an owner cannot connect one for someone else.
Claude, on the web, desktop, mobile and in Cowork
Open Customize › Connectors, choose Add custom connector and paste the address. Claude sends you to WAOversight to sign in and allow it. Once WAOversight is in the Claude directory, you will find it there instead. On a Team or Enterprise plan an owner adds it for the organisation, and each member connects with their own login.
Claude Code
Run the command in a terminal, then /mcp to sign in.
claude mcp add --transport http waoversight https://mcp.waoversight.com/mcpChatGPT
Open Settings › Connectors › Advanced, switch on Developer mode, choose Create and paste the address. On a Business or Enterprise workspace an admin creates it. Once the plugin is listed in ChatGPT's directory, you will find it there.
Cursor and VS Code
Add the server to your mcp.json and sign in when the editor asks.
{ "mcpServers": { "waoversight": { "url": "https://mcp.waoversight.com/mcp" } } }Microsoft 365 Copilot and Gemini Enterprise
Both connect through their admin centres: ask your administrator to add the server address there. Every assistant signs in as one WAOversight login and reads only what that login can see.
Before any of this works, an owner or admin switches AI assistants on at Settings › AI assistants. Until then an assistant that connects is refused, and told why. The step-by-step for each client, the caps and the troubleshooting are on connecting an AI assistant.
What a connection is
Your assistant asks WAOversight for a sign-in, and WAOversight shows you a page that says exactly what you are allowing: which assistant, where its code goes, as which login, and what it may read. An app that calls itself Claude but sends its code somewhere else is shown as unverified, so you can refuse it.
Allow it, and the assistant reads as you: the same teams, the same threads, the same limits as your dashboard. A manager's assistant cannot see a team the manager does not manage, and the reply says nothing about that team's existence. Reps have no login, so no rep's assistant can connect.
It is signed in for an hour at a time and can stay connected for up to 90 days without asking you again. Change your password, and every connection ends on its next request. Each connection is listed under Your account, and on Settings › AI assistants for an owner or admin, with when it was made and when it last read. You are emailed when one is made, with the assistant's name and where it connected from.
What leaves, and to whom
This is not Nora. Nora reads on your workspace's own provider, under a key the owner chose and a disclosure the owner accepted, with identifiers redacted first. An assistant is yours: what you ask it for is sent to its provider, Anthropic, OpenAI or whoever runs it, under your own account's terms with them, and nothing is redacted, because you asked for the customer by name and the reply is your own read.
So there are 2 acknowledgements. The owner accepts, at switch-on, that members may connect assistants whose providers receive what those members ask for, with WAOversight not party to that agreement. Each person accepts the same at consent, for their own assistant. Both are versioned, and a changed wording asks again.
WAOversight keeps nothing from the exchange. What you asked and what the assistant answered stay with you and your provider. The settings page shows counts, by day and by person, and the access audit shows which reads were made.
What the owner controls
The switch. AI assistants are off until an owner or admin switches them on at Settings › AI assistants and accepts the acknowledgement. Off ends every connection at once, and on again starts from none. A workspace that is closing cannot switch them on.
The daily cap. The most calls every assistant in the workspace may make in one day, on the workspace's clock: 5,000 by default, anywhere from 100 to 1,000,000. Past it, every assistant is told to wait until tomorrow. Each connection is also held to 60 calls a minute and 1,000 an hour, which the cap does not change, so one assistant stuck in a loop cannot spend the day's allowance.
Every connection, with Revoke. Who, which assistant, what it may read, when it was made and when it last read. Revoking ends it on the assistant's next request. The operator console can end a connection too, with a reason recorded in your workspace's own admin log, and sees it as metadata only.
It needs a subscription. An assistant reads a workspace on a live subscription or its trial, on every plan: there is no plan that has it and no plan that lacks it. A workspace with no card on file is refused, and the assistant is told why.
What this does not do
- It never sends. Not a reply, not a reminder, not a notice. The only WhatsApp message WAOversight sends is an escalation notice to your own rep, and no tool reaches that path.
- It never changes anything. It cannot assign, dismiss, snooze or escalate an item, open or close a case, mark a customer, or change a rule or a setting.
- It is not Nora, and it does not run Nora. It can read Nora's findings; it does not make them, and nothing an assistant says is written into your queue.
- It does not hand over a file. Attachments come back as a list with a sign-in link, and opening one is a dashboard read, audited as one.
- It does not read past your login. A manager's assistant sees that manager's teams and nothing more, and a rep has no login to connect.
- It does not keep what you asked. Counts only. What left for your provider, and what the provider keeps, is between you and them.
- It is only as current as capture. It reads the archive, so a number that dropped its link is reported as such, and nothing that was missed appears. Every figure it quotes is the dashboard's own, defined in the metrics guide.
QUESTIONS
What managers ask about AI assistants
Can I connect Claude or ChatGPT to my team's WhatsApp conversations?
Yes. WAOversight is an MCP connector: in Claude, add https://mcp.waoversight.com/mcp as a custom connector; in ChatGPT, create it under Developer mode; Claude Code and Cursor take the same address. Sign in with your own WAOversight login and the assistant reads what you can read, never sends, and every read is in the access audit under your name. An owner or admin switches it on first.
Which assistants work?
Any that speaks MCP over HTTP with a sign-in: Claude on the web, desktop and mobile and in Claude Code, ChatGPT with Developer mode, Cursor and VS Code, and Microsoft 365 Copilot and Gemini Enterprise through their admin centres. The address is the same for every one.
What does the assistant's provider receive?
Whatever you ask for, as the dashboard would show it to you: names, numbers and message text included, nothing redacted. It goes to your assistant's provider under your own account's terms with them, not under the workspace's agreement with us. The owner accepts that at switch-on, and you accept it when you connect.
Can it send a message or reply for me?
No. There is no tool that sends, and no linked number can send through WAOversight. The assistant can draft the reminder you want to send your reps; sending it is yours.
Can my team see that my assistant read their chats?
A read by your assistant is written to the access audit before any data returns, under your name and the assistant's, the same row a dashboard read writes. The owner and any auditor read that log. Nothing is sampled and nothing is left for later.
Who can connect one?
Anyone with a WAOversight login: owners, admins, managers and auditors. Each person connects their own, as themselves; an owner cannot connect an assistant for someone else. Reps have no login and cannot connect.
Does it cost extra?
No. AI assistant access is on every plan, for a workspace on a subscription or its trial. Your assistant's provider bills you as it already does; we add nothing and meter nothing beyond the daily cap the owner sets.
How do I end a connection?
From Your account, where your own are listed with Revoke. An owner or admin ends anyone's from Settings › AI assistants, or ends every one by switching assistants off. Changing your password ends them too. Each ends on the assistant's next request.
My team will think I don't trust them.
Then tell them, which you have to do anyway. Nothing here is hidden from your team: they are told which numbers are archived and why, before you link one. Your own reading is on the record too, because every manager view is written to an access log that your workspace owner and your auditors can read, and that nobody can edit or switch off. Send them our employee page before you roll it out.
Ask the question. Get the record.
Switch AI assistants on, paste one address into the assistant you already use, and the next question you type is answered from your company numbers, on the record.
WAOversight is an independent product and is not affiliated with or endorsed by WhatsApp or Meta.