Read the requested action.
Check what the agent wants to do, which project or account it affects, and why it is needed. Inspect the surrounding conversation when the request is unclear.
Product / Approvals
The decisions that matter
come back to you.
Review requested actions in context, decide what should happen, and keep the team moving with a clear answer.
A practical starting point
Give each decision
the context it needs.
Choose the next step.
Approve an action you understand, deny it, or ask for a narrower plan. Give feedback that explains the condition the next request needs to satisfy.
Check what followed.
Look for the resulting action and output. An approved request is permission to proceed; it does not establish that the requested action succeeded.
Put it into practice
Be specific about consequential work.
A development team can prepare a change, run checks, and hand over a reviewable result before asking to publish. A support team can draft a reply before you decide to send it. Put those expectations in the project brief.
Before approving an external action, confirm the destination, scope, and content. If the plan has changed since the request was created, ask the agent to restate the current action.
In the website demo, the approval controls complete once and do not execute commands. Real behavior depends on the app’s access settings and the tools being used.