How do I report that Avvi got something wrong?

Say so in the same conversation. What makes a report useful is what you expected, what happened, and roughly when.

Say so in the conversation where it happened. Avvi can pass the report to your IT team from there, with the context of what you were doing already attached.

Three things make a report useful: what you expected, what actually happened, and roughly when. Everything else is optional.

Reporting it is worth doing even when you found a way around the problem. A workaround you never mention is a problem that stays.

Before you begin

Stay in the conversation where it happened rather than starting a new one.

Have the three things ready. You do not need technical detail and you should not guess at causes.

Send the report

Say plainly what went wrong. For example: that removed the wrong person, I meant Sam Green not Sam Brown.
Say what you expected instead.
Ask Avvi to pass it to your IT team.
If something needs undoing, ask for that as a separate request.

Reporting and fixing are different things. Ask for both if you need both.

Good to know

If a change was made that should not have been, say so first and report second. Most changes can be reversed by asking for the opposite.

Quoting Avvi’s own words back is more useful than describing them. The exact wording tells your IT team where to look.

Verify it worked

Avvi confirms when the report has been sent.

If a change also needed reversing, check that separately rather than assuming the report did it.

If something doesn’t look right

If Avvi says it cannot pass the request on, your organisation has not set up that route. Contact your IT team directly.

If nothing comes back, remember nobody is watching for reports in real time. Follow up the way you normally would if it is urgent.

If Avvi disagrees that anything went wrong, report it anyway. Your IT team can look at the record.