When you do ask for approval, the design of that moment determines whether the person can make a good decision in the four seconds they'll give it.
Show | Why | Example |
|---|---|---|
The action, in plain language | They need to know what they're approving | 'Send this email to Karin at Bexley Logistics' |
The exact content, not a summary | Summaries hide the thing that's wrong | The full draft text, not 'a delay notification' |
Why the agent chose this | Lets them judge the reasoning, not just the output | 'Because the customs hold is now 6 days' |
What happens if they decline | Makes declining feel safe rather than obstructive | 'It'll hand this to you with its findings' |
Anything unusual about this case | Directs attention where it's needed | 'This customer has 3 open complaints' |
That last row does the most work. If every request looks the same, attention degrades uniformly. If the unusual ones are visibly marked, attention concentrates where it matters, which is the only realistic way to keep an approval step meaningful at volume.