Library · Chargebacks · How to run this
Forter dispute-workspace fight-pack drop rail is not Chargeflow auto-fight fight-pack drop queue
Mount one Forter dispute-workspace fight-pack drop rail. Note when the pack became pack-ready. Note when ops dropped it. Keep Forter case rows beside that window. The hour gap is FT case-filing hours. Chargeflow auto-fight fight-pack queues, dispute-workspace arbitration rails, and issuer-reply bays never feed this rail.
Pair: Case-filing lag under Chargebacks. Chargeflow twin: CF case-filing. Arbitration twin: FT arbitration-file.
Dispute-workspace fight-pack drop stamps
Ready hour — Pack-ready stamp on the Forter dispute-workspace fight-pack drop rail.
Filed hour — Drop stamp on that same rail.
Cases — Forter fight-pack drop rows inside that pack-ready → drop span.
FT case-filing hours = filed hour − ready hour. Hot FT case-filing hours usually mean the dispute-workspace rail is short on drop capacity — chase that rail before arbitration accept lag. Leave blank chips blank.
What not to do
Do not invent FT case-filing hours. Do not dump arbitration accept CSVs, issuer-reply stamps, or Chargeflow auto-fight queue hours into ready/filed boxes. Do not fold FT pack-hole % into drop hours. Do not fuse MIDs when one Forter dispute-workspace fight-pack drop rail owns the stack.
Related: Chargebacks, CF case-filing, FT arbitration-file, FT issuer-reply.
Procedure
- Type ready hour, filed hour, and cases.
- Read FT case-filing hours.
- Staff the dispute-workspace fight-pack drop rail when FT case-filing hours drag.
Failure modes
- Inventing FT case-filing hours.
- Dumping arbitration accept stamps, issuer-reply hours, or Chargeflow auto-fight queue hours into pack-ready/drop boxes.
- Folding FT pack-hole % into drop hours.
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
- FT case-filing hours
- Drop hour − pack-ready hour on one Forter dispute-workspace fight-pack drop rail.
Work with us — We run this job on your accounts. Services
FAQ
- Is this Chargeflow case-filing lag?
- Forter dispute-workspace fight-pack drop rail vs Chargeflow auto-fight fight-pack drop queue. [Case-filing lag](/manuals/chargeflow-case-filing-lag) stays on Chargeflow. Drop / pack-ready stamps for Forter belong on this dispute-workspace rail.
- Is this Forter arbitration-file lag?
- Dispute-workspace fight-pack drop rail vs dispute-workspace arbitration filing rail. [Arbitration-file lag](/manuals/forter-arbitration-file-lag) clocks file → workspace accept. Here you only score drop stamp − pack-ready stamp on the fight-pack rail.
- What FT case-filing hours should I invent?
- None. Pull pack-ready stamp, drop stamp, and Forter case rows from the same dispute-workspace fight-pack drop rail.