Skip to main content

Cross-Department Support

Cross-Department Support

AddressingCrowned Credit operates as a tight, interdependent team. No department is an island. When a client moves from onboarding to active disputes to support requestsand finally to graduation, multiple teams must hand off work cleanly and communicate clearly. This page defines how departments collaborate, what the handoff protocols are, and who owns what at each stage.

🤝 Core Principle
At Crowned Credit, the client doesn't care which department you're in Discord—

Providingthey supportcare about getting results. A handoff failure between Onboarding and CSR is a client failure. A missed update between Dispute and CSR is a client failure. Own the handoff as much as you own your own tasks.

Department Interaction Map

From To Trigger What Passes Onboarding CSR Team Onboarding Call complete + docs collected Client profile, transition note, baseline scores, client concerns Onboarding Dispute Team All docs received + credit report pulled DisputeFox profile, credit report, target items list Dispute Team CSR Team Bureau response received / dispute round complete Results summary — what was removed, what remains, next strategy CSR Team Dispute Team Client submits new documents / client reports error on report New documents uploaded to DisputeFox, note with client context CSR Team Admin / Billing Failed payment, billing dispute, plan change request GHL contact note + escalation tag + verbal/Slack notification Admin / Billing CSR Team Payment resolved, plan changed, account updated Note in GHL, confirmation of resolution, any new subscription dates Dispute Team CSR Team Client is graduation-ready Graduation flag in DisputeFox, summary of all wins, score improvement data Any Team Team Lead / Ops Manager Escalation (legal, complaint, major issue) Written escalation note, attempted resolution steps, client details

Handoff Protocols

Onboarding when→ capacityCSR allowsTeam Handoff

This is the most important handoff in the client lifecycle. The CSR team will manage this client for months — they need a complete picture of who the client is.

What the Onboarding Specialist Must Do:

    Write a thorough transition note in GHL — include:
      Client's goals and motivation for joining Any concerns or skepticism the client expressed Client's communication preferences (prefers calls vs. texts, best contact times) Baseline credit scores from all three bureaus Top 3–5 items on the report that the client is most focused on Status of document collection Status of SmartCredit setup Update GHL pipeline stage to "Onboarding Complete" Tag the assigned CSR in the GHL note Post in team channel: "Handoff ready: {{contact.first_name}} [last initial]. Notes in GHL. Assigned to [CSR Name]."

      What the CSR Must Do Upon Receiving Handoff:

        Acknowledge the handoff in the team channel within 2 hours Read the full transition note in GHL Introduce yourself to the client via SMS within 48 hours: "Hi {{contact.first_name}}! This is [Your Name] — I'll be your main point of contact here at Crowned Credit going forward. I've reviewed your file and I'm excited to work with you. Feel free to reach out anytime!" Schedule a quick intro call if the client would benefit from it

        Onboarding → Dispute Team Handoff

        What the Onboarding Specialist Must Do:

          Confirm DisputeFox profile is fully set up (name, email, plan, start date) Confirm credit report from all 3 bureaus is pulled and visible in DisputeFox List the top dispute candidates in DisputeFox notes (based on onboarding call discussion) Upload all received documents to DisputeFox Move DisputeFox stage to "Credit Analysis" Notify Dispute Team in their channel: "New client ready for Round 1 analysis: {{contact.first_name}} [last initial]. DisputeFox profile live. Docs uploaded."

          What the Dispute Team Must Do:

            Acknowledge the notification Begin credit analysis within 3 business days If any documents are missing or unclear, notify Onboarding/CSR immediately — do not wait

            Dispute Team → CSR Team Handoff (Round Results)

            After every dispute round result is processed, the Dispute Team must brief the CSR so the client can be called with an update.

            Dispute Team Must Provide:

              Post a results update in the appropriate channel (or tag the CSR directly in GHL notes):
                Number of items deleted Number of items verified (and new strategy for each) Updated scores (if available) Recommended next round start date Update DisputeFox stage to "Round X – Response Received" Add detailed notes in DisputeFox for each item outcome

                CSR Must Do After Receiving Results:

                  Call the client with results within 48 hours Celebrate any deletions — make it a moment Explain what remains and what the plan is for Round 2 Log call notes in GHL

                  CSR → Admin/Billing Handoff

                  CSR Must:

                    Log the billing issue clearly in GHL notes: what happened, what the client said, date of issue Tag the conversation: billing-issue Notify billing team in team channel with: client name, GHL link, issue summary Communicate to client: "I've escalated this to our billing team and you'll hear back within [timeframe]." Do NOT promise refunds, credits, or specific resolutions — only billing can authorize those

                    Cross-Department Communication Standards

                    Where to Communicate

                    Channel Used For Not Used For GHL Notes All client-specific info, handoff notes, call logs, billing issues Team-wide announcements, general questions Team Channel (Slack/Discord) Handoff notifications, escalation alerts, shift updates, team announcements Sensitive client data, long-form discussions DisputeFox Notes Dispute-specific strategy notes, round results, bureau response details Billing info, general CRM data Direct Message Urgent person-to-person communication that needs immediate attention Anything that should be team-visible or logged
                    📋 The Golden Rule of Handoffs
                    Never assume the next person knows what you know. Write it down. Every handoff note should be written as if the recipient has never spoken to this client before — because sometimes, they haven't. Over-communicate on handoffs. Under-communication is what causes clients to fall through the cracks.

                    Handling Unowned or Orphaned Clients

                    Occasionally a client will contact us and it's unclear which team or rep owns their file. Here's how to handle it:

                      Search GHL by the client's phone number or email If a contact is found but has no assigned rep, take ownership temporarily Respond to the client immediately — never let a client wait because ownership is unclear Post in team channel: "Found orphaned client: {{contact.first_name}} [last initial]. Currently unassigned. Who owned this file?" Team Lead will reassign within 1 hour Transfer ownership in GHL and brief the new assignee via notes
                      Back to top