Information checked: 21 July 2026.
Live chat can help a customer at the point of difficulty, but an unattended widget, unclear bot or poorly governed transcript can reduce trust. Choose chat only when the business can staff, monitor and remove it safely.
In brief: Chat is useful only when its identity, scope, privacy, staffing and fallback are explicit.
Decide which service is being offered
Chat models
- Live human chat
- Customer expectation: A person is available now; Operational requirement: Staffing, queue and handover
- Asynchronous messaging
- Customer expectation: A later response; Operational requirement: Clear response time and notification
- Rules-based bot
- Customer expectation: Help with limited known tasks; Operational requirement: Visible scope and human route
- Generative chatbot
- Customer expectation: Flexible natural-language replies; Operational requirement: Knowledge control, monitoring and disclosure
Set boundaries
State whether the visitor is speaking to a person or automated system. Do not let a bot invent prices, policies, legal advice or commitments. Provide a route to a human and make it clear when the conversation is no longer monitored.
Control personal data
Collect the minimum information, explain transcript use, set retention and restrict staff access. Prevent users from submitting payment-card details or sensitive information in an ordinary chat. Review the supplier’s subprocessors and model-training terms.
Design for failure
If the widget fails, keep phone, email or booking routes visible. Do not cover content or controls on mobile. Ensure keyboard access, readable focus and a way to close the widget.
Acceptance test
Ask common, ambiguous and unsafe questions. Test after hours, handover, transcript export, deletion, mobile keyboard use and supplier disconnection. Publish only when the team owns the answers and escalation path.
Example: an after-hours promise nobody can honour
A chatbot tells a visitor that a refund will be issued within 24 hours, although it has no access to the order and the business policy says otherwise. Restrict automated answers to approved knowledge, label uncertainty and route commitments to a person. Review transcripts for recurring failures rather than treating every completed conversation as success.
What the business should retain
- Approved knowledge and prohibited topics
- Human escalation and service hours
- Transcript retention and access
- Supplier model-training settings
- Mobile and accessibility test
Sources and date checked
Technical and product information was checked against the following primary sources on 21 July 2026. Plans, interfaces and provider terms can change, so recheck them before purchase or migration.
Keep the decision under your control
Retain the relevant accounts, source material, supplier terms and recovery information. Recheck changing prices, interfaces and rules before acting.