Chat hell.

Real-time pressure, sold as helpfulness.

The green dot is a leash. The moment your customer sees it, they expect you to be there. The moment you're not, the green dot becomes a complaint.

Chat sells itself as customer service. For you, it's performance pressure.

What it does to your day

You sit down to ship a feature. The widget pings. You stop. You read. You answer. The customer thanks you. Twelve minutes later, ping again. New customer. Same loop. Your day fragments into 40 reply windows. Nothing ships.

You can't batch. You can't think. You can't go to lunch without checking your phone.

Every chat tool promises “set your hours” and “go offline.” Then the tool puts a “first response time” on your dashboard that climbs every minute you're slow. The number pretends to be a metric. It's a guilt counter.

What it does to your product

Real conversations have history. Chat doesn't. Tomorrow's session is a new transcript. Last week's question is gone. Last month's bug report is gone. Each chat is an island.

So you build escalation. You build “tickets.” You build a CRM bolted onto the chat tool. You build queues. You build dashboards. You shipped a chat widget. You ended up running a call center.

The myth: customers want chat

Customers don't pick chat because they prefer chat. They pick it because the alternative is your “Contact us” form with seven required fields. Given a choice between “type one line and get a reply” and “fill a form to maybe hear back in 48 hours,” chat wins by default.

Take away the form. Make email work like a one-line widget. The customer gets what they wanted: a reply that lands. Without the green dot.

What email actually does

Email lets you batch. Answer at nine. Answer at five. Skip the dinner table. Read every message in context, with the customer's full history next to it.

The customer doesn't get a slower reply. They get a better one — written by someone who isn't typing through a panic.