{"meta":{"slug":"how-to-win-over-a-customer","area":"organizzazione","data":"2026-10-03","autore":"Redazione Prodability","meta_title":"How to win over a customer without being charismatic","meta_description":"Trust matters more than likability: how to win over a customer with proven competence and promises kept, even without a born salesperson's charisma.","keyword_principale":"how to win over a customer","keywords_secondarie":"customer trust, customer acquisition, business reliability, consultative selling, sales follow-up","tags":["Business processes","Company culture","Procedures and SOPs"],"title":"How to win over a customer without being a charismatic salesperson","lunghezza":"12 min read","featuredVisual":{"kind":"image","src":"/article-assets/come-conquistare-un-cliente/en/how-to-win-over-a-customer.jpg","alt":"How to win over a customer without being a charismatic salesperson"}},"content":"# How to win over a customer without being a charismatic salesperson\n\nTo win over a customer, what matters more: coming across as likable or coming across as reliable?\n\nThe scene is familiar to anyone who sells something: a negotiation that seemed to have gone well. The customer smiled, asked questions, shook hands warmly.\n\nThen they signed with a competitor.\n\nWinning over a customer means earning the trust they need to choose you — and keep choosing you — even when there are alternatives. It doesn't mean being liked by them.\n\nThis article looks at why likability isn't enough to generate that trust, which factors really build it according to the available research, and how to turn these factors into a repeatable process that works even for people who don't feel like born salespeople.\n\n## What is the difference between being liked by a customer and winning them over\n\nThe two concepts are often used as synonyms. They aren't.\n\nLikability is a real lever of influence: Cialdini places it among the principles that steer decisions [4]. People tend to say yes to those they like.\n\nBut being liked by a customer and winning them over are different phenomena.\n\nBeing liked is a momentary state: it runs out when the conversation ends. Winning someone over is a decision the customer makes — and renews over time — when they assess whom to entrust with a problem, a budget, a part of their work.\n\nFor that decision, friendliness is not the main criterion. A very likable supplier who delivers late gets replaced. A not-so-brilliant supplier who keeps every commitment gets called back.\n\nKey point: likability can open a door, but it is not what drives the customer to sign and to stay.\n\nIf likability doesn't decide, what triggers the choice? To answer, it helps to first take a close look at the sales model many people have learned — and its limits.\n\n## How to recognize the likable-salesperson script and its limits\n\nTraditional sales training has spread a recognizable script, built around four moves.\n\nFirst move: build personal rapport, show interest in the customer's life. Second: bring a problem to the surface. Third: discredit the solutions the customer is already using. Fourth: present your own offer with a push of urgency.\n\nThis pattern could work when the customer met few salespeople. Today they meet it everywhere, and they recognize it.\n\nBased on experience observed in the field, one can hypothesize that artfully constructed friendliness produces the opposite of the intended effect: the customer perceives the technique and raises their defenses.\n\nOn the limits of this approach, the best-known argument is Neil Rackham's: closing and pressure techniques, effective in simple sales, lose effectiveness in complex, high-value sales, where the customer evaluates carefully [3].\n\nIn those negotiations, the salespeople with the best results were not the most brilliant: they were the ones who asked the most questions about the customer's problems before proposing any solution [3].\n\nKey point: the likability script misdiagnoses the problem. A customer who doesn't buy is, in many cases, not a customer who didn't have a good time: it is a customer who doesn't trust you.\n\nBut where exactly does a customer's trust come from? Research has given this question a fairly precise answer.\n\n## How to build customer trust: the three factors that really matter\n\nThe reference model on trust in professional relationships identifies three factors that make someone trustworthy: ability, benevolence and integrity [1].\n\nTranslated into the relationship with a customer, they mean three concrete things.\n\nAbility: the customer must perceive real competence on their problem. Not enthusiasm, not smooth talk: verifiable knowledge of the industry, of similar cases, of the alternatives.\n\nBenevolence: the customer must perceive that their interest comes before the immediate sale. Someone who advises against an unsuitable purchase is building this factor.\n\nIntegrity: the customer must observe consistency between what is said and what is done. Every promise kept is evidence; every promise broken is a contradiction.\n\nThese factors don't stay theoretical. A meta-analysis conducted specifically on the customer-salesperson relationship found that trust has a moderate but positive influence on purchasing attitudes, intentions and behaviors, and that its antecedents include competence, honesty and attention to the customer's interest — while personal likability is only one of the factors, not the pivot [2].\n\nThis is liberating news for anyone who doesn't see themselves as a charmer: of the three factors that generate trust, none requires charisma. All three can be demonstrated with facts.\n\nKey point: trust isn't asked for and it isn't acted out. It is demonstrated on three fronts — competence, genuine interest, consistency.\n\nThe first front, perceived competence, is also the one you can act on fastest. Let's see how.\n\n## How to position yourself as an expert on the problem, not the product\n\nA salesperson who knows only their own product is perceived as a talking brochure. A counterpart who knows the customer's problem is perceived as an advisor.\n\nThree practices help build this positioning.\n\nFirst practice: communicate about the industry, not the product. Periodically send your contacts useful updates on their market — trends, regulations, cases — instead of promotions alone. People who receive value before buying attribute competence to whoever sends it.\n\nSecond practice: in negotiations, present the full range of solutions to the customer's problem, including those that don't involve your own offer. Your proposal comes at the end, as the result of an analysis, not as the starting point. This is the direct application of what research observed in the most effective salespeople: first explore the problem, then the solution [3].\n\nThird practice: openly state the limits of your offer. Saying in which situations your product is not the best choice makes what you claim about its strengths more credible. Honesty, after all, is among the documented antecedents of trust [2].\n\nKey point: the expert is not the one who sells better, but the one who shows they know the problem better than anyone else courting the customer.\n\nThese practices build initial trust. But the trust that really wins over a customer is played out on even more concrete ground — and this is where the discussion changes nature.\n\n## Why reliability is an organizational fact, not a personality trait\n\nTrust, as we have seen, rests on integrity: consistency between what is said and what is done [1].\n\nIn everyday practice this consistency takes a precise form: small promises kept systematically. The document sent when it was promised. The quote that arrives within the stated time. The follow-up call made on the agreed day.\n\nNone of these actions wins over a customer on its own. Their sum, repeated without visible exceptions, does.\n\nAnd this is where a widespread misunderstanding emerges: considering reliability a personal gift, like charisma. Those who keep their promises would be \"serious people\"; those who forget them, unreliable.\n\nOperational reality is different. An attentive person keeps promises as long as there are few of them. When customers increase, commitments multiply and memory is no longer enough — not because of a character flaw, but because of a structural limit.\n\nThe central hypothesis of this article can therefore be stated like this: the reliability the customer perceives is not the reflection of a personality, it is the product of an organization. And like every product, it can be designed.\n\nHow, in concrete terms, do you design a company that keeps its promises by construction and not through goodwill? The sections that follow describe three interventions.\n\n## How to make follow-up punctual by design, not by memory\n\nEvery promise made to a customer is a deadline. The first intervention consists of treating it as such.\n\nThe operating rule: no commitment made to a customer stays only in the head of the person who made it. Every promise — \"I'll send you the quote by Thursday,\" \"I'll call you back after the trade show\" — is recorded the moment it is made, with a date and an owner.\n\nThe tool matters less than the method: it can be a CRM, a shared spreadsheet, a commitments log. What matters is that the system generates the reminder instead of the person.\n\nAdd to this a written follow-up procedure: who contacts the customer again, after how many days, with what content. When the follow-up is defined by a procedure, it happens even in peak weeks — which are exactly the ones when memory fails.\n\nKey point: punctual follow-up is not a matter of individual discipline, it is a matter of design. A tracked commitment is a commitment that will be kept even on a bad day.\n\nThe second intervention concerns a type of promise that many companies make without realizing it: response times.\n\n## How to give customers guaranteed response times\n\nEvery request left unanswered is an implicit promise not kept. A customer who writes and doesn't know when they will get an answer is silently forming their judgment of your reliability.\n\nThe intervention consists of defining internal response standards — for example: every request gets a first reply within one business day — and communicating them openly to the customer.\n\nBased on observed experience, one can hypothesize that the certainty of response times matters more than their speed: a reply promised within 24 hours and delivered on time builds more trust than answers that are sometimes immediate and sometimes missing. This is consistent with the role of behavioral consistency in the perception of integrity [1].\n\nThe standard doesn't require having the solution right away: it requires telling the customer that the request has been taken on and when they will get a complete answer.\n\nKey point: a stated response time turns an indefinite wait into a pact that is honored.\n\nThe third intervention remains, the most delicate one: what happens to trust when the promise changes hands.\n\n## How to align what sales promises with what operations delivers\n\nTrust won during a negotiation can be lost at delivery. It happens when the promises made by the salesperson don't reach, intact, the people who have to keep them.\n\nThe customer doesn't distinguish between departments: for them there is only one company that promised one thing and delivered another. The perceived inconsistency hits exactly the integrity factor [1].\n\nThe intervention consists of a formal handover between sales and operations: a document listing the commitments made — timelines, customizations, special conditions — shared with and confirmed by those who will have to carry them out, before delivery is promised to the customer.\n\nOnce this is up and running, add a periodic joint review: sales and operations compare what was promised with what was delivered, and adjust future promises based on real capacity.\n\nKey point: a company wins over customers when the people who promise and the people who deliver work from the same list of commitments.\n\nAt this point, the pieces of the path can be put back together.\n\n## Winning over a customer is an organizational skill: the summary\n\nThe path started from a question: do you need to be liked by the customer or do you need their trust?\n\nThe research answer is clear: trust is built on competence, genuine interest and consistency between words and actions [1] [2] — and none of these factors requires charisma.\n\nThe idea to take away, however, goes one step further: the consistency that generates trust is made of small promises kept systematically, and being systematic is not a character trait. It is a process: tracked commitments, designed follow-ups, standard response times, alignment between those who promise and those who deliver.\n\nIf you want to explore the organizational side of this approach, you can start with how to [create standard operating procedures](https://blog.prodability.com/procedure-operative-standard-sop/) that make these behaviors stable. And since even the best relationships go through critical moments, it helps to know in advance [how to handle a conflict with a customer](https://blog.prodability.com/gestire-un-conflitto-con-il-cliente-la-guida-in-9-passi/).\n\nA company that works this way changes its nature in the eyes of the market: customers stop wondering whether promises will be kept, quotes are evaluated with less suspicion, word of mouth starts on its own — because reliability, when it is systematic, becomes the trait you are remembered for.\n\nAnd this reputation, unlike likability, doesn't depend on anyone having a good day.\n\n## FAQ\n\n### Is likability useless for winning over a customer?\n\nNo. Likability is one of the levers of influence described by Cialdini [4] and it makes the first contact easier. The point is that it isn't enough: in considered purchasing decisions the customer mainly evaluates competence, honesty and demonstrated consistency [2]. Likability works as an accelerator of a trust that has to rest on verifiable facts, not as a substitute for it.\n\n### How do you win over a customer without sales experience?\n\nBy focusing on the factors that don't require technique: knowing the customer's problem in depth, honestly presenting all the available solutions, keeping every commitment made. According to Rackham, in complex negotiations the best results come from those who explore problems with questions, not from those who apply closing techniques [3].\n\n### How long does it take to build a customer's trust?\n\nThere is no documented standard time: it depends on what is at stake and on how often you are in contact. Trust grows as evidence accumulates — promises kept, timely answers, deliveries that match what was agreed — so the more opportunities you create to demonstrate consistency, the faster the process goes. A structured follow-up also serves this purpose: multiplying the evidence.\n\n### What is the difference between winning over a customer and building customer loyalty?\n\nWinning over concerns the first choice: getting the customer to sign with one supplier rather than another. Building loyalty concerns the following choices: making sure they keep buying over time. The mechanisms, however, converge: the same systematic reliability that wins over a new customer is what makes it uneconomical for them to change suppliers.\n\n## Sources and references\n\n1. Mayer, R. C., Davis, J. H., & Schoorman, F. D. (1995). An Integrative Model of Organizational Trust. *Academy of Management Review*, 20(3), 709–734. https://www.jstor.org/stable/258792 — foundational reference.\n\n2. Swan, J. E., Bowers, M. R., & Richardson, L. D. (1999). Customer Trust in the Salesperson: An Integrative Review and Meta-Analysis of the Empirical Literature. *Journal of Business Research*, 44(2), 93–107. https://www.sciencedirect.com/science/article/abs/pii/S0148296397002440 — foundational reference.\n\n3. Rackham, N. (1988). *SPIN Selling*. McGraw-Hill. — *Practical sales nonfiction. It presents the author's proprietary research, never published in a peer-reviewed venue and not verifiable at the primary source: cited for the arguments it makes, not as a source of data.*\n\n4. Cialdini, R. B. (1984). *Influence: The Psychology of Persuasion*. William Morrow. — foundational reference.","path":"content/articles/art-0017/en.md","routePath":"how-to-win-over-a-customer","wordCount":2444,"imageMeta":{"/article-assets/come-conquistare-un-cliente/come-conquistare-un-cliente.jpg":{"w":1200,"h":825},"/article-assets/come-conquistare-un-cliente/en/how-to-win-over-a-customer.jpg":{"w":1200,"h":825}},"html":"<p>The scene is familiar to anyone who sells something: a negotiation that seemed to have gone well. The customer smiled, asked questions, shook hands warmly.</p>\n<p>Then they signed with a competitor.</p>\n<p>Winning over a customer means earning the trust they need to choose you — and keep choosing you — even when there are alternatives. It doesn't mean being liked by them.</p>\n<p>This article looks at why likability isn't enough to generate that trust, which factors really build it according to the available research, and how to turn these factors into a repeatable process that works even for people who don't feel like born salespeople.</p>\n<h2 id=\"what-is-the-difference-between-being-liked-by-a-customer-and-winning-them-over\" class=\"article-h2-retrowave\"><span>What is the difference between being liked by a customer and winning them over</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"what-is-the-difference-between-being-liked-by-a-customer-and-winning-them-over\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>The two concepts are often used as synonyms. They aren't.</p>\n<p>Likability is a real lever of influence: Cialdini places it among the principles that steer decisions <a class=\"article-citation\" href=\"#rif-4\">[4]</a>. People tend to say yes to those they like.</p>\n<p>But being liked by a customer and winning them over are different phenomena.</p>\n<p>Being liked is a momentary state: it runs out when the conversation ends. Winning someone over is a decision the customer makes — and renews over time — when they assess whom to entrust with a problem, a budget, a part of their work.</p>\n<p>For that decision, friendliness is not the main criterion. A very likable supplier who delivers late gets replaced. A not-so-brilliant supplier who keeps every commitment gets called back.</p>\n<p>Key point: likability can open a door, but it is not what drives the customer to sign and to stay.</p>\n<p>If likability doesn't decide, what triggers the choice? To answer, it helps to first take a close look at the sales model many people have learned — and its limits.</p>\n<h2 id=\"how-to-recognize-the-likable-salesperson-script-and-its-limits\" class=\"article-h2-retrowave\"><span>How to recognize the likable-salesperson script and its limits</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"how-to-recognize-the-likable-salesperson-script-and-its-limits\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>Traditional sales training has spread a recognizable script, built around four moves.</p>\n<p>First move: build personal rapport, show interest in the customer's life. Second: bring a problem to the surface. Third: discredit the solutions the customer is already using. Fourth: present your own offer with a push of urgency.</p>\n<p>This pattern could work when the customer met few salespeople. Today they meet it everywhere, and they recognize it.</p>\n<p>Based on experience observed in the field, one can hypothesize that artfully constructed friendliness produces the opposite of the intended effect: the customer perceives the technique and raises their defenses.</p>\n<p>On the limits of this approach, the best-known argument is Neil Rackham's: closing and pressure techniques, effective in simple sales, lose effectiveness in complex, high-value sales, where the customer evaluates carefully <a class=\"article-citation\" href=\"#rif-3\">[3]</a>.</p>\n<p>In those negotiations, the salespeople with the best results were not the most brilliant: they were the ones who asked the most questions about the customer's problems before proposing any solution <a class=\"article-citation\" href=\"#rif-3\">[3]</a>.</p>\n<p>Key point: the likability script misdiagnoses the problem. A customer who doesn't buy is, in many cases, not a customer who didn't have a good time: it is a customer who doesn't trust you.</p>\n<p>But where exactly does a customer's trust come from? Research has given this question a fairly precise answer.</p>\n<h2 id=\"how-to-build-customer-trust-the-three-factors-that-really-matter\" class=\"article-h2-retrowave\"><span>How to build customer trust: the three factors that really matter</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"how-to-build-customer-trust-the-three-factors-that-really-matter\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>The reference model on trust in professional relationships identifies three factors that make someone trustworthy: ability, benevolence and integrity <a class=\"article-citation\" href=\"#rif-1\">[1]</a>.</p>\n<p>Translated into the relationship with a customer, they mean three concrete things.</p>\n<p>Ability: the customer must perceive real competence on their problem. Not enthusiasm, not smooth talk: verifiable knowledge of the industry, of similar cases, of the alternatives.</p>\n<p>Benevolence: the customer must perceive that their interest comes before the immediate sale. Someone who advises against an unsuitable purchase is building this factor.</p>\n<p>Integrity: the customer must observe consistency between what is said and what is done. Every promise kept is evidence; every promise broken is a contradiction.</p>\n<p>These factors don't stay theoretical. A meta-analysis conducted specifically on the customer-salesperson relationship found that trust has a moderate but positive influence on purchasing attitudes, intentions and behaviors, and that its antecedents include competence, honesty and attention to the customer's interest — while personal likability is only one of the factors, not the pivot <a class=\"article-citation\" href=\"#rif-2\">[2]</a>.</p>\n<p>This is liberating news for anyone who doesn't see themselves as a charmer: of the three factors that generate trust, none requires charisma. All three can be demonstrated with facts.</p>\n<p>Key point: trust isn't asked for and it isn't acted out. It is demonstrated on three fronts — competence, genuine interest, consistency.</p>\n<p>The first front, perceived competence, is also the one you can act on fastest. Let's see how.</p>\n<h2 id=\"how-to-position-yourself-as-an-expert-on-the-problem-not-the-product\" class=\"article-h2-retrowave\"><span>How to position yourself as an expert on the problem, not the product</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"how-to-position-yourself-as-an-expert-on-the-problem-not-the-product\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>A salesperson who knows only their own product is perceived as a talking brochure. A counterpart who knows the customer's problem is perceived as an advisor.</p>\n<p>Three practices help build this positioning.</p>\n<p>First practice: communicate about the industry, not the product. Periodically send your contacts useful updates on their market — trends, regulations, cases — instead of promotions alone. People who receive value before buying attribute competence to whoever sends it.</p>\n<p>Second practice: in negotiations, present the full range of solutions to the customer's problem, including those that don't involve your own offer. Your proposal comes at the end, as the result of an analysis, not as the starting point. This is the direct application of what research observed in the most effective salespeople: first explore the problem, then the solution <a class=\"article-citation\" href=\"#rif-3\">[3]</a>.</p>\n<p>Third practice: openly state the limits of your offer. Saying in which situations your product is not the best choice makes what you claim about its strengths more credible. Honesty, after all, is among the documented antecedents of trust <a class=\"article-citation\" href=\"#rif-2\">[2]</a>.</p>\n<p>Key point: the expert is not the one who sells better, but the one who shows they know the problem better than anyone else courting the customer.</p>\n<p>These practices build initial trust. But the trust that really wins over a customer is played out on even more concrete ground — and this is where the discussion changes nature.</p>\n<h2 id=\"why-reliability-is-an-organizational-fact-not-a-personality-trait\" class=\"article-h2-retrowave\"><span>Why reliability is an organizational fact, not a personality trait</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"why-reliability-is-an-organizational-fact-not-a-personality-trait\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>Trust, as we have seen, rests on integrity: consistency between what is said and what is done <a class=\"article-citation\" href=\"#rif-1\">[1]</a>.</p>\n<p>In everyday practice this consistency takes a precise form: small promises kept systematically. The document sent when it was promised. The quote that arrives within the stated time. The follow-up call made on the agreed day.</p>\n<p>None of these actions wins over a customer on its own. Their sum, repeated without visible exceptions, does.</p>\n<p>And this is where a widespread misunderstanding emerges: considering reliability a personal gift, like charisma. Those who keep their promises would be \"serious people\"; those who forget them, unreliable.</p>\n<p>Operational reality is different. An attentive person keeps promises as long as there are few of them. When customers increase, commitments multiply and memory is no longer enough — not because of a character flaw, but because of a structural limit.</p>\n<p>The central hypothesis of this article can therefore be stated like this: the reliability the customer perceives is not the reflection of a personality, it is the product of an organization. And like every product, it can be designed.</p>\n<p>How, in concrete terms, do you design a company that keeps its promises by construction and not through goodwill? The sections that follow describe three interventions.</p>\n<h2 id=\"how-to-make-follow-up-punctual-by-design-not-by-memory\" class=\"article-h2-retrowave\"><span>How to make follow-up punctual by design, not by memory</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"how-to-make-follow-up-punctual-by-design-not-by-memory\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>Every promise made to a customer is a deadline. The first intervention consists of treating it as such.</p>\n<p>The operating rule: no commitment made to a customer stays only in the head of the person who made it. Every promise — \"I'll send you the quote by Thursday,\" \"I'll call you back after the trade show\" — is recorded the moment it is made, with a date and an owner.</p>\n<p>The tool matters less than the method: it can be a CRM, a shared spreadsheet, a commitments log. What matters is that the system generates the reminder instead of the person.</p>\n<p>Add to this a written follow-up procedure: who contacts the customer again, after how many days, with what content. When the follow-up is defined by a procedure, it happens even in peak weeks — which are exactly the ones when memory fails.</p>\n<p>Key point: punctual follow-up is not a matter of individual discipline, it is a matter of design. A tracked commitment is a commitment that will be kept even on a bad day.</p>\n<p>The second intervention concerns a type of promise that many companies make without realizing it: response times.</p>\n<h2 id=\"how-to-give-customers-guaranteed-response-times\" class=\"article-h2-retrowave\"><span>How to give customers guaranteed response times</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"how-to-give-customers-guaranteed-response-times\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>Every request left unanswered is an implicit promise not kept. A customer who writes and doesn't know when they will get an answer is silently forming their judgment of your reliability.</p>\n<p>The intervention consists of defining internal response standards — for example: every request gets a first reply within one business day — and communicating them openly to the customer.</p>\n<p>Based on observed experience, one can hypothesize that the certainty of response times matters more than their speed: a reply promised within 24 hours and delivered on time builds more trust than answers that are sometimes immediate and sometimes missing. This is consistent with the role of behavioral consistency in the perception of integrity <a class=\"article-citation\" href=\"#rif-1\">[1]</a>.</p>\n<p>The standard doesn't require having the solution right away: it requires telling the customer that the request has been taken on and when they will get a complete answer.</p>\n<p>Key point: a stated response time turns an indefinite wait into a pact that is honored.</p>\n<p>The third intervention remains, the most delicate one: what happens to trust when the promise changes hands.</p>\n<h2 id=\"how-to-align-what-sales-promises-with-what-operations-delivers\" class=\"article-h2-retrowave\"><span>How to align what sales promises with what operations delivers</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"how-to-align-what-sales-promises-with-what-operations-delivers\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>Trust won during a negotiation can be lost at delivery. It happens when the promises made by the salesperson don't reach, intact, the people who have to keep them.</p>\n<p>The customer doesn't distinguish between departments: for them there is only one company that promised one thing and delivered another. The perceived inconsistency hits exactly the integrity factor <a class=\"article-citation\" href=\"#rif-1\">[1]</a>.</p>\n<p>The intervention consists of a formal handover between sales and operations: a document listing the commitments made — timelines, customizations, special conditions — shared with and confirmed by those who will have to carry them out, before delivery is promised to the customer.</p>\n<p>Once this is up and running, add a periodic joint review: sales and operations compare what was promised with what was delivered, and adjust future promises based on real capacity.</p>\n<p>Key point: a company wins over customers when the people who promise and the people who deliver work from the same list of commitments.</p>\n<p>At this point, the pieces of the path can be put back together.</p>\n<h2 id=\"winning-over-a-customer-is-an-organizational-skill-the-summary\" class=\"article-h2-retrowave\"><span>Winning over a customer is an organizational skill: the summary</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"winning-over-a-customer-is-an-organizational-skill-the-summary\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<p>The path started from a question: do you need to be liked by the customer or do you need their trust?</p>\n<p>The research answer is clear: trust is built on competence, genuine interest and consistency between words and actions <a class=\"article-citation\" href=\"#rif-1\">[1]</a> <a class=\"article-citation\" href=\"#rif-2\">[2]</a> — and none of these factors requires charisma.</p>\n<p>The idea to take away, however, goes one step further: the consistency that generates trust is made of small promises kept systematically, and being systematic is not a character trait. It is a process: tracked commitments, designed follow-ups, standard response times, alignment between those who promise and those who deliver.</p>\n<p>If you want to explore the organizational side of this approach, you can start with how to <a href=\"https://blog.prodability.com/en/standard-operating-procedures/\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"article-inline-link\">create standard operating procedures</a> that make these behaviors stable. And since even the best relationships go through critical moments, it helps to know in advance <a href=\"https://blog.prodability.com/en/resolve-customer-conflict/\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"article-inline-link\">how to handle a conflict with a customer</a>.</p>\n<p>A company that works this way changes its nature in the eyes of the market: customers stop wondering whether promises will be kept, quotes are evaluated with less suspicion, word of mouth starts on its own — because reliability, when it is systematic, becomes the trait you are remembered for.</p>\n<p>And this reputation, unlike likability, doesn't depend on anyone having a good day.</p>\n<h2 id=\"faq\" class=\"article-h2-retrowave\"><span>FAQ</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"faq\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<h3 id=\"is-likability-useless-for-winning-over-a-customer\">Is likability useless for winning over a customer?</h3>\n<p>No. Likability is one of the levers of influence described by Cialdini <a class=\"article-citation\" href=\"#rif-4\">[4]</a> and it makes the first contact easier. The point is that it isn't enough: in considered purchasing decisions the customer mainly evaluates competence, honesty and demonstrated consistency <a class=\"article-citation\" href=\"#rif-2\">[2]</a>. Likability works as an accelerator of a trust that has to rest on verifiable facts, not as a substitute for it.</p>\n<h3 id=\"how-do-you-win-over-a-customer-without-sales-experience\">How do you win over a customer without sales experience?</h3>\n<p>By focusing on the factors that don't require technique: knowing the customer's problem in depth, honestly presenting all the available solutions, keeping every commitment made. According to Rackham, in complex negotiations the best results come from those who explore problems with questions, not from those who apply closing techniques <a class=\"article-citation\" href=\"#rif-3\">[3]</a>.</p>\n<h3 id=\"how-long-does-it-take-to-build-a-customers-trust\">How long does it take to build a customer's trust?</h3>\n<p>There is no documented standard time: it depends on what is at stake and on how often you are in contact. Trust grows as evidence accumulates — promises kept, timely answers, deliveries that match what was agreed — so the more opportunities you create to demonstrate consistency, the faster the process goes. A structured follow-up also serves this purpose: multiplying the evidence.</p>\n<h3 id=\"what-is-the-difference-between-winning-over-a-customer-and-building-customer-loyalty\">What is the difference between winning over a customer and building customer loyalty?</h3>\n<p>Winning over concerns the first choice: getting the customer to sign with one supplier rather than another. Building loyalty concerns the following choices: making sure they keep buying over time. The mechanisms, however, converge: the same systematic reliability that wins over a new customer is what makes it uneconomical for them to change suppliers.</p>\n<h2 id=\"sources-and-references\" class=\"article-h2-retrowave\"><span>Sources and references</span><button type=\"button\" class=\"article-heading-link\" data-copy-id=\"sources-and-references\" aria-label=\"Copy link to section\"><svg xmlns=\"http://www.w3.org/2000/svg\" width=\"16\" height=\"16\" viewBox=\"0 0 24 24\" fill=\"none\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><path d=\"M9 17H7A5 5 0 0 1 7 7h2\"/><path d=\"M15 7h2a5 5 0 1 1 0 10h-2\"/><line x1=\"8\" x2=\"16\" y1=\"12\" y2=\"12\"/></svg></button></h2>\n<ol class=\"article-process-list\">\n<li>\n<p>Mayer, R. C., Davis, J. H., &amp; Schoorman, F. D. (1995). An Integrative Model of Organizational Trust. <em>Academy of Management Review</em>, 20(3), 709–734. <a href=\"https://www.jstor.org/stable/258792\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"article-inline-link\">https://www.jstor.org/stable/258792</a> — foundational reference.</p>\n</li>\n<li>\n<p>Swan, J. E., Bowers, M. R., &amp; Richardson, L. D. (1999). Customer Trust in the Salesperson: An Integrative Review and Meta-Analysis of the Empirical Literature. <em>Journal of Business Research</em>, 44(2), 93–107. <a href=\"https://www.sciencedirect.com/science/article/abs/pii/S0148296397002440\" target=\"_blank\" rel=\"noopener noreferrer\" class=\"article-inline-link\">https://www.sciencedirect.com/science/article/abs/pii/S0148296397002440</a> — foundational reference.</p>\n</li>\n<li>\n<p>Rackham, N. (1988). <em>SPIN Selling</em>. McGraw-Hill. — <em>Practical sales nonfiction. It presents the author's proprietary research, never published in a peer-reviewed venue and not verifiable at the primary source: cited for the arguments it makes, not as a source of data.</em></p>\n</li>\n<li>\n<p>Cialdini, R. B. (1984). <em>Influence: The Psychology of Persuasion</em>. William Morrow. — foundational reference.</p>\n</li>\n</ol>","headings":[{"level":2,"text":"What is the difference between being liked by a customer and winning them over","id":"what-is-the-difference-between-being-liked-by-a-customer-and-winning-them-over"},{"level":2,"text":"How to recognize the likable-salesperson script and its limits","id":"how-to-recognize-the-likable-salesperson-script-and-its-limits"},{"level":2,"text":"How to build customer trust: the three factors that really matter","id":"how-to-build-customer-trust-the-three-factors-that-really-matter"},{"level":2,"text":"How to position yourself as an expert on the problem, not the product","id":"how-to-position-yourself-as-an-expert-on-the-problem-not-the-product"},{"level":2,"text":"Why reliability is an organizational fact, not a personality trait","id":"why-reliability-is-an-organizational-fact-not-a-personality-trait"},{"level":2,"text":"How to make follow-up punctual by design, not by memory","id":"how-to-make-follow-up-punctual-by-design-not-by-memory"},{"level":2,"text":"How to give customers guaranteed response times","id":"how-to-give-customers-guaranteed-response-times"},{"level":2,"text":"How to align what sales promises with what operations delivers","id":"how-to-align-what-sales-promises-with-what-operations-delivers"},{"level":2,"text":"Winning over a customer is an organizational skill: the summary","id":"winning-over-a-customer-is-an-organizational-skill-the-summary"},{"level":2,"text":"FAQ","id":"faq"},{"level":3,"text":"Is likability useless for winning over a customer?","id":"is-likability-useless-for-winning-over-a-customer"},{"level":3,"text":"How do you win over a customer without sales experience?","id":"how-do-you-win-over-a-customer-without-sales-experience"},{"level":3,"text":"How long does it take to build a customer's trust?","id":"how-long-does-it-take-to-build-a-customers-trust"},{"level":3,"text":"What is the difference between winning over a customer and building customer loyalty?","id":"what-is-the-difference-between-winning-over-a-customer-and-building-customer-loyalty"},{"level":2,"text":"Sources and references","id":"sources-and-references"}],"tldr":"To win over a customer, what matters more: coming across as likable or coming across as reliable?","tldrItems":null}