If you asked your AI assistant to post a reply, update a ticket, publish an article, add someone to an organization or change or apply a macro 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, Publishing, User and Organization Changes, Macro Changes or Merging are Not Allowed
4. Your Account Owner Turned it Off for You
5. You Turned it Off for Yourself
6. The Setting was Changed on a Different Swifteq Account
7. Your Zendesk User Cannot Make the Change
8. The Person Already Belongs to Another Organization
9. CCs Cannot be Added
10. Linking or Solving a Problem Ticket
11. Applying a Macro
12. Merging Tickets
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. |
| Changes to users and organizations are not enabled for this account, so nothing was changed | Refer to cause 3. |
| Changes to macros are not enabled for this account, so nothing was changed | Refer to cause 3. |
| Merging tickets is not enabled for this account, so nothing was merged | Refer to cause 3. |
| Nothing was merged: every ticket merged into ... must have its requester | Refer to cause 12. |
| Nothing was merged: ... is solved, ... is closed, ... is shared, ... is still with an AI agent or ... was merged into ... | Refer to cause 12. |
| Zendesk refused the merge (403), so nothing was merged | Refer to cause 7. |
| Zendesk refused this change (403), so nothing was changed | Refer to cause 7. |
| Ticket ... is closed, This macro is inactive, This macro starts a side conversation or a message that the macro's files could not be copied | Refer to cause 11. |
| This macro was applied to this ticket at ..., so nothing was sent again | Refer to cause 11. |
| Public replies are not enabled for this account, so no ticket was created | Refer to cause 3. |
| The requester's email address does not belong to anyone in Zendesk yet, and adding new users is not enabled for this account, so no ticket was created | Refer to cause 3. |
| CCs reach people outside your team, and public replies are not enabled for this account, so nothing was changed | Refer to cause 3. |
| A CC's email address does not belong to anyone in Zendesk yet, and adding new users is not enabled for this account ... | Refer to cause 3. |
| CCs are not allowed with a private comment ... | Refer to cause 9. |
| CCs are turned off in this Zendesk account ... | Refer to cause 9. |
| Ticket ... is a problem with ... unsolved incidents. Solving it also solves them ... | Refer to cause 10. |
| Ticket ... is ..., not a problem ... or Problem ... is closed, so incidents cannot be linked to it | Refer to cause 10. |
| Ticket ... is a problem with ... linked incidents. Changing its type would leave them linked to a ticket that is not a problem ... | Refer to cause 10. |
| This Zendesk account allows one organization per user, and ... already belongs to ... | Refer to cause 8. |
| Your account owner has turned off ... for you | Refer to cause 4. |
| You have turned off ... for yourself | Refer to cause 5. |
| 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, Publishing, User and Organization Changes, Macro Changes or Merging are Not Allowed
Allow public ticket replies, Allow publishing Help Center articles, Allow changes to users and organizations, Allow changes to macros and Allow merging tickets 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. To add someone to an organization, change a macro or merge tickets, make the change in Zendesk. To apply a macro whose reply is public, ask for it to be applied as an internal note. For a new ticket, ask for a private first note, or create it for someone who is already in Zendesk. For CCs, CC only people who are already in Zendesk, or leave the CCs out.
- Or ask your account owner to turn on the permission in the Settings tab.
4. Your Account Owner Turned it Off for You
The permission is on for the account, but your account owner has turned it off for you personally on the Users page. In your Settings tab, the Me switch for that permission is locked and shows Your account owner has turned this off for you. You cannot turn it back on yourself.
What to do: Ask your account owner to change your write access on the Users page. In the meantime, ask for an internal note instead of a public reply, or for a draft instead of a published article. If all changes are off for you, the AI assistant can still read.
5. 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.
6. 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.
7. Your Zendesk User Cannot Make the Change
Zendesk still applies its own permissions. For example, a Light Agent can add internal notes but cannot post public replies or change ticket fields, an agent without Help Center permissions cannot create articles, only an admin can add another agent to an organization, and changing a shared or group macro needs an admin or a role allowed to manage macros. Agents can only change their own personal macros. On Enterprise plans, merging tickets is a role permission too.
What to do: Check the Zendesk role of the user behind the connection, or reauthorize with a user that has the required permissions.
8. The Person Already Belongs to Another Organization
Some Zendesk accounts allow each user to belong to only one organization. If the person you asked to add already belongs to another organization, the AI assistant does not move them unless you ask it to, and the message names their current organization.
What to do: If moving them is what you want, ask the AI assistant to move them. They leave their current organization, and Zendesk moves their open tickets to the new one.
9. CCs Cannot be Added
Zendesk ignores CCs in two cases, so the MCP Server refuses the request instead of making it without them:
- The same request adds an internal note. CCs are not allowed with a private comment, including the first comment of a new ticket.
- CCs are turned off in your Zendesk (Admin Center > Objects and rules > Tickets > Settings).
What to do: Add or remove CCs in a separate request, without a comment. To turn on CCs, ask a Zendesk admin.
10. Linking or Solving a Problem Ticket
Solving a problem ticket in Zendesk also solves all its open incident tickets, adds the same comment to each and runs your triggers for each one, which can email every requester. Reopening the problem ticket afterwards does not reopen them. So the MCP Server does not solve a problem ticket that still has open incidents until your AI assistant confirms it, and the message says how many incidents would be solved.
Linking is refused when the ticket to link to is not a problem ticket, or is closed. A problem ticket that still has incidents linked to it cannot change type, because its incidents would stay linked to a ticket that is no longer a problem.
What to do:
- To solve the problem ticket and its incidents, tell your AI assistant to go ahead.
- To solve only the problem ticket, ask your AI assistant to unlink the incidents first.
- To link tickets, ask your AI assistant to find the open problem tickets, or set the ticket's type to Problem first.
11. Applying a Macro
The AI assistant applies a macro the way an agent does in Zendesk, and refuses when it cannot do the same:
- The ticket is closed. Zendesk does not allow changes to a closed ticket.
- The macro is inactive. Agents cannot apply it either until it is reactivated.
- The macro starts a side conversation, which the MCP Server cannot do.
- One of the macro's files cannot be attached, for example because it is larger than your Zendesk account's attachment limit. Nothing is sent, so the reply never goes out without its file.
If the same macro was applied to the same ticket in the last 10 minutes, nothing is sent again, so a retry does not post the reply twice.
What to do: Reactivate the macro, or apply it in Zendesk. To apply a macro to the same ticket a second time on purpose, ask your AI assistant to apply it again.
12. Merging Tickets
The MCP Server checks every merge before anything changes in Zendesk, and refuses it when:
- The tickets have different requesters. The MCP Server only merges tickets from the same requester, and the message names each ticket's requester. This cannot be turned off. With CCs on, Zendesk itself would merge them, and the other customer would then receive the replies on the ticket you keep.
- A duplicate is solved or closed. Zendesk only merges unsolved tickets into another. A solved ticket can still be the one you keep: merge the other tickets into it. A closed ticket cannot be merged.
- The ticket you keep is closed, or was itself merged into another ticket. The message says which ticket it was merged into, so you can merge into that one instead.
- A ticket is shared with another Zendesk account, or a Zendesk AI agent is still handling it. Zendesk does not merge these.
Asking for the same merge again is safe: tickets that were already merged are reported as already merged, and nothing is sent again. If the result says the merge is not confirmed, Zendesk had not finished it yet. Check the tickets in Zendesk before trying again.
What to do: If tickets from different requesters really belong together, merge them in Zendesk. Otherwise choose another ticket to keep, or leave the duplicate as it is.
Permission changes apply from the next request. After reauthorizing Zendesk, 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.