Key takeaways
- Emergencies still belong on the phone; chat and text suit routine jobs, quotes and status questions.
- Smartphones are near universal (91% of adults) and 79% of adults 65 and older own one, so every channel reaches most customers[1].
- Chat sets an expectation of a reply within minutes; an unanswered chat window does more harm than no chat at all.
- Staff chat with a phones-first rule, short saved replies and an after-hours handoff to text.
- Measure bookings per channel, not conversations, before adding or dropping a channel.
How customers choose a channel
People pick the channel that fits the moment. A homeowner with water coming through the ceiling calls, because they want a person now. Someone pricing a water heater replacement at work opens the website chat because they cannot talk at their desk. A tenant reporting a running toilet sends a text from the bus. Your job is not to push everyone to one channel; it is to make each channel lead to the right next step quickly.
Device ownership is not the limiting factor. In 2026, 91% of US adults owned a smartphone and 98% owned a cellphone of some kind; among adults 65 and older, 79% owned a smartphone and 96% a cellphone[1]. About 16% of adults are smartphone-dependent, meaning they go online by phone without home broadband[1], so your website chat must work well on a small screen.
- All adults
- Age 65+
Source: Pew Research Center, 2026[1]
Show the data
| Item | All adults | Age 65+ |
|---|---|---|
| Cellphone of any kind | 98% | 96% |
| Smartphone | 91% | 79% |
Channel by channel
| Channel | Best for | Customer expects | Main risk |
|---|---|---|---|
| Phone | Emergencies, complex problems, older customers, anything urgent | A person within a few rings | Missed calls when the office is busy or closed |
| Website chat | Routine bookings, service-area and fee questions, quote requests | A reply within a minute or two while the window is open | Unanswered chats that look abandoned |
| Text message | Status updates, reschedules, photos of the problem, tenants | A reply within the hour in business hours | Threads that nobody owns |
| Web form | Estimates, non-urgent requests, commercial inquiries | A reply the same or next business day | Forms that sit in an inbox overnight |
The pattern is simple. The more urgent the problem, the more the customer wants a live voice. The more the customer wants to compare, think or send a photo, the more they prefer a written channel. Design each channel around that.
Keep emergencies on the phone
The biggest risk with chat is a real emergency typed into a window nobody is watching. Every written channel should push urgent problems to the phone at once.
Chat greeting: "Hi, this is [Company]. If water is running and you can't shut it off, or sewage is coming up inside, please call us now at [number] so we can help right away. For everything else, tell me what's going on."
- Show the phone number at the top of the chat window and on every page of the site, tappable on mobile.
- If a chat mentions flooding, sewage, gas or no water, the reply is the phone number and shut-off guidance, not a booking form.
- Give after-hours chats and texts an automatic reply that states the emergency number and when written messages will be answered.
- Never let a chat bot or saved reply promise a time for an emergency it cannot dispatch.
Response expectations by channel
A chat window creates a promise the moment it opens. People expect a reply in a minute or two, while they are still on the page. If you cannot answer that fast, change the window to say so honestly or switch to a message form with a clear reply time. A chat that shows "Typically replies in a few minutes" and then goes silent for an hour is worse than no chat.
- Phone: answer within three or four rings during office hours; have overflow or after-hours coverage for the rest.
- Chat: first reply within two minutes while the visitor is on the page; otherwise, collect a phone number and text them.
- Text: reply within an hour during office hours and say when the next reply will come if it will be longer.
- Forms: same business day for anything that came in before mid-afternoon, next morning for the rest.
Write these targets down and check them monthly. If the phones are fine but chats wait twenty minutes, the problem is staffing, not the channel.
Staffing chat without hurting the phones
Most shops cannot hire a dedicated chat agent, so chat lands on the same CSR who answers the phone. That works if you set rules. Customer service representatives already juggle busy periods, including evenings and weekends[2]; adding chat without rules means both channels suffer at the Monday morning peak.
Phones first
A ringing phone always beats a chat. The CSR sends a saved "I'll be with you in a moment" reply and takes the call.
Cap concurrent chats
Limit each person to two or three open chats. Above that, new visitors see a message form instead of live chat.
Use saved replies
Prepare short replies for service area, hours, fees you share, booking steps and the emergency instruction. Keep them in your voice.
Capture a phone number early
Ask for a name and mobile number in the first exchange so the conversation can move to text or a call if the visitor leaves.
Hand off after hours
Outside office hours, turn live chat into a message form or route it to whoever covers your nights, with the emergency number shown first.
Texting is the bridge between channels
Text sits between the phone and the website, and it rescues conversations the other channels drop. A chat visitor who closes the tab, a caller who hung up in a queue and a form sender who never answered your callback can all be reached by text. That matters because calling back often fails: in Pew's 2020 survey, 80% of US adults said they don't generally answer calls from unknown numbers[3].
- Ask permission to text in every channel, and record it.
- Send the first text from the same number customers call, with your company name in the first line.
- Keep texts to one question or one piece of information each.
- Invite photos of the problem; a picture of a water heater label saves a diagnostic question.
- Assign every text thread to a named person so none go unanswered over a weekend.
What a good chat collects
A chat is only useful if it ends in a ticket dispatch can act on. Use the same minimum fields as the phone, gathered conversationally rather than as a form dumped into the window.
- Name and mobile number, with permission to text.
- Service address and ZIP code, so you can check the service area early.
- The problem in their words, plus a photo if they can send one.
- Whether water is still running, to catch hidden emergencies.
- Preferred day and time window.
- Owner or tenant, and the landlord's details if relevant.
Reviews follow every channel
Written channels leave a record, and customers remember slow or clumsy replies when they write reviews. In Pew's survey, 82% of US adults said they at least sometimes read online ratings or reviews before buying something for the first time[4]. A quick, helpful chat can become the line a customer quotes in a five-star review; a chat that ignored their flooded basement can become the opening of a one-star one.
Should you add chat at all?
Chat is worth adding when your phones are already answered well, your site gets steady traffic, and you have someone who can reply within minutes during the hours chat is open. It is not worth adding when calls already go to voicemail during peaks, because chat will take attention from the phone without fixing the bigger leak.
- Check your phone answer rate during peaks first. Fix that before adding a channel.
- Look at website traffic by hour. Open chat only for the hours you can staff.
- Start with chat on the booking and service pages, not every page.
- Track bookings per channel for three months, then decide whether to expand, shrink or drop it.
Example: adding chat to a five-truck shop
Example (fictional): A five-truck shop opens live chat from 8 am to 4 pm on weekdays, with one CSR covering both phone and chat under a phones-first rule and a cap of two open chats. In the first month the site gets 140 chats: 60 are service-area or fee questions answered with saved replies, 45 become booked jobs, 20 are quote requests passed to the estimator, and 15 go quiet. Three chats mention active leaks; each gets the phone number and shut-off guidance in the first reply, and two call in. Phone answer rate does not drop, because the cap keeps chat from crowding out calls, so the owner keeps the hours as they are and adds saved replies for the most common questions.
Frequently asked questions
Do plumbing customers use website chat?
Many do for routine jobs, quotes and service-area questions, especially when they cannot talk on the phone. Emergencies still mostly come by phone, and chat should send them there.
Should chat replace my phone line?
No. Chat adds a channel for non-urgent requests. Urgent problems need a live voice, so the phone number should be visible in the chat window and on every page.
Can one CSR handle phones and chat?
Yes, with a phones-first rule, a limit on open chats, saved replies and a message form when chat is full or closed.
How fast should I reply to a website chat?
Within a minute or two while the visitor is still on the page. If you can't, show a message form with an honest reply time instead of a live chat window.
References
Pew Research Center (2026). Mobile Fact Sheet (opens in a new tab) ↑
U.S. Bureau of Labor Statistics (2025). Occupational Outlook Handbook: Customer Service Representatives (opens in a new tab) ↑
Pew Research Center (2020). Most Americans don't answer cellphone calls from unknown numbers (opens in a new tab) ↑
Pew Research Center (2016). Online Reviews (Online Shopping and E-Commerce) (opens in a new tab) ↑