Library · Chargebacks · How to run this
Slow fight clocks leave dollars open
Cases × AOV $ is at-risk $. Lag hours is the alert→fight clock. Type lag hours, cases, and AOV $.
Pair: Alert-to-fight lag on Chargebacks. SLA: alert response clocks. Pack: evidence pack hours.
What you type
Lag hours — average hours from alert to fight / refund decision (export).
Cases — open alert cases in that window.
AOV $ — average order value on those cases (typed).
At-risk $ = cases × AOV. Cut lag when hours are material — do not invent an at-risk chip.
What not to do
Do not invent at-risk $. Do not mix RDR auto-refunds into fight cases. Do not treat Ethoca ack as fight. Do not average every MID when one owns the lag.
Related: Chargebacks, alert response clocks, evidence pack hours, RDR vs alert mix.
Procedure
- Type lag hours, cases, and AOV $.
- Read at-risk $ and lag.
- Cut lag when hours are material.
Failure modes
- Inventing at-risk $.
- Mixing RDR auto-refunds into fight cases.
- Treating Ethoca ack as fight.
Worked example
None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.
Glossary
- Alert-to-fight at-risk $
- Open alert cases × AOV $; lag hours is alert→fight clock.
Work with us — We run this job on your accounts. Services
FAQ
- Is this alert response clocks?
- Sibling clock. [Alert response clocks](/manuals/alert-response-clocks) is the written SLA window. This page is hours from alert to fight decision × cases × AOV.
- Is this evidence pack hours?
- Related labor. [Evidence pack hours](/manuals/chargeflow-evidence-pack-hours) is pack build time. This page is alert→fight lag and at-risk $.
- What at-risk $ should I invent?
- None. Type lag hours, open cases, and AOV $ from the alert tool for the same window.