approve_action
ChatGPTExecute or deny a pending action proposal that this connection created. Call only after the user has explicitly confirmed the exact action in this conversation. Approving applies the change in DisputeChat immediately and returns the execution receipt; denying closes the proposal. A dispute round is the one action that is not reversible from chat — it files real disputes and prepares real letters, so confirm the client and the items by name before approving one, and never approve one twice.
browse_client_cockpit
ChatGPTUse this when the mounted DisputeChat cockpit filters, searches, pages, or refreshes its client queue.
get_action_status
ChatGPTCheck whether a previously proposed DisputeChat CRM action is still pending, was denied, failed, expired, or executed successfully. Returns the stored execution receipt when available.
get_business_summary
ChatGPTGet 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_client_360
ChatGPTReturn the structured, live 360-degree view for one visible client: access, CRM status, scores, readiness, dispute round, mailing, monitoring, and recent verified activity. Full credit details fail closed unless the client has active full sharing. Use open_client_360 when the user asks to see the visual 360 view.
get_client_status
ChatGPTGet a grounded status report for one visible client, including authorization, dispute progress, scores, mailing, monitoring, and readiness when the client's sharing permission allows it. Use search_clients first to resolve clientId.
get_connection_context
ChatGPTConfirm which DisputeChat organization, member role, and client visibility scope this connection can read. Use this before answering organization-wide questions.
get_dispute_items
ChatGPTList 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_letters
ChatGPTDraft the dispute letters for one client's round and return the full text of each, exactly as it would be mailed — usually one letter per bureau covering every item at that bureau. Nothing is saved: this is a draft to read and adjust before the round is created. Each letter reports whether it is ready to mail and, if not, what to fix. Items with a dispute already in progress are left out and returned in alreadyOpenItemIds. Call this after get_dispute_reasons.
get_dispute_reasons
ChatGPTFor items already picked for a dispute round, return the reason each one should be disputed under — already chosen, so nothing needs to be asked item by item. The reason comes from the contradiction the dispute engine found in that account's own data, with the finding in why; when there is no finding, the reason is the standard one and why is null. Also returns the five reasons an owner can switch to. Call this after get_dispute_items and before get_dispute_letters.
get_leads
ChatGPTList the connected organization's leads — prospects who have not become clients yet — with their pipeline stage, where they came from, contact details, and how long they have been waiting. Use this for any question about leads, prospects, or the top of the funnel. Filter by stage to answer questions like which leads are new or need a follow-up.
get_needs_attention
ChatGPTGet the real, prioritized list of visible clients and invitations needing attention today. This is read-only and never sends a message or starts a dispute.
inspect_client_cockpit
ChatGPTUse this when the mounted DisputeChat cockpit expands or refreshes one visible client row.
list_clients
ChatGPTReturn 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.
open_client_360
ChatGPTRender 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_command_center
ChatGPTRender 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.
propose_client_note
ChatGPTCreate 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_status_change
ChatGPTCreate 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_dispute_round
ChatGPTCreate 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_new_lead
ChatGPTCreate 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.
search_clients
ChatGPTSearch 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.