Pick one structure and stick with it.
Risk Ops::ATO::Escalate and Risk Ops::Escalate::ATO can both work. The problem starts when your instance uses both.
Zendesk Macro Naming Generator
Stop inventing a new naming pattern every time someone creates a macro.
Type the parts.
Put them in order.
Copy the name.
One less Refund2.
Stays in your browser.
Not sent anywhere.
Examples
Risk Ops::ATO::Escalate
Risk Ops::Escalate::ATO
Both fine. Pick one and stick with it.
Before you create another macro...
Don't make the next person guess.
If someone can't predict what a macro is called, they'll probably create another one.
Avoid temporary names.
Refund New, Refund Test, Refund Final. Those names rarely stay temporary.
Keep it readable.
If a new admin has to ask what a macro name means, it's probably trying to do too much.
Rename in batches, not all at once.
A naming standard is easier to adopt when new macros follow it first. Clean up older ones over time instead of trying to rename everything in one afternoon.