Every action an agent proposes waits in one queue with the reason and the policy that held it. Approve, edit and approve, or reject with a reason. Submitting a candidate always needs a person.
Then nobody can say why it happened. Every message, submittal and merge an agent proposes should wait for someone who can answer for it.
71%
of Americans oppose AI making a final hiring decision.
Every action that reaches outside ANDY becomes a proposal: an email, a submittal, a merge.
Your autonomy settings say which steps need approval. Submittals, merges and sensitive fields always do.
Approve, edit and approve, reject with a reason, or snooze. Your edits are kept next to the draft.
Filter to one type of low-risk item and approve them at once. Submittals never qualify.
Request: What's waiting for me?
Waiting for your approval
Co-Pilot default: needs approval.
Priya, thanks for the call today. I'll send your details to the team at Harbor & Vine LLP this afternoon and come back to you by Friday. Jordan
Request: Show the merge waiting for me.
Waiting for your approval
Platform lock: this action always needs a human.
Keep the résumé upload from Oct 2 and the phone number from the Aug 18 import. The older record's history moves across.
Request: Show the submittal waiting for me.
Waiting for your approval
Platform lock: this action always needs a human.
! Conflict warning: submitted to this client on Mar 14
Marcus T., Security Specialist, Woodbridge, VA. Active TS/SCI, current polygraph.
Fictional example. Approval Queue works this way in ANDY today.
Whatever your autonomy settings hold for review, and always submittals, merges and sensitive fields.
Each proposal, the policy that held it, who decided and when, and the text before and after any edit.
Every requisition shows its mode: Co-Pilot, Hybrid or Custom. Co-Pilot, the default, sends nothing without your approval.
How approval works