Skip to main content
Approvals are how the team uses AI without losing operating control. Any action that changes a customer promise, margin position, supplier commitment, internal owner, or connected business system should be reviewed before it moves.

What needs approval

Customer commitments

Buyer replies with price, promise date, quantity, substitute product, or service recovery commitments.

Margin and finance

Margin exceptions, duty reserves, free-time exposure, credit notes, payment terms, and finance approvals.

System state

PO extraction, SKU mapping, ERP writebacks, CRM changes, invoice checks, and document updates.

Sensitive context

Actions that use customer, supplier, pricing, compliance, or internal operating notes.

What each button means

ActionUse when
ApproveThe suggestion is correct and ready to move.
EditThe direction is right but the copy, data, or owner needs adjustment.
AssignAnother operator, finance reviewer, or admin needs to decide.
RejectThe recommendation is wrong, stale, or unsafe.

Reviewer checklist

Approval means accountability. Check source context, not just the drafted output. If the context is stale or missing, assign or reject the item instead of approving it.
  • Source thread matches the customer, supplier, shipment, or account.
  • SKU, quantity, unit, account, and owner mapping are correct.
  • Pricing, margin, and promise-date logic fit the agreed guardrail.
  • The action does not reveal internal notes, supplier pricing, or sensitive context.
  • The activity trail will explain the decision later.

Audit trail

Each reviewed action should leave enough context for a future operator to answer: what changed, who reviewed it, what was approved, and where it moved next.
Last modified on May 28, 2026