Using admin copilot to change your configuration

Plan requirement

Subscription Suite Professional or higher, Support Professional or higher
Access Admin

Describing the change you want and reviewing what admin copilot proposes. The review is the part that matters. Alongside Conversational assistance you also get Latest insights and Top recommendations, which arrive without being asked and are worth reading before you ask for anything.

Use it

  1. In Admin Center, click the AI icon, then select Admin copilot and Admin copilot.
  2. Use Conversational assistance and describe what you want to achieve.
  3. Read the proposed change in full.
  4. Adjust the description if it is not right.
  5. Apply it, then verify the effect.

An admin copilot answer: a heading reading How to improve this, four bulleted suggestions, a link to edit the item it is talking about, a follow-up question, and an input box at the bottom reading Ask admin copilot anything.

Notice what the answer is: prose with suggestions, a link to the thing it is talking about, and a question back. It proposes and explains; it does not quietly change anything while you read. That is why the review step above is the one that matters.

Describe the outcome, not the mechanism

"Tickets about billing from business customers should reach the finance team within an hour" gets you a sensible proposal. "Create a trigger" gets you a trigger that may not do what you needed.

Saying what should happen lets it choose the right mechanism, which is often not the one you had in mind.

Read the conditions, not the action

Proposals are usually right about what to do and imprecise about when. A condition slightly broader than you meant catches tickets you did not intend, and it will do so quietly.

Say what should not happen

"But not for tickets already assigned" and "not for the trial brand". Exclusions are rarely inferred, and they are what keeps a change contained.

Change one thing at a time

Applying three proposals in one sitting makes an unexpected effect hard to attribute. Slower, and much easier to unpick.

Verify with a real ticket

Not by rereading the configuration. Send a ticket that should match and one that should not, and see what happens to each.

Ask it to explain, too

Asking what an existing trigger does, or what would break if you disabled it, is often more useful than asking for something new.

See also

Was this article helpful?

0

Still stuck?

Our support team will take a look with you.

Comments

0 comments

Article is closed for comments.