Customers are the stakeholder group that management thinks it knows the most about. There is contact, there are figures, there is an account team that reports. That also makes this group the group where assumption creeps in fastest: because there is already so much data, a question that doesn't already seem answered is rarely asked anymore.
A structured conversation with customers does not start with satisfaction. Satisfaction is a result, not a diagnosis. What you want to know is whether customers recognize the commitments that were made. Not: do you find us reliable. Rather: which agreement was made, was it kept, and does the customer know that you know whether it was kept. That last part is the piece that is most often missing. A customer who sees a small commitment disappear without explanation draws a bigger conclusion than a customer who hears why an investment was postponed. The size of the promise does not determine the extent of the damage to trust; keeping it does.
The question you ask internally and the question you ask the customer must touch on the same subject, but not have the same format. Internally you ask: which commitments were made to this customer this quarter, and what is the status. Externally you do not ask about the commitment itself, but about the impression that remains: what has stayed with the customer from the contact, and what had he expected would happen. These are two inquiries running alongside each other, not one after the other. The difference between what is considered handled internally and what is experienced as unresolved externally is the first usable outcome. Not the average, not the report card: the gap.
Account teams generally report upward what is going well, and downplay what is not finished. That is not unwillingness; it is how reporting lines work. The result is that management has a picture that is systematically more favorable than what the customer experiences, precisely in the case of small, non-escalated commitments. The major delivery agreements are tracked, measured, and usually kept as well. The small ones: a callback agreement, a promised adjustment, a conversation that was supposed to follow, disappear into the gap in between. That gap is where trust slowly leaks away without there being an incident to point to.
Once the gap between the internal picture and the external picture is visible, the question is no longer what customers think — we do not know that, and we will not fill it in until the customer says so themselves. The question is which commitments were made to customers, by whom, and whether they were kept. A commitment tracker records that per commitment: who promised what, to whom, when, and whether it has been completed. Not as an assessment, but as record-keeping that is otherwise kept nowhere once a commitment is small enough to fall outside the formal project file. A signal rhythm repeats the external inquiry at fixed moments, so that a shift in the customer's perception is not only noticed when a contract is cancelled.
The pattern where small commitments cause more damage than large investments that don't go ahead is not unique to customers. Anyone who asks the same questions of suppliers, financiers or supervisory authorities often sees a similar gap between what is considered handled internally and what is experienced as open externally. That is not a reason to merge the conversations — each stakeholder group has its own language and its own expectations — but it is a reason to see the tracker as one instrument that is filled in separately per group.
This page describes how you structure the conversation with customers, not what customers think of you. The latter remains unknown until the customer says so, and the external inquiry is meant to obtain that statement, not to predict it. We draw no conclusion about satisfaction, loyalty or purchase intent. We record what was promised and what the customer knows of it, and leave the rest to the customer.
The Trust Baseline, including the commitment tracker and the signal rhythm for customers, is under construction. Anyone who wants to work with this as soon as it is available can sign up for the waiting list. There is currently no module to order and no advisory conversation to schedule; there is a place to be informed as soon as the instrument is ready.
Anyone wondering how much of the work around customer contact — recording commitments, following up on signals, preparing conversations — can already be done with the support of AI will find at the work scan of FTE TO AI a calculation per task of what part of it can be taken over.
Vraag maar. Het interessantste antwoord komt meestal van wie u nog niet heeft gesproken.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.