Library · Chargebacks · How to run this
Alert-to-refund lag is not alert-to-fight
Refund hour − alert hour make lag hours. Type both plus alerts.
Pair: Alert-to-refund lag on Chargebacks. Fight: alert-to-fight lag. Waste: refund-before-alert waste.
What you type
Alert hour — hour index when the alert landed (window clock).
Refund hour — hour index when the refund posted for that alert cohort.
Alerts — alerts in that same refunded cohort.
Lag hours = refund hour − alert hour. Cut ops lag when hours are fat — do not invent a lag chip.
What not to do
Do not invent lag hours. Do not mix fight decisions into refund hour. Do not treat duplicate alerts as separate refunds. Do not average every MID when one owns the lag.
Related: Chargebacks, alert-to-fight lag, refund-before-alert waste, alert duplicate rate, MID alert coverage gap.
Procedure
- Type alert hour, refund hour, and alerts.
- Read lag hours.
- Cut ops lag when hours are material.
Failure modes
- Inventing lag hours.
- Mixing fight decisions into refund hour.
- Treating duplicate alerts as separate refunds.
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-refund lag hours
- Refund hour − alert hour for the typed alert cohort.
Work with us — We run this job on your accounts. Services
FAQ
- Is this alert-to-fight lag?
- Sibling alert clock. [Alert-to-fight lag](/manuals/disputifier-alert-to-fight-lag) is hours to fight decision × cases. This page is refund hour − alert hour on Chargeblast.
- Is this refund-before-alert waste?
- Related dollars. [Refund-before-alert waste](/manuals/disputifier-refund-before-alert-waste) is refund then alert fee on one order. This page is alert-to-refund lag.
- What lag hours should I invent?
- None. Type alert hour, refund hour, and alerts from the same Chargeblast window.