Agent Handoff Ownership SLA Auditor

How to use Agent Handoff Ownership SLA Auditor

A sent handoff does not establish a new owner. Review who acknowledged which job, when the ownership chain became established and whether that acceptance met your entered deadline.

1. Enter authorized job deadlines, initial owners and explicit transfer acknowledgments.
2. Choose the UTC as-of time and inspect unresolved, late or chain-inconsistent handoffs.
3. Resolve ownership against original messages and the real operator; export the review without sending a task.

Good to know

• Acceptance is not completion, consent or a verified legal SLA. Unacknowledged or future-dated transfers do not silently establish ownership.
• The deadline is per entered job. Simultaneous transfers are ordered by handoff ID; avoid relying on simultaneous dependent events.
• Each input field is limited to 8,000 UTF-16 characters and each exact-header CSV to 100 data rows. Quoted commas/newlines and doubled quotes are supported. Unsupported controls and unpaired surrogates are refused. Decimal magnitudes are at most 999,999,999 with a smallest nonzero magnitude of 0.000000001; exponents are refused and whole counts are checked exactly. Rational results show at most 18 fractional digits and an ellipsis when more remain.
• Editable Markdown and long-form CSV both retain all summary metrics, context, detailed findings, entered source rows and scope limitations. CSV columns are Record type,Section,Source row,Field,Value; spreadsheet-looking text is apostrophe-prefixed. These are review artifacts, not proof of source truth or a completed real-world task.
• Runs deterministically in this browser. No AI, API, vendor connection, upload, outreach, calendar change, payment, storage or background monitoring. Use authorized pseudonymous records; inspect exports before sharing.