Skip to content

Live chat

Live chat is described in four words: “Answer visitors in real time.”

Conversations sit in folders — All, Open and the rest — and a visitor who has not identified themselves appears as Guest. There is a search box, and ⌘K jumps to a conversation.

Turning on live chat is not adding a feature; it is publishing a promise to be present.

A chat widget nobody answers is worse than no chat widget. A shopper who types a question and waits does not conclude “they must be busy” — they conclude the store is abandoned, and they were already unsure enough to ask.

Before switching it on, answer one question honestly: who is watching it, during which hours? If the answer is “nobody, mostly”, a contact form sets a truthful expectation and a chat widget does not.

Most conversations begin as Guest. You do not have their order, their history or their name — so the first useful thing you can do is ask which order they mean, rather than guess from context you do not have.

The Open folder is the only one that matters minute to minute. An email inbox tolerates a day; an open chat tolerates minutes. Read the count as a queue length — and if it is regularly longer than one person can hold, the fix is staffing or published hours, not faster typing.

  • It does not say what a visitor sees outside your hours, whether transcripts are kept, or whether a conversation can be assigned to a person. None has been checked against the current screen, and the first is the one that decides whether switching it on is safe.
  • It does not cover the support ticket queue. Chat is synchronous; support is not.