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 coversexplains how to manage the pipeline efficiently, keep it accurate, and use it to drive results.

Legal Disclaimer: Results vary based on individual credit profiles and are not guaranteed.

Pipeline Stage Overview

Stage Description Owner Typical Duration 1. New Client Client profile created in DisputeFox; onboarding in progress; credit report not yet analyzed Onboarding Team Days 1–10 2. Credit Analysis Credit report has been pulled from all 3 bureaus; negative items are being categorized and prioritized Dispute Team Days 5–12 3. Round X – Letters Preparing Dispute letters being generated for this round; items selected, letter types chosen Dispute Team 2–5 business days 4. Round X – Letters Sent Letters have been submitted to bureaus and/or creditors; awaiting response window Dispute Team 30–45 days 5. Round X – Awaiting Response Within the 30–45 day response window; monitoring SmartCredit for bureau updates Dispute Team / CSR 30–45 days 6. Round X – Response Received Bureau responses are in; items need to be reviewed and classified (deleted, updated, verified) Dispute Team 3–7 business days 7. On Hold Client is unresponsive, has missing documents, or has a billing issue — disputes paused CSR Team Until resolved 8. Graduation Ready All actionable items have been addressed; client meets graduation criteria Dispute Team / CSR 1–2 weeks 9. Graduated Client has completed the program; graduation call done; moved to alumni status CSR Team Permanent

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 datePipeline 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" Fortracking 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 creditprogress scorefrom ininitial theanalysis "Scorethrough Tracking"every sectiondispute ofround their— profileso Notify the assigned CSR to call theno client withfalls results

Planning the Next Round

After processing all responses, review what remainsforward 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"schedule. 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

Graduation Criteria Checklist

Criterion Met? Minimum 2 complete dispute rounds have been run☐ All actionable negative items have been disputed (at least once per viable strategy)☐ Client's score has improved measurably (document starting vs. current)☐ Remaining items on report are either accurate, too recent to dispute, or legally required☐ No new negative items have been added by the client during the program☐ Graduation call is scheduled with the CSR team☐