What admin copilot does

Help with configuration work: describing what you want and getting a proposed change instead of a settings hunt.

Help with configuration work: describing what you want and getting a proposed change instead of a settings hunt.

What it does

You describe the outcome in ordinary language, and it proposes the configuration: a trigger, a view, a field, a routing rule. You review the proposal and decide.

Where it helps most

• Things you do rarely. Building a trigger once a quarter means relearning the conditions each time.
• Finding where a setting lives in an interface with a great many screens.
• Explaining existing configuration, particularly one somebody else built.

The last one is underrated

Inheriting an account with forty triggers nobody documented is a common situation. Being able to ask what a trigger does, and what would happen if you disabled it, is worth more than building new ones quickly.

You still approve

Nothing is applied without you agreeing. That matters more here than with agent-facing features, because configuration changes affect everybody at once and some of them are awkward to unpick.

Review the proposal properly

A proposed trigger can be right in intent and wrong in scope: the correct action with a condition that catches more tickets than you meant. Read what it will match, not only what it will do.

It does not know your business

It knows Zendesk. Whether a change is a good idea for your organisation, and whether it conflicts with something you agreed last year, is still your judgement.

See also

• Using admin copilot to change your configuration
• Testing admin copilot changes before applying them
• Managing access to admin copilot