Knowledge · Business Operations

    Payment Promises and Follow-Up History

    How to capture what a customer promised, when, and to whom — and why a written follow-up history changes both the tone and the outcome of collections calls.

    What is a payment promise in collections?

    A payment promise is a customer's specific commitment to pay an amount by a date. To be useful it has to be recorded with the amount, the date, the person who committed, and who took the call — then followed up on that date. An unrecorded promise is a rumour.

    Key takeaways

    • Capture amount, date, who committed and who heard it — every time.
    • A promise creates a follow-up obligation on your side, not just theirs.
    • Broken promises are the strongest escalation signal you have.
    • Follow-up history must survive staff turnover.
    • Tone improves when the history is visible: you stop guessing what was said.

    What a usable promise record contains

    • The invoice or invoices it covers.
    • The amount promised — often less than the full balance.
    • The date promised, as a real date rather than "next week".
    • The named person who made the commitment.
    • The channel and the person on your side who took it.
    • A follow-up scheduled for the day after the promised date.

    Why history changes the conversation

    Collections goes badly when the caller has no memory. Repeating the same opening question to a customer who has already explained themselves twice reads as incompetence, and it hands them a reason to delay again.

    With history visible, the call opens differently: "On the 4th you said the 20th, and we agreed $2,100 of the $5,400 — where are we?" That is not aggressive, it is specific, and specific is what gets paid.

    Second and third broken promises

    • One broken promise is normal life. Re-book it and move on.
    • Two suggests the commitment was never real — change who is on the call.
    • Three is an escalation trigger, and the response is a business decision.
    • Record the pattern; do not rely on the frustration of whoever is chasing.

    Where URBLD fits

    URBLD keeps an append-only activity timeline on receivables alongside notes on the invoice and customer, so calls, contacts and commitments stay attached to the record rather than to a person. There is no dedicated promise-to-pay field or automatic promise reminder today.

    Principles reinforced

    This page rests on the following foundational ideas.

    FAQ

    Frequently Asked Questions

    Straight answers about how URBLD runs the business end-to-end.

    More in Business Operations

    The daily mechanics: workflows, checklists, scheduling and handoffs.

    Browse Business Operations
    Share this page