Skip to article
ecomservices.io
Chargebacks · How to run this
MatchingNot on this page yetPricingCalculatorIntakeCalculatorReason codesCalculatorRepresentmentCalculatorThresholdsCalculatorAllocationCalculatorOptimisationCalculatorPrevention stackCalculatorProviders

Library · Chargebacks · How to run this

Chargeflow fight share is not Chargebacks911 fight share

How to run thisChargebacks3 steps
CalculatorChargeflow alert-to-fight share · Calculator lives in the articleOpen

CF fight % is the slice of Chargeflow alerts that land in a representment pack in one fight window. Fought console rows count. Every Chargeflow alert sits under.

Pair: Alert-to-fight share on Chargebacks. Intake twin: Chargebacks911 alert-to-fight. Escape twin: alert-escape.

What you type

Alerts fought — Chargeflow alerts sent into a representment pack in the window.

Alerts — Every Chargeflow alert in that same fight window.

CF fight % = fought ÷ alerts × 100. A fat CF fight % usually means the refund default is too loose — write it before you staff more packs. Never invent a CF fight chip.

What not to do

Do not invent CF fight %. Do not load a Chargebacks911 intake or Verifi CDRN fight file into Chargeflow fields. Do not count escaped alerts or auto-accepts as fights. Do not blend networks when Chargeflow alone owns the pack pile.

Related: Chargebacks, Chargebacks911 alert-to-fight, Verifi alert-to-fight, alert-escape.

Procedure

  1. Type alerts fought and alerts.
  2. Read CF fight %.
  3. Tighten the refund fork when CF fight % is material.

Failure modes

  • Inventing CF fight %.
  • Dumping a Chargebacks911 or Verifi fight file into Chargeflow fields.
  • Counting escaped alerts or auto-accepts as fights.

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 %
Alerts fought ÷ Alerts × 100.

Work with us — We run this job on your accounts. Services

FAQ

Is this Chargebacks911 alert-to-fight share?
Intake desk vs fight console. [Chargebacks911 alert-to-fight](/manuals/chargebacks911-alert-to-fight-share) stays on 911 intake. Here both counts are Chargeflow fight-console rows.
Is this Chargeflow alert-escape rate?
Escape is still-posted CB, not fight. [Alert-escape rate](/manuals/chargeflow-alert-escape-rate) is escaped ÷ alerts. This page is fought ÷ alerts.
What CF fight % should I invent?
None. Export fought Chargeflow alerts and total alerts from one Chargeflow fight window.