DisputeChat

Return a paginated, permission-scoped client directory with real CRM, connection, readiness, and attention signals. Use this data tool for client-list questions; use open_client_command_center when the user asks to see or explore the visual command center.

list_clients

List one client's negative credit items that a dispute round could challenge, grouped by bureau, with the creditor, what kind of negative mark it is, a masked account number, the balance, and how many times it has been disputed already. Each item also reports disputeInProgress: when true that item already has an open dispute, which the letter and round-creation steps reject, so leave it out rather than building a round around it. eligibleItems counts the items a new round could actually be built from — totalItems includes the held ones. Also returns the round number a new round would get. Use this before proposing a dispute so the round is built from real items. Returns canRun false with a plain reason when the client has not shared their report or runs their own disputes.

get_dispute_items

Render the interactive Client 360 for one visible DisputeChat client. Use search_clients or list_clients first to resolve clientId, then call this when the user asks to see or open the detailed visual client view.

open_client_360

Render the interactive DisputeChat Client Command Center. Use this whenever the user asks to see, browse, explore, filter, or open their client list. It shows live, permission-scoped data and lets the user click any row into Client 360.

open_client_command_center

Create a reviewable proposal to change one DisputeChat client's CRM workflow status. This does not change the CRM until an owner or admin approves it inside DisputeChat. Use search_clients first to resolve clientId.

propose_client_status_change

Create a reviewable proposal to append one note to a DisputeChat client. This does not change the CRM until an owner or admin approves it inside DisputeChat. Use search_clients first to resolve clientId.

propose_client_note

Create a reviewable proposal to start a dispute round for one client. This does not file anything until an owner or admin approves it. Call only immediately after get_dispute_letters, once the user has read the letters and said to proceed. Copy that result's roundNumber, grouping, bureau, itemIds, and exact body text into letterReview; approval and filing are bound to those exact stored bodies. Items already in dispute or no longer eligible are named as not included instead of disappearing. Leave an item's reason out to keep the one get_dispute_reasons chose.

propose_dispute_round

Create a reviewable proposal to add one lead (a prospect who is not a client yet) to DisputeChat. Use this when the user gives you a prospect's details in any form, including pasted text such as a voicemail, email, or message — extract the name and contact details and show them for confirmation. This does not add the lead until an owner or admin approves it. Never invent contact details that were not provided.

propose_new_lead

Use this when the mounted DisputeChat cockpit filters, searches, pages, or refreshes its client queue.

browse_client_cockpit

Search the connected organization's client roster by name and return only clients visible to the connected team member. An empty query returns the first visible clients.

search_clients

Get a plain count of how the connected organization is doing: clients (total, connected, invite still pending, reached their goal), the open lead pipeline by stage, recent activity such as dispute rounds sent, and the bureau response windows currently running (active, overdue, due soon, in flight). Use this for questions about the book of business overall, how the week or month went, or how many clients or leads there are. Response-window counts are current, not limited to the reporting period, because a deadline that passed weeks ago is still today's most urgent item. Counts respect the connected member's client visibility.

get_business_summary