Live chat and messaging support

Use live chat when an available agent and customer can work through a question together. Use persistent messaging when either person may need to leave and return. In both modes, tell customers when to expect a reply and give unfinished work a monitored path forward. A widget labelled “chat” by itself does not promise an immediate answer.

Make the response promise visible

Show live chat only when the team can accept it, and explain what happens when it is unavailable. Help Scout’s Beacon presents live chat when a user is available and shows a message screen when the team is unavailable. This is Help Scout behaviour, not a rule for every widget.

Messaging can remain available outside staffed hours. Zendesk’s messaging Web Widget stays available when agents are offline, and Zendesk advises telling customers when staff will respond. An acknowledgement alone does not answer that question.

Choose a promise the team can cover. If an Australian team serves customers across time zones, state the applicable hours and time zone rather than saying only “business hours”. Assign someone to messages received while the team is away.

Live chat vs persistent messaging: key differences in availability and customer experience

Use availability controls as guardrails

Help Scout provides separate chat statuses: Available accepts incoming chats; Assign Only prevents new chats but allows teammates to assign ongoing ones; and Unavailable removes the user from Beacon and prevents new or assigned chats.

Custom availability can differ by inbox, which can help teams match coverage to particular queues.

Help Scout also changes a user to Unavailable when it detects they have logged out, closed all Help Scout browser windows, lost their internet connection or put their computer to sleep.

If an available user does not accept a missed chat within five minutes, Help Scout changes users who were available in that inbox to Assign Only. This applies across all inboxes where they were available.

Set a capacity limit that reflects the work involved, not just the number of agents on shift. Help Scout’s maximum-chat setting defaults to three, and Help Scout suggests that two to five may help prevent customers waiting; at the limit, an agent’s status changes to Assign Only. The setting counts chats across chat-enabled inboxes.

Plan the offline experience for each mode

Zendesk live chat prevents customers starting a chat when all agents are logged out or set to Invisible. Teams can use operating hours to switch off live chat on a schedule, then offer an offline form or contact form so customers can leave a request for later follow-up.

Zendesk messaging behaves differently: customers can resume a conversation, and the messaging widget cannot be turned off to prevent that. Zendesk recommends setting business hours and using a business-hours condition in the bot to tell customers when staff are unavailable and when they can expect to hear back. Make the wording match the response promise your team can meet.

Pros and cons of using persistent messaging for Australian businesses

Decide what the conversation must retain

Live chat is a session with a beginning and end. Persistent messaging can pause and resume; it can also support a rapid exchange. Zendesk documents both patterns for its channels. A retained thread helps only when the returning agent can identify the issue and see the relevant history.

Decide what must be visible on return: the customer’s question, earlier answers, any promised action, the current owner and a usable reply route. Treat a new issue from the same customer separately when continuing the old thread would obscure what needs doing.

An email address typed into a chat is not proof that the visitor owns an account. Follow the organisation’s identity procedure before discussing account-specific details. Check how the chosen product recognises a returning customer.

Give each mode an operating path

For live chat, decide who accepts new chats, how many simultaneous chats an agent can handle, who takes over at shift end and how a later answer reaches the customer. For messaging, decide who checks new messages and returned replies, including replies that arrive when the original agent is away.

When an issue needs investigation, record the remaining action, owner and next customer update. A platform may already have created a ticket for the messaging request. The operational decision is whether that record now makes unfinished work visible; creating another ticket could split the history.

Before moving a reply to email or another channel, confirm that the destination can reach the customer and that the next agent can see the earlier exchange. Available channels depend on the product and its configuration.

Operating path for live chat support in Australian businesses

Check the customer journey

Walk through an enquiry resolved during chat, an overnight message, a customer who leaves mid-conversation and a question needing a specialist. For each, identify what the customer was told, who owes the next response, what the next agent can see and where the reply will arrive.

Review coverage when availability changes

Test the customer experience at the edges of staffed time as well as during a normal shift. Confirm that the message shown to customers remains accurate when agents are offline or a conversation is resumed.

Checklist: ensuring compliance with Australian electronic commerce guidelines