Library · Chargebacks · How to run this
Tickets that become chargebacks
CB tickets over total tickets make CB ticket %. CB ticket % = CB tickets / total × 100. Type CB tickets and total tickets.
Pair: Escalation to chargeback on Chargebacks. Clock: SLA breach cost. Fork: refund this ticket.
What you type
CB tickets — helpdesk tickets that posted a bank chargeback in the window.
Total tickets — all tickets in the same window (same queue export).
CB ticket % = CB / total × 100. Fix intake when the share is material — do not invent a CB ticket chip.
What not to do
Do not invent a CB ticket percent. Do not mix alert refunds into CB tickets. Do not treat SLA breaches as chargebacks. Do not average every brand queue when one owns the hole.
Related: Chargebacks, SLA breach cost, refund this ticket, alert refund vs fight.
Procedure
- Type CB tickets and total tickets.
- Read CB ticket %.
- Fix intake when the share is material.
Failure modes
- Inventing a CB ticket percent.
- Mixing alert refunds into CB tickets.
- Treating SLA breaches as chargebacks.
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
- CB ticket escalation %
- Tickets that posted a chargeback ÷ total tickets × 100.
Work with us — We run this job on your accounts. Services
FAQ
- Is this SLA breach cost?
- Related helpdesk clock. [SLA breach cost](/manuals/zendesk-sla-breach-cost) prices tickets past SLA. This page is tickets that became chargebacks vs total.
- Is this refund this ticket?
- Related pre-CB move. [Refund this ticket](/manuals/refund-to-protect-mid) is the refund fork. This page is escalation share into CB.
- What CB ticket % should I invent?
- None. Type CB-linked tickets and total tickets from the helpdesk export for the same window.