Troubleshooting
Fix common problems with the Bigly MCP, from connection and permission errors to changes that won't save and AI calls that are being blocked.
Walk through a permission error, a preview_required message and a not-enabled message, then run the blocked-calls diagnosis and follow its advice to the right setting.
Most MCP problems fall into three groups: the assistant can't connect, it can connect but isn't allowed to do something, or a change is refused. Your assistant usually passes Bigly's message on to you. Find the message below to see what it means and what to do.
Before you start
- Open AI › Connect your AI agent in the app. It shows whether the MCP is enabled for your account and whether you're allowed to use it.
- Know which assistant you're using and whether it connects by sign-in (Claude, ChatGPT) or by token (Claude Code and others). See Connect your AI assistant.
Connection problems
| What you see | What it means | What to do |
|---|---|---|
| The tab says the MCP integration isn't enabled for your account, or the assistant reports The MCP API is not enabled. | The feature is off for your account. | Contact support to turn it on. |
| The tab says you don't have permission to manage access tokens. | Your role doesn't include MCP access. | Ask an admin to change your role or to connect for you. See Team members. |
| The Bigly sign-in page says AI app connections aren't available. | None of your workspaces allow you to use the MCP. | Ask an admin of the workspace to turn the MCP on and give you access. |
| Authentication required, or the token is invalid or expired. | The token was revoked, mistyped, or belongs to another workspace. For Claude or ChatGPT, the connection was removed. | Generate a new token, or connect the app again. |
| Complete your checkout to use the MCP API. | Your new account hasn't finished signing up. | Finish checkout, then try again. |
| Claude or ChatGPT stopped working after a while. | The connection was disconnected, your access changed, or it hasn't been used for a long time. | Connect it again from the assistant's connector settings. |
AI › Connect your AI agent showing the yellow notice that the MCP integration isn't enabled for the account yet.
Errors when reading or changing settings
| Message starts with | What it means | What to do |
|---|---|---|
permission_denied | Your role can't view or change that area. The message names the missing permission. | Ask an admin. The account owner and admins can view and change every area by default. |
preview_required | The assistant tried to save a change without a matching preview. The preview may have expired (10 minutes by default), already been used, or the values changed after you saw them. | Ask the assistant to preview the change again, check it, and confirm. See How changes are made safely. |
confirmation_required | The save was sent without the right confirmation phrase. | Tell the assistant you approve the preview. It adds the phrase for you. |
validation_error | A value isn't allowed, for example an unknown voice, a time in the wrong format, or a missing required field. The message says which. | Ask the assistant to check the settings reference and fix the value. |
not_found | The item doesn't exist in your account, for example an intro or webhook that was already deleted. | Ask the assistant to list what exists now. |
That change failed. Read the error, tell me what it means in plain English, and suggest a fix.
The assistant can read but not change something
If the assistant says it has no tool to change an area, your role can view it but not change it. Bigly only gives the assistant update tools for the areas you're allowed to change. Ask an admin to update your role, then reconnect or restart your assistant so it picks up the new tools.
Diagnose blocked calls
If AI calls aren't going out, ask the assistant to run the Diagnose blocked AI calls workflow. It's read-only: it looks at your setup and Bigly's block reasons, then tells you which setting is likely responsible. It doesn't change anything or show contact details.
Our AI calls aren't going out. Diagnose why without changing anything.
Common reasons Bigly blocks a call, and where to look:
| Reason | What it means | Where to look |
|---|---|---|
| Do-not-call or litigator match | The number is on a protected list. | Compliance overview |
| Number reassigned | The number now belongs to someone else. | Compliance overview |
| Opted out | The contact was moved to do-not-call by an opt-out tag, too many hang-ups, or repeated phone-network errors. | AI settings |
| Line type not allowed | For example, a landline when only mobiles are allowed. | Compliance overview |
| Zip code not allowed | The contact's zip code isn't on your allowed list. | Allowed zip codes |
| Outside calling hours | The call fell outside your calling window or the state's legal hours. | Calling hours |
| Contact already converted | The contact already became a sale or transfer. | Contacts |
| Call caps reached | The number was already called the maximum times per day, week or month, or your account hit its calls-per-minute limit. | AI settings |
A Claude reply listing the most likely reasons calls are blocked, each with the setting to review, and stating that nothing was changed.
Common questions
The assistant made a change I didn't expect. Check the preview it showed you. Ask it to change the value back, which it previews again. For intros, prompt variables and voice prompts you can also roll back in Activity log.
The assistant can't find my contacts or calls. The MCP doesn't read contact or call data. See What the MCP doesn't cover.
Should I contact support? Yes, if the MCP isn't enabled, or if an error keeps happening after you preview and confirm again.