Record the commitment while the account is open
When a customer agrees to pay, record the promise against the account with the agreed details and due date. Keep the conversation outcome and follow-up responsibility together. A note saying “will pay next week” gives the next collector too little information.
Illustrative example: an account holder agrees during a call to make a payment on Friday. The collector records the commitment, schedules follow-up and keeps the account history available for the next interaction. This is a workflow example, not a customer case study.
Keep promises and payments separate
Recording a promise should not make an account look recovered. The financial system must supply the payment update before the team can assess whether the commitment was met. Agree how payments are matched to accounts and how reconciliation exceptions are reviewed.
GoDesk supports payment imports and attribution alongside the promise lifecycle. Full, partial or unmatched payment situations need a defined operational process and reliable source data.
Give supervisors a view of what is due
Supervisors need to distinguish upcoming commitments, promises due for review, kept promises and broken promises. Grace periods and follow-up rules should be configured around the portfolio’s operating process.
This makes the next action more specific: check the payment update, contact the account holder, review the strategy or resolve a data mismatch. It also helps another collector continue the work without reconstructing the earlier conversation.
Review results by portfolio and team
Review promises alongside reported recovery and contact activity. A portfolio with many promises but few recorded payments needs investigation; call volume alone will not explain the issue.
When evaluating GoDesk, ask to see an account move from contact to promise, due-date review and payment update. Include both a kept and a broken commitment in the demonstration.
← All articles & guides