Sales & Conversion· 5 min read

Building Trust in the First Message

What makes a first chat reply credible to a sceptical visitor: being specific, being honest about limits, and always giving a clear next step.


Walk into a small shop and within a few seconds you have a sense of the place. Someone looks up, says hello, and either knows their stock or does not. You forgive a lot if the person behind the counter is straight with you. You forgive very little if they are obviously reading from a script.

A chat window gets judged the same way, only faster and more harshly. Visitors have met plenty of chat widgets that ask for an email address before answering anything, or that reply to a clear question with "Great question! Let me connect you with our team." After a couple of those experiences, people arrive expecting to be disappointed.

That scepticism is the starting point. The first message, and the one after it, have to overcome it. Here is what actually does.

Two first replies to the same question

A visitor on a dental practice website types a simple question. First, the kind of reply that loses trust:

Visitor: do you take new patients

Assistant: Hi there!! Thanks so much for reaching out! We'd love to help you on your dental journey. Can I get your name and email so a member of our friendly team can get back to you?

Nothing in that reply answers the question. It is warm, but warm about nothing. And it asks for personal details in exchange for information the practice surely knows.

Now the version that builds trust:

Visitor: do you take new patients

Assistant: Yes, we're currently accepting new private patients. The first appointment is a full check-up, and the next available slots are usually within two weeks. I can take a booking request now, or tell you about fees first. Which would help?

The second reply is not cleverer. It is simply specific, it assumes the visitor wants an answer, and it offers a choice of next step. Both examples use invented details, so replace them with what your practice actually offers.

The ingredients of a credible reply

When a first impression in chat works, it tends to have most of these:

Why admitting limits increases trust

This one surprises owners. The instinct is to make the assistant seem as capable as possible. But visitors trust a source more when they see it decline something.

If a visitor asks a vet clinic's assistant whether their dog's symptoms are serious, the credible reply is not a guess. It is something like: "I can't assess symptoms, and if your dog is struggling to breathe or has collapsed, call the clinic or your nearest emergency vet now. For anything less urgent, I can take details so a vet or nurse calls you back." The assistant has just shown it will not bluff. Its answers about opening hours and fees now carry more weight.

The same applies to ordinary gaps. An assistant that says "I don't have that information, but I can pass your question to the team" is more believable than one that produces a confident, invented answer. That is the reason grounding matters: answers should come from your own content, and when the content does not cover something, the assistant should say so. There is more on this in how grounding keeps assistants accurate. SpideyChat works this way and records the unanswered question so you can add the answer later.

Things that quietly destroy trust

A few habits undo a good first message almost immediately.

Overpromising. "We can definitely fit you in this week!" when the assistant has no view of your diary. It cannot check a calendar, so it should capture the request and say a person will confirm.

Repeating the same line. Asking for an email a second time after the visitor has already declined.

Pretending to be a named human. Calling the assistant "Sarah from reception" when there is no Sarah reading the chat.

Emoji and exclamation marks in serious contexts. Fine for a cake shop. Jarring for a funeral director or an accountant chasing a tax deadline.

Hiding the exit. No way to reach a real person, or a handover that leads nowhere. If a team member is on duty, let them take over. If not, say when someone will reply.

Being clear that the visitor is talking to an assistant is covered in more detail in telling customers the receptionist is AI.

Auditing your own welcome and first replies

  1. Open your site in a private browser window and read the welcome message as a stranger. Ask whether it could belong to any other company. If yes, rewrite it with something specific.
  2. Ask your assistant the five questions new visitors most often ask. Read only the first sentence of each reply. Does it answer the question?
  3. Ask two questions you know are not covered. Check that it admits the gap rather than inventing something.
  4. Ask one sensitive question relevant to your field (a symptom, a legal situation, a complaint). Check it routes to a person or emergency service instead of advising.
  5. Count how many replies ask for contact details before giving anything useful. Aim for none.
  6. Look at the last line of each reply. Is there a next step?

Rewrite one message today

Start with the welcome message, because every visitor sees it. Replace any generic greeting with one sentence naming what the assistant helps with, specific to your business, and one sentence on when a person is available. Then run the six-step audit above and fix the worst reply you find. Small changes to the first exchange tend to matter more than anything further down the conversation.

Frequently asked questions

Should my website assistant say it is not a human?
Yes. Be upfront from the start, for example by naming it as the business's assistant. People react far worse to discovering it later than to being told at the beginning.
Is a friendly, casual tone better for building trust?
Friendly helps, but only if the content is useful. Match the tone your business uses in person, and never let personality replace a straight answer.
What should the welcome message say?
Say briefly what the assistant can help with and, if relevant, when a person is available. Avoid generic lines that could belong to any company.

Keep reading

Building Trust in the First Message · SpideyChat