01 / The work
Keep the exact terms in view.
A negotiator works with changing balances, expiring offers and incomplete information. A useful queue should explain what needs attention: missing intake, an unreviewed proposal, an expiration date or a funding assumption. A single score cannot explain the whole case.
02 / The process
A clearer path through offer review.
- Review the client’s debts and the recorded offer history. Keep each creditor proposal and revision distinct so the team can see how the terms changed.
- Use the negotiator desk to inspect the reason an item needs review. Check the offer’s expiration and the available funding scenario before proposing the next action.
- Bind customer acceptance to the exact offer version. Model an installment schedule with dates and cent-level totals, then require verified payment evidence before treating the settlement as complete.
03 / Context & decisions
What stays connected
Keep proposal, acceptance, installment schedule and verified payment as separate stages. An updated offer should retain the previous version; a creditor reply does not replace the client’s acceptance. The history should explain the next decision.
Current scope & remaining work
04 / Product status
What you can explore today.
- Working preview
- Offer history, explainable review queue, local approval modeling and installment scenarios.
- Prepared backend
- Exact-terms checks, guarded stage transitions and reversal-aware completion tests.
- Connection work remaining
- Authenticated consent, provider-confirmed settlements and production reconciliation.
05 / Common question
Does an offer in the system mean the debt is settled?
No. A proposal, customer acceptance, scheduled installment and verified payment are separate records. The product is being built to keep those distinctions visible.