Skip to main content
Sign in Menu

Connect your AI assistant to AllVoices

Annie Meadows
  • Updated

Overview

AllVoices MCP lets you work with AllVoices from inside the AI assistant your company already uses: Claude, ChatGPT, Gemini Enterprise or Microsoft 365 Copilot. Ask questions about your cases, pull together reports, and create cases without leaving the chat.

MCP (Model Context Protocol) is an open standard that lets AI assistants connect securely to business tools. AllVoices MCP gives your AI assistant the same access you already have in AllVoices, and nothing more.

To get started you need three things: MCP turned on for your AllVoices account (ask your Customer Success Manager), an enterprise plan for your AI tool, and your AI tool admin to add the AllVoices connector.

What you can do

At launch, your AI assistant can read anything you can see in AllVoices and take one write action: create a new case.

Action Type What it does Try asking
Search and look up cases Read Find cases by keyword, status, date, type or owner "Show me open harassment cases from the last 60 days."
Get a case summary Read Pulls the case details, notes, tasks, files, workflow steps and activity "Catch me up on case 202609-0020."
See your inbox at a glance Read Counts of open, overdue, unassigned and new cases "How many cases are overdue right now?"
See your tasks Read Your open tasks across all cases "What tasks do I have due this week?"
Analyze trends Read Spot patterns across the cases you have access to "Summarize the themes in our cases this quarter for my leadership update."
Create a case Write Opens a new case and fills in the form from what you give it, like a document, notes or a chat thread "Create a case from this email."

What it can't do yet. Your AI assistant can't add to, edit or delete existing cases, change a case's status, reassign cases, or message reporters. We're adding actions gradually and will share updates as they become available.

It works with your other tools. Because your AI assistant may also be connected to tools like email, Slack or your document storage, you can combine them. For example: "Create a case from my Slack conversation with Jordan today," or "Turn our open case summary into a slide for Thursday's leadership meeting."

Before you start

Setup takes two people: someone who owns your AllVoices account and the admin for your company's AI tool. Check these off before you begin.

  • MCP is turned on for your AllVoices account. It's off by default. Ask your Customer Success Manager to turn it on.
  • Your company is on an enterprise plan for your AI tool. Claude Team or Enterprise, ChatGPT Business or Enterprise, Gemini Enterprise, or Microsoft 365 Copilot with Copilot Studio.
  • You know who your AI tool admin is. Every tool below needs an admin to add AllVoices once before anyone can use it.
  • Your IT or security team has signed off, if your company requires approval to connect AI tools to business systems. The security section below covers what they'll want to know.
  • Each person who'll use it has an AllVoices login. People connect with their own AllVoices account and only see what that account can see.

You'll need the AllVoices MCP server address during setup: [AllVoices MCP URL]. Your Customer Success Manager can also share it.

Set up your AI tool

In every tool, an admin adds AllVoices once for your company. Then each person connects with their own AllVoices login.

AI tool Plan needed Who adds AllVoices Setup effort
Claude Team or Enterprise An Owner or Primary Owner Light
ChatGPT Business or Enterprise A workspace admin or owner Light
Gemini Enterprise Gemini Enterprise A Google Cloud or Workspace admin Moderate
Microsoft 365 Copilot Microsoft 365 Copilot with Copilot Studio IT, by building a Copilot Studio agent Heavier

Claude (Team and Enterprise)

Admin steps (one time). On Team plans, only Owners and Primary Owners can add a custom connector. On Enterprise, people with a custom role that includes Manage access to Libraries can too.

  1. Go to Organization settings > Connectors.
  2. Click Add, hover over Custom, then select Web.
  3. Name the connector AllVoices. This is the name your team will see.
  4. Paste the AllVoices MCP server address, [AllVoices MCP URL], and click Continue.
  5. Review the authentication settings Claude detects and click Continue.
  6. Under Authentication, choose a sign-in option (not "No sign in"). Under OAuth client, keep the recommended option unless your Customer Success Manager tells you otherwise.
  7. Click Add.

Steps for each person.

  1. Go to Customize > Connectors.
  2. Find AllVoices in the list. It usually has a "Custom" label.
  3. Click Connect, sign in with your AllVoices account, and approve access.
  4. In a chat, click + in the lower left, then Connectors, and switch AllVoices on for that conversation.

ChatGPT (Business and Enterprise)

ChatGPT calls connected tools "apps." Full MCP support, including write actions, is in beta for Business and Enterprise plans and works on ChatGPT web only, not mobile.

Admin steps (one time). Only admins and owners can turn on developer mode and publish an app.

  1. Turn on developer mode. In Workspace Settings, go to Permissions & Roles > Connected Data and switch on Developer mode / Create custom MCP connectors. On Business plans, each admin turns this on for themselves.
  2. Go to Workspace settings > Apps > Create.
  3. Name the app AllVoices and enter the server address, [AllVoices MCP URL].
  4. Choose OAuth for authentication.
  5. Click Scan Tools. When prompted, sign in with your AllVoices account, then wait for the scan to finish.
  6. Click Create. The app is saved as a draft so you can test it.
  7. Test it: open a new chat, pick AllVoices from the tools menu, and try a few prompts from the table above.
  8. Publish it: go to Workspace settings > Apps > Drafts and click Publish.

On Enterprise, you can also choose which groups get access and which AllVoices actions are allowed before you publish, for example read only.

Steps for each person.

  1. Start a chat on ChatGPT web and select AllVoices from the tools menu, or mention it in your message.
  2. Sign in with your AllVoices account the first time.
  3. When ChatGPT asks you to confirm a write action, like creating a case, review it and approve.

When AllVoices adds new actions. ChatGPT keeps a snapshot of the actions it approved. Your admin needs to refresh the app (Enterprise) or recreate and republish it (Business) to pick up new ones. We'll let you know when that's needed.

Gemini Enterprise

Google's custom MCP connection is a preview (pre-GA) feature, so the steps and screens may change. Gemini needs a few extra sign-in details from AllVoices. Ask your Customer Success Manager for these before you start:

  • Authorization URL: [AllVoices authorization URL]
  • Token URL: [AllVoices token URL]
  • Client ID and Client Secret: [provided by AllVoices]
  • Scopes: [AllVoices scopes]

Admin steps (one time), Business edition.

  1. Sign in to Gemini Enterprise at business.gemini.google.
  2. Click Settings & help, select your team, then go to Manage team > Connected apps.
  3. Click Add MCP Server.
  4. Enter the server URL, [AllVoices MCP URL], and name it AllVoices. Click Next.
  5. Under Authentication settings, choose OAuth 2.0 and enter the sign-in details from AllVoices.
  6. Click Verify Auth, then Continue.
  7. Choose a location for the data connector, give it a name, and click Add.
  8. Turn the connection on. New MCP connections are off by default and stay hidden from your team until you enable them.

On Gemini Enterprise Standard or Plus editions, the setup runs through the Google Cloud console instead, and your organization's policy may block custom MCP servers until a Cloud admin allows them. Your Customer Success Manager can walk your Google admin through it.

Steps for each person.

  1. In Gemini Enterprise, select the AllVoices connector.
  2. Sign in with your AllVoices account when prompted.
  3. Ask your question or request.

Microsoft 365 Copilot

Microsoft 365 Copilot connects to MCP servers through an agent your IT team builds in Copilot Studio. Your team then uses AllVoices through that agent. The consumer Copilot app doesn't support MCP.

IT steps (one time).

  1. In Copilot Studio, create an agent for your HR or ER team, or open an existing one.
  2. Go to the agent's Tools page and select Add a tool > New tool > Model Context Protocol. This opens Microsoft's MCP onboarding wizard.
  3. Enter the server name AllVoices, a short description (for example, "Look up, summarize and create employee relations cases in AllVoices"), and the server URL, [AllVoices MCP URL].
  4. Choose OAuth 2.0 for authentication. Select Dynamic discovery if it's available. Otherwise choose Manual and enter the sign-in details your Customer Success Manager provides: [AllVoices client ID, client secret, authorization URL, token URL, refresh URL].
  5. Select Create. If Copilot Studio shows a callback URL, send it to your Customer Success Manager so AllVoices can register it.
  6. On Add tool, select Create a new connection, then Add to agent.
  7. Publish the agent to the places your team works, such as Microsoft 365 Copilot or Teams.

If your company uses Power Platform data policies, they also apply to this connection, so make sure the AllVoices connector is allowed.

Steps for each person.

  1. Open the AllVoices agent in Microsoft 365 Copilot or Teams.
  2. Sign in with your AllVoices account when prompted.
  3. Ask your question or request.

How security works

AllVoices MCP checks every request against your AllVoices account before it touches any data, and it records what happens.

  • Off until you ask for it. MCP is turned off for every company by default. We turn it on for your company only when you request it.
  • Secure sign-in. You sign in to AllVoices through a standard OAuth flow. Your AI tool never sees your AllVoices password. It gets an access token tied to your account.
  • Permission checks on every request. Before anything happens, AllVoices confirms MCP is on for your company, the action is allowed, and your role permits it.
  • Your company's data only. Your AI assistant can only reach your company's AllVoices data, never another customer's.
  • Limited actions. At launch, the only write action is creating a case. Existing cases can't be added to, edited, deleted or closed through MCP.
  • Recorded. Actions taken through your AI assistant appear in the AllVoices activity log under your name.
  • You stay in control. Disconnect at any time, and your AI assistant immediately loses access.
  • Built on an open standard. MCP is the open standard that Anthropic, OpenAI, Google and Microsoft use to connect their AI tools to business systems.

If your IT or security team needs more detail for a review, ask your Customer Success Manager for our security and data-flow overview: [link to security overview].

How permissions work

Your AI assistant works as you. It signs in with your AllVoices account and gets exactly your AllVoices permissions. There's no separate AI access level.

  • It only sees what you can see. If you can open five cases in AllVoices, your AI assistant can see those five and nothing else.
  • It can only do what your role allows. If your role can't create cases, your AI assistant can't either. On top of that, it's limited to the actions listed in What you can do.
  • Trends and summaries stay within your access. When you ask about patterns, it only looks across cases you're allowed to see. It never sees another company's data.
  • Everyone connects separately. When an admin adds AllVoices to your AI tool, that doesn't give anyone access to AllVoices data. Each person signs in with their own account.
  • Role changes carry over. Because access is checked against your AllVoices account, changing someone's role in AllVoices changes what their AI assistant can see and do.
  • Your company can narrow it further. Your AllVoices admin can limit which actions are available for your company, for example read only. Some AI tools also let your AI admin turn off specific actions.

FAQ

How is this different from Vera? Vera works inside AllVoices and guides you through individual cases. MCP lets the AI tool your company already uses work with AllVoices, which is great for questions across many cases and for combining AllVoices with your other tools, like email, Slack or your documents. You can use both.

Does our AI tool admin need to be an admin in AllVoices? No. They just need permission to add a connector in your AI tool. Each person still signs in with their own AllVoices account to use it.

Will my AI assistant change things without asking? At launch the only change it can make is creating a new case. It can't add to, edit, delete or close existing cases. Most AI tools also ask you to confirm before taking a write action.

Can I see what my AI assistant did in AllVoices? Yes. Actions appear in the case activity log under your name, like any other action you take. We're working on labeling which AI tool took each action.

What happens to our data in the AI tool? When you ask a question, the case data needed to answer it is sent to your AI tool. How that tool stores and uses data is set by your company's agreement with your AI vendor, so check those terms with your IT or legal team. For how AllVoices handles your data, see [link to AllVoices AI and data policy].

Can we start with read only? Yes. Ask your Customer Success Manager to limit your company to read-only actions. You can add write actions later.

How do I disconnect? Anyone can disconnect AllVoices from their AI tool's connector or app settings. You can also see and disconnect connected AI tools in AllVoices at [AllVoices settings path]. Admins can remove the connector for the whole company in the AI tool's admin settings.

Which AI tools are supported? Any AI tool that supports remote MCP connectors. This guide covers the four most common enterprise options. If you use something else, talk to your Customer Success Manager.

Who do I contact for help? Your Customer Success Manager. For setup inside your AI tool, your AI tool admin and the vendor help articles below are the best resources.

Vendor help articles

AI tools update their screens often. If a step above doesn't match what you see, these are the current guides from each vendor.