Plan requirement
| Subscription | Suite Growth or higher |
| Also required | Copilot |
| Access | Admin |
Describing the change you want and reviewing what admin copilot proposes. The review is the part that matters.
Use it
- Open admin copilot in Admin Center.
- Describe what you want to achieve.
- Read the proposed change in full.
- Adjust the description if it is not right.
- Apply it, then verify the effect.
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.
Comments
0 comments
Article is closed for comments.