appliedTrust and reassurance5 min read

Finding the reassurance your customers are missing

Adding trust badges is easy. Working out which doubt is stopping people from buying is the part that moves the number.

What you'll be able to doFind out which doubt is stopping customers before you add reassurance, put the right reassurance at the point the doubt arises, and recognise review practices that cross into deception.

“Can we add some trust signals?” usually arrives as a brief with a row of payment logos, a padlock, the words “secure checkout” and a star rating in the header. Sometimes the test wins, more often it’s flat, and in both cases nobody learns much, because nobody knew which worry the logos were meant to answer.

Reassurance works when it answers a specific doubt at the moment the customer has it. Will it arrive in time? What if it doesn’t fit? Is this a real company? Will I be charged more at the end? Is the product any good? Those are different worries with different answers, and they turn up at different points in the journey. A padlock does nothing for someone who’s wondering about returns.

Doubts vary more than you’d think

Baymard’s survey of US online shoppers gives a sense of the spread. Setting aside people who were only browsing, the most common reason given for abandoning a checkout was extra costs being too high, at 40%. Delivery being too slow came next at 20%, then distrust of the site with card details at 19%. An unsatisfactory returns policy was 13%, and not being able to see the total cost upfront was 12%.

Treat those as a prompt rather than a map of your own customers. They’re self-reported reasons from one population, and your business will have its own pattern. The useful point is that “trust” covers several separate problems, and site security is only one of them.

The kinds of reassurance

Reviews answer “is it any good?” and “do people like me buy this?”. The Spiegel Research Center at Northwestern found that a product with five reviews had a purchase likelihood 270% higher than one with none, and that purchase likelihood tended to peak for ratings between 4.0 and 4.7 and fall as the average approached a perfect 5. One reading of that is that shoppers find a spotless score less believable than a good one with a few complaints.

Guarantees and returns answer “what if it goes wrong?”. They work best stated plainly, close to the decision, with the terms a click away rather than buried in the footer. Delivery information answers “when will it come and what will it cost?”, and a date is more reassuring than a range of working days. Security cues answer “is my card safe?”, and belong on the payment step, where that worry lives. A real address, a phone number and named people answer “is this a real company?”, which matters most for a business the visitor hasn’t heard of.

Finding the doubt that’s costing you

Before anyone designs a reassurance test, find the doubt. A one-question poll at checkout or on exit, asking what nearly stopped someone buying, gets you the customer’s own words. Customer service logs and live chat transcripts are full of the questions people couldn’t answer from the page. Your reviews, and your competitors’ negative ones, show what people worry about after buying. Session recordings show people opening the returns policy in a new tab or hovering over delivery costs. Usability testing with think aloud lets you hear the hesitation as it happens.

Then group what you find and count it. The reassurance worth testing is the one that answers the most common doubt, placed at the point in the journey where that doubt shows up. A hypothesis like “customers hesitate at the basket because they can’t tell whether it will arrive before Saturday” gives you something to learn from whichever way the test goes.

Watch your guardrails too. Making a generous returns policy more prominent may lift sales and lift returns along with them, so measure both before calling it a win.

The shadow side

The manipulative version of reassurance is reassurance that isn’t true. Fake reviews, written by staff or bought in. Reviews from people with a connection to the business that isn’t disclosed. Showing only the five-star reviews while presenting them as the full picture. Inviting only happy customers to leave a review. Trust badges for awards nobody gave you.

Regulators have caught up with this. In the UK, paragraph 13 of Schedule 20 to the Digital Markets, Competition and Consumers Act 2024 bans submitting or commissioning fake consumer reviews, and requires businesses that publish reviews to take reasonable steps to prevent and remove fake ones. The CMA has published separate guidance on what that means in practice. In the US, the FTC’s 2024 rule bans fake reviews, paying for positive or negative sentiment, undisclosed insider reviews, using threats to suppress negative reviews, and claiming that the reviews on display are all or most of those submitted when negative ones have been held back because of their rating.

Cherry-picking also does you less good than it seems. If the Spiegel findings hold for your products, a page of nothing but five-star reviews is less persuasive than a mix, and a customer who finds out you hid the bad ones won’t believe the good ones either.

What to ask an agency

What evidence says this doubt exists, and how often does it come up? Where in the journey does it arise, and is the reassurance going there? If reviews are involved, are we showing all of them, and how are they sorted by default? Does the guarantee commit operations to something they can deliver? Which guardrail will tell us if the reassurance is attracting the wrong kind of order?

A brief that can answer those has found a doubt worth answering. If it can’t, send it back for research before anything gets built.

Put it to work

Pick your highest-value journey and gather a week of evidence on what makes people hesitate, from an exit or checkout poll, customer service logs and live chat. Group the doubts and count them before you propose any reassurance.

There is no right answer. Write yours first, then compare.

Sources

Shoshin is written by Another Web is Possible. Lessons are licensed CC BY-SA 4.0.Our promise.