Library · Chargebacks · How to run this
Chargeflow fight-clock wait is not Chargeblast fight-clock wait
CF fight-clock at-risk $ is cases × AOV $ on a Chargeflow fight-clock export. Park lag hours beside that product so the stall stays visible.
Pair: Alert-to-fight lag on Chargebacks. Chargeblast twin: Chargeblast lag. Disputifier twin: Disputifier lag.
What you type
Lag hours — Mean hours from Chargeflow alert arrival to fight / refund decision.
Cases — Open Chargeflow alerts still waiting that decision on the export.
AOV $ — Average order dollars on those Chargeflow alerts.
CF fight-clock at-risk $ = cases × AOV. When lag hours run long and CF fight-clock at-risk $ is material, the Chargeflow fight seat is the chase — never invent a CF fight-clock at-risk chip.
What not to do
Never invent CF fight-clock at-risk $. Never load Chargeblast or Disputifier lag rows into Chargeflow inputs. Never swap fight-share % for dollar burn. Never merge MID books when one Chargeflow seat owns the stall.
Related: Chargebacks, Chargeblast lag, Disputifier lag, alert-to-refund.
Procedure
- Type lag hours, cases, and AOV $.
- Read CF fight-clock at-risk $.
- Chase fight desk when CF fight-clock at-risk $ is material with fat lag.
Failure modes
- Inventing CF fight-clock at-risk $.
- Pasting a Chargeblast or Disputifier lag file into Chargeflow fields.
- Treating fight-share % as dollar burn.
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
- CF fight-clock at-risk $
- Cases × AOV $ on one Chargeflow fight-clock export; lag hours held beside.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Chargeblast alert-to-fight lag?
- Separate alert rail. [Alert-to-fight lag](/manuals/chargeblast-alert-to-fight-lag) prices Chargeblast. Chargeflow alone owns cases, AOV $, and lag hours here.
- Is this Disputifier alert-to-fight lag?
- Different dispute desk. [Alert-to-fight lag](/manuals/disputifier-alert-to-fight-lag) stays on Disputifier. No Disputifier rows enter Chargeflow fields.
- What CF fight-clock at-risk $ should I invent?
- None. Take lag hours, cases, and AOV $ from one Chargeflow fight-clock export.