Zendesk Copilot: review what guides your team’s replies

Review the information behind the reply

If your team uses AI to prepare customer replies, check what informs the draft as well as the wording it produces. An internal handover may contain useful context, an unfinished assumption or a decision that needs confirming.

On November 2, Zendesk made internal notes part of the information its Copilot auto assist uses on a ticket, meaning a customer support request. That inclusion happens automatically when the conversation contains internal notes.

A separate change rolling out from November 3 to 6 lets administrators narrow which written procedures auto assist considers by the team assigned to the request and its labels. Together, the updates deserve a review of the guidance your staff rely on.

Read the announcement: Zendesk: automatic internal-note context from November 2.

Keep notes and procedures distinct

Auto assist helps human service staff prepare replies and actions. It is part of the Copilot add-on, rather than the separate AI agent that talks directly to customers. Check that your account includes it.

Zendesk says the helper may ignore an internal note it considers unhelpful or sensitive. That is not a reason to assume every unsuitable detail will be excluded. Give staff a clear way to distinguish confirmed decisions from information still being checked.

Customer replies still need staff approval before sending. Some actions can run automatically when an administrator has separately pre-approved them in a procedure. Review those action rules alongside the reply-review process.

Make the right procedure eligible

Previously, procedure availability could be limited by brand. The new settings add the assigned staff group and ticket tags, which are labels on the request. They can be combined to make a procedure relevant to a narrower set of work.

Where several categories are configured, a request must match at least one selected value in each category. That makes the procedure eligible for consideration; it does not force auto assist to use it.

Procedures without specific restrictions remain broadly available. These settings also do not provide a switch for excluding individual internal notes. Check the rollout has reached your account before relying on the new choices.

Make review part of the team routine

Our perspective: clear, maintained instructions are easier to review than a growing collection of half-finished explanations. Have the knowledge owner keep approved answers current and let the support lead check how those answers appear in a representative conversation.

For a separate draft-and-review routine in Claude or Codex, our Inbox and Customer Replies Playbook helps maintain approved answers and prepare replies for a person to check. Zendesk configuration remains the administrator’s responsibility.

1. Review an approved or invented conversation containing an internal handover.
2. Check whether the draft separates confirmed facts from unresolved questions.
3. Test a request that should qualify for a procedure and one that should not.
4. Name who updates the procedure and who approves customer-facing replies.