Each dispute represented or accepted on the evidence on file.
What it solves: Each chargeback is represented, partly represented or accepted on what its Box evidence and Outlook refund history show, analysts are assigned by tier, and late evidence re-runs the rules. The disputes lead approves every status before Attio changes.
How it runs
- Dispositions Each in-scope dispute gets a status from its Box evidence and, where the rules call for it, its refund history in Outlook Who decides: The disputes lead approves before Attio is written
- Caseload plan Disputes set to represent or represent partial are assigned to analysts by tier and capacity Who decides: The disputes lead approves the assignments
- Worksheet review The generated win-probability worksheet is checked, every wrong score is listed and the Box review file is annotated Who decides: The disputes lead approves the corrected scores
- Delivery proof Disputes with new delivery confirmations are re-derived under the full rule order, and a newly eligible one gets an analyst Who decides: The disputes lead approves, and an analyst sends each reply
- Weights revision Scores and tracks are recomputed under the new checklist weights for disputes currently set to represent Who decides: The disputes lead approves
- Extension and withdrawal An extended deadline is updated and its dispute re-derived, and a withdrawn dispute is closed with its analyst cleared Who decides: The disputes lead approves both
- Close-out Totals per reason code are counted from the final Attio records and a close-out note is created for each Who decides: The disputes lead signs the close-out
Tools it connects
- Attio: Tracks every dispute with its status, score, track, analyst and deadline, plus the close-out notes.
- Box: Keeps each dispute’s evidence file and the worksheet review file.
- Google Drive: Keeps the response policy, the checklist weights and the generated worksheet.
- Outlook: Holds the refund confirmations the rules check before a dispute is represented.
- Gmail (optional): Carries delivery confirmations, extensions and withdrawals, and each reply is a draft an analyst sends.
- Slack (optional): Is where analysts flag capacity and customer care flags withdrawals.
Set-up prompt
Paste this into Kylon, or start it in one click below.
Set up our card chargebacks desk in this Room. Take it one step at a time and wait for my OK before you move on.
1. Connect Attio, Box, Google Drive and Outlook first, since the first run needs them. Tell me which ones still need connecting. Gmail and Slack can wait until a step uses them.
2. Ask me who works this desk: the disputes lead, the dispute analysts and the customer care lead. Help me invite them to this Room.
3. Build a Chargeback Desk App with Dispute, Reason, Analyst and Status columns, one record per dispute. Pull open disputes from Attio and match each to its Box evidence file.
4. Read each dispute's Box evidence and, where our rules call for it, its refund history in Outlook. Propose a status for each, generate the win-probability worksheet in Google Drive, check every score against our checklist weights, and show me disputes that fail or whose scores look wrong.
5. Draft all replies on delivery, processor and withdrawal threads in Gmail and all analyst caseload updates in Slack. Draft the close-out note for each reason code. Write nothing to Attio and send nothing until the disputes lead approves every status, score, assignment and close-out.
6. Write the rule order, the approval chain and the recording fields into this Room's guideline so every dispute cycle follows them.
7. After one clean cycle, offer to turn the incoming-dispute review into an Automation.
Start with step 1. Once the tools are connected, or I say the rest can wait, ask me for our rules one at a time.