# Handle a support ticket end to end

> Let your AI read a Zendesk ticket and the customer's history, draft a reply, and post it and update the ticket only after your approval.

This guide handles one Zendesk ticket from start to finish in your AI chat: read it, check the customer's history, write the reply, and post it with a status change. Every change waits for your yes. You finish with the ticket answered and a record of it on **Activity**.

## What you need

- A **Pro** or **Agency** plan. Replies and ticket updates are changes, which aren't on Free.
- A [Zendesk](https://docs.plugsight.app/connectors/zendesk.md) connection, signed in with an agent or admin login. Changes appear in Zendesk as made by you.

## One-time set-up: allow changes

1. On **Connections**, click the Zendesk connection's switch so it says **Can reply & update**.
2. On **MCP servers**, open the server your AI app uses. If its badge says **Read & draft only**, click **Edit configuration**, tick **Allow changes** and save.
3. On **Permissions**, check nothing is paused: neither **Pause everything** nor the **Helpdesk** row.
4. Back on **Connections**, check the line under the Zendesk switch says **Ready**.

If it names something else, follow [Switch states under each account](https://docs.plugsight.app/permissions/switch-states.md). The full list of checks is in [How changes are allowed](https://docs.plugsight.app/permissions/how-changes-are-allowed.md).

> [!TIP]
> Want to try this without any risk of a reply reaching a customer? Ask only for internal notes, which customers never see, until you're comfortable.

## Step 1: read the ticket

- "Read Zendesk ticket 4821 and summarise it: who it's from, what they want, what's been said so far, and what's still open."

Your AI reads the whole conversation, public replies and internal notes, oldest first, with links to attachments.

## Step 2: check the customer's history

- "What else has this customer raised in the last 90 days? Anything still open?"
- "Find the customer's other tickets about refunds."

## Step 3: check for a macro

- "Is there a macro for this kind of request?"

If there is, your AI can apply it in Step 5. Before applying a macro, it previews exactly what the macro will change (reply text, status, tags and other fields) and shows you.

## Step 4: write the reply

- "Draft a public reply to ticket 4821: apologise for the delay, confirm the refund of the second item, and say it takes 5 working days. Friendly, under 120 words. Don't post it yet."

Ask for changes until you're happy with the text. Nothing is posted while you're editing.

## Step 5: post it and update the ticket

- "Post that reply and set the ticket to pending."

Your AI shows you the ticket and the exact text, and the status change, then waits. Read it, then say yes. Only then is the reply posted. A public reply is emailed to the requester by Zendesk.

Or, with a macro:

- "Apply the 'Refund approved' macro to ticket 4821."

Your AI shows the preview, then applies it after your yes.

Other changes your AI can make the same way, each after your yes:

- **Internal note**: "Add an internal note to 4821: refund approved by Sam, ref R-2231."
- **Update**: status, priority, type, assignee, and adding or removing tags. "Tag 4821 'refund' and assign it to me."
- **New ticket**: "Open a ticket for jane@acme.com about the missing invoice." Its first message is an internal note unless you ask for it to go to the customer.

## Step 6: check it worked

1. Open the ticket in Zendesk: the reply and changes are there, made by you.
2. In Plugsight, open **Activity** and filter by **AI apps**. Each change is listed with its result.

## If the change is refused

Your AI passes on Plugsight's reason. The common ones:

| Message | Fix |
| --- | --- |
| Changes are off for "…". Allow them under Connections first. | Turn the Zendesk switch to **Can reply & update**. |
| The "…" MCP is read-only. Allow changes on the MCP server first (MCP servers page). | Tick **Allow changes** on the server. |
| Helpdesk replies and updates are paused (Permissions page). | Click **Resume** next to **Helpdesk** on **Permissions**. |
| Zendesk refused this action for that agent (…). | Your Zendesk role doesn't allow it. Ask a Zendesk admin. |

Every message is explained in [Your AI can't send or change anything](https://docs.plugsight.app/troubleshooting/ai-cant-send-or-change.md).

## Related articles

- [Approvals in the chat](https://docs.plugsight.app/permissions/approvals.md)
- [Weekly support ticket review](https://docs.plugsight.app/guides/weekly-support-review.md)
- [When to use Pause](https://docs.plugsight.app/guides/when-to-pause.md)

---

Web version: https://docs.plugsight.app/guides/support-ticket-with-approval
