Dispute Round Pipeline Management
Dispute Round Pipeline Management
DisputeFox is the primary tool for managing all dispute activity at Crowned Credit. The dispute pipeline tracks every client's progress through the credit repair process — from initial analysis to graduation. This page covers how to manage the pipeline efficiently, keep it accurate, and use it to drive results.
⚙️ Pipeline Accuracy = Client Results
The dispute pipeline is not just an admin tool — it is a live, real-time view of every client's credit repair journey. If a client is in the wrong stage, letters don't get sent on time. If bureau responses aren't logged, strategies don't evolve. Keep the pipeline accurate at all times.
The dispute pipeline is not just an admin tool — it is a live, real-time view of every client's credit repair journey. If a client is in the wrong stage, letters don't get sent on time. If bureau responses aren't logged, strategies don't evolve. Keep the pipeline accurate at all times.
Pipeline Stage Overview
Round-by-Round Process
Starting a New Dispute Round
- Open the client's DisputeFox profile
- Navigate to Disputes → Add New Round
- Select the round number (Round 1, 2, 3, etc.)
- Review the credit report (SmartCredit) and identify target items for this round
- For each item, select:
- Bureau(s) the item appears on
- Dispute reason (inaccurate information, unverifiable, outdated, procedural error)
- Letter type (bureau dispute, creditor dispute, debt validation, etc.)
- Generate dispute letters — review each letter for accuracy before submitting
- Submit letters through DisputeFox (electronic) or prepare for mailing (certified mail for hard copies)
- Log the submission date in DisputeFox and set a follow-up date for 35 days out
- Move client to stage: "Round X – Letters Sent"
- Update GHL pipeline to match
Monitoring the Response Window
- During the 30–45 day window, check SmartCredit for the client at least once per week
- Some bureaus respond early — catch updates as soon as they're posted
- Log any changes (even partial or unclear ones) in DisputeFox notes immediately
- Notify the CSR assigned to this client if a significant update is detected mid-window
Processing Bureau Responses
- When responses arrive (typically by Day 30–40), move client to: "Round X – Response Received"
- For each disputed item, classify the outcome:
- ✅ Deleted — item removed from that bureau's report
- 🔄 Updated — item was modified (balance changed, status updated) but not removed
- ❌ Verified — bureau confirmed the item as accurate; needs new strategy
- ⏳ No Response — bureau did not respond (potential automatic deletion trigger)
- Document every outcome in DisputeFox with the bureau response date
- Update the client's credit score in the "Score Tracking" section of their profile
- Notify the assigned CSR to call the client with results
📊 What to Do With Each Outcome
✅ Deleted: Celebrate with the client. Remove from next round's target list. Document as a "win."
🔄 Updated: Determine if the update helps or is neutral. If still negative, add to Round 2 with updated strategy. If removed in all but one bureau, target that bureau specifically.
❌ Verified: Analyze why it was verified. Was the original dispute too generic? Try a different letter type — procedural dispute, method of verification request, or escalation to original creditor.
⏳ No Response: Under FCRA, if the bureau does not respond within 30 days, the client may be entitled to demand deletion. Log this carefully and consult Dispute Manager.
✅ Deleted: Celebrate with the client. Remove from next round's target list. Document as a "win."
🔄 Updated: Determine if the update helps or is neutral. If still negative, add to Round 2 with updated strategy. If removed in all but one bureau, target that bureau specifically.
❌ Verified: Analyze why it was verified. Was the original dispute too generic? Try a different letter type — procedural dispute, method of verification request, or escalation to original creditor.
⏳ No Response: Under FCRA, if the bureau does not respond within 30 days, the client may be entitled to demand deletion. Log this carefully and consult Dispute Manager.
Planning the Next Round
- After processing all responses, review what remains on the credit report
- Categorize remaining items by:
- Priority (high impact on score vs. low impact)
- Age (older items are harder to defend for bureaus)
- Bureau (which bureau still shows it — target specifically)
- New strategy needed (different letter type, creditor-level dispute, etc.)
- Begin building Round 2 in DisputeFox within 5 business days of completing response review
- Aim to send Round 2 letters within 7–10 days of receiving Round 1 responses
Putting a Client On Hold
A client is moved to "On Hold" when progress cannot continue. Common reasons:
- Missing required documents (ID, proof of address)
- Client unresponsive for 14+ days
- Billing issue — payment failed, subscription lapsed
- Client explicitly requested a pause
Hold Process
- Move client to "On Hold" in DisputeFox pipeline
- Log the hold reason and date in DisputeFox notes
- Update GHL pipeline to reflect hold status
- Add tag in GHL:
on-hold+ reason (e.g.,on-hold-billing) - Assign a CSR to actively work on resolving the hold condition
- Set a follow-up date in GHL for 7 days — if not resolved by then, escalate