Record the promise in the customer's words

A promise register starts with the exact words the customer heard or read. Paraphrasing too early hides the difference between we will call you today and we will try to call you today. Copy the sentence into the register and link the message or call record. The original wording is the evidence if the promise is later disputed.

Add the channel, the date, and the person who made the promise. A promise made in a chat has a different record than one made by phone. If the promise was made verbally, write it down immediately and note that it was verbal. A register that depends on memory will not survive a shift change.

Store the promise with the message identifier so the original wording can be opened later. If the customer quotes a sentence the team does not recognize, the identifier settles the question quickly. A register that stores only a paraphrase forces the team to search the whole thread. The identifier is a small field with a large payoff.

Tie every promise to a record and owner

Each promise needs a record identifier, such as an order number, ticket, or account. Without a record, the promise floats outside the system that the team actually works in. Add the owner who will keep the promise and the person who will check it. A promise with a record can be reviewed, while a promise without one becomes folklore.

If the promise spans several records, choose one as the anchor and link the others. Do not create a second register for each team, because split registers produce conflicting answers. The owner should be able to see every open promise for a customer in one view. A single view is the difference between coordination and guessing.

Separate a promise from an estimate

An estimate is a forecast, and a promise is a commitment. The two should never share the same language. Use a phrase such as we expect by Thursday for an estimate, and reserve we will deliver by Thursday for a commitment the team can keep. Train the team to hear the difference and to label it in the register.

When a customer asks for a date the team cannot guarantee, offer an estimate and explain what would make it firm. Record the condition that turns the estimate into a promise, such as receipt of a signed form. A clear condition protects the customer from a false expectation and protects the team from an impossible target. Review the condition with the owner before it is used in a customer message.

Write the promise language so the condition is visible to the customer. A sentence such as we will ship after the signed form arrives is clearer than a date with no explanation. The team should use the same phrasing in the register and in the message. Consistency makes it easier to spot when a promise has quietly become a guess.

Update the register when the promise changes

Promises change, and the register should change at the same moment. If the delivery date moves, update the date, the reason, and the person who told the customer. Do not leave the old date in place with a note in a private chat. The register is the shared truth, so an outdated entry is worse than no entry.

Send the customer a short update rather than waiting for them to ask. A revised promise should include the new date and the reason in plain language. Record the customer's response so the next owner knows whether the change was accepted. A promise that changes twice without a clear message erodes trust quickly.

Review promises that were missed

At the end of each week, list the promises that were missed and group them by cause. Common causes include an unrealistic estimate, a missing dependency, an owner who was away, and a process that nobody controlled. The cause matters more than the name of the person who answered the phone. Fix the cause before adding more reminders.

For each missed promise, record what the customer was told and when they were told it. A fast, honest update can preserve trust even when the date slips. A silent slip is the one that turns into a complaint. The review should produce one change to intake, one change to ownership, or one change to the promise language.

Ask the owner of the missed promise what would have made the date realistic, not what went wrong. The answer often reveals a dependency that was never recorded. Add that dependency to the register as a condition. A promise that names its condition is easier to keep and easier to renegotiate early.

Keep the register short enough to trust

A promise register with fifty columns will not be maintained. Keep the customer, the promise, the record, the owner, the date, and the status. Add a short note field for the condition or the reason. Everything else belongs in the linked record, not in the register.

Review the fields after the first month and remove any that nobody used. Ask the team whether the register helped them avoid a duplicate message or a missed date. If it did not, the design is wrong, not the team. A short register that people update is more valuable than a complete one they avoid.

Audit a small sample of register entries each month against the customer messages. Look for promises that were never recorded, dates that changed without a note, and owners who no longer work on the account. Fix the register before the next review, not after a complaint. A short audit keeps the shared truth from drifting.

If the promise fields and review rules are already defined but need a steady owner, promise tracking support can turn approved examples, decision lines, and review rules into a draft your manager can check. The manager still owns exceptions and final approval.

For the next step, compare this workflow with Run a weekly backlog aging review for a delegated queue and Build a shift handoff note that survives a time zone gap. For access and oversight, use the authoritative planning reference alongside your own policy.