Verifying an exception rule is only half the workflow. When a driver drops a wet or leaning shrink-wrap load, standard operating procedures require photographic evidence before breaking the trailer seal and opening an OS&D / Carrier Exception Ticket within a strict deadline window.
Switching to legacy portals to re-type shipment IDs, severity levels, customer references, and policy citations wastes critical unloading minutes—and letting an automated system fire write requests unchecked is unacceptable in mission-critical logistics.
Safe automation with explicit human checkpoints
SCA draws a bright operational line between read checks (auto_run) and state-changing write tools (require_approval):
- Inspect before execution. When a dispatcher asks
Coca-Cola Assistantto log an incident after checking the SOP, the assistant populates every required field (shipmentRef,customer,exceptionType,summary) inside an inline Human Approval Card. - Two-hour expiry & idempotency. Every pending write request carries a cryptographic idempotency key and
2-hourexpiry window so interrupted shifts never create duplicate ERP or WMS records. - Granular company-level enablement. Company Admins inspect the Tools Catalog screen to review every connector's schema, execution mode (
auto_runvsrequire_approval), and activation status per specialist.
Closing the loop on claims leakage
Instead of rejected claims caused by missed reporting deadlines or incomplete exception summaries, every logged incident captures the exact cited SOP clause alongside human sign-off in an auditable timeline.
