If you asked your AI assistant to post a reply, update a ticket or publish an article and it refused, this article explains the most common reasons and how to fix them.
When an action is refused, nothing is changed in Zendesk. The MCP Server never carries out a refused action in a different form. For example, a refused public reply is not added as an internal note.
In this Article
What the Message Tells you
1. Write Access was not Authorized
2. Changes are Turned Off for the Account
3. Public Replies or Publishing are Not Allowed
4. You Turned it Off for Yourself
5. The Setting was Changed on a Different Swifteq Account
6. Your Zendesk User Cannot Make the Change
What the Message Tells you
| Message | Cause |
|---|---|
| Write access to Zendesk is turned off for this account, so no changes can be made | Refer to cause 2. |
| Public replies are not enabled for this account, so nothing was posted | Refer to cause 3. |
| Publishing articles directly is not enabled for this account, so nothing was created (or nothing was saved) | Refer to cause 3. |
| You have turned off ... for yourself | Refer to cause 4. |
| A message saying the Zendesk connection does not have write access | Refer to cause 1. |
1. Write Access was not Authorized
The Zendesk connection was authorized with Read Helpdesk Data only.
What to do: Reauthorize and turn on Write Helpdesk Data. For the account's connection, refer to Reauthorizing or Disconnecting the MCP Server. If you are on your own Zendesk login, refer to Connecting your Own Zendesk Login to the MCP Server.
2. Changes are Turned Off for the Account
Allow any changes in Zendesk is off in the This account column of the Settings tab. No changes can be made, including internal notes, status changes and article drafts.
What to do: Ask your account owner to turn it on. It works from the next request, and nobody needs to reconnect.
3. Public Replies or Publishing are Not Allowed
Allow public ticket replies and Allow publishing Help Center articles are off by default.
What to do:
- Ask for an internal note instead of a public reply, or for a draft instead of a published article.
- Or ask your account owner to turn on the permission in the Settings tab.
4. You Turned it Off for Yourself
The permission is on for the account, but off in your own Me column.
What to do: In the Settings tab, switch the permission back on in the Me column.
Refer to Write Permissions for the MCP Server.
5. The Setting was Changed on a Different Swifteq Account
If the permission is on but the action is still refused, check whether your company has more than one Swifteq account. Settings belong to the Swifteq account, not to the Zendesk account. If the person who changed the setting and the person using the AI assistant signed up separately, they are on different accounts.
What to do: Change the setting on the Swifteq account you actually use, or move everyone onto one account. Refer to How to Control Access and Subscription Cost for the MCP Server.
6. Your Zendesk User Cannot Make the Change
Zendesk still applies its own permissions. For example, a Light Agent cannot add public replies, and an agent without Help Center permissions cannot create articles.
What to do: Check the Zendesk role of the user behind the connection, or reauthorize with a user that has the required permissions.
After making any of these changes, start a new chat in your AI assistant and try again.
If you are still having problems, contact Swifteq support using the Live Chat or email support@swifteq.com, and include the exact message your AI assistant showed.