I Added Live Chat.Then I Stopped Answering.
Live chat looks great on a website. It signals availability, responsiveness, and customer care.
The problem is that it only works if someone's actually there to respond. I installed a chat widget, felt productive about it, then realized I'd created a tool that could damage trust the moment a visitor opened it and nobody replied.
The friction isn't the installation, most platforms handle that in minutes. The friction is the commitment.
Web.dev's performance research shows user expectations spike when they see an interactive element. A chat box sitting there unanswered is worse than no chat box at all.
I found myself choosing between hiring someone to monitor it around the clock, setting up aggressive auto-responders that felt impersonal, or turning it off entirely.
What I learned: live chat isn't a feature you add because it's trendy. It's a staffing decision disguised as a technical one.
If you can't staff it reliably, a simple contact form with a clear response-time promise is more honest. Our web design work starts with what you can actually maintain, not what looks complete.
Before installing live chat, decide who monitors it and when. If the answer is eventually or someone will, don't install it yet. A contact form with a 24-hour response guarantee beats a chat box that leaves people staring at silence.
