Overview

Live chat lets website visitors talk with your team through the same customer widget used for ticket intake. New conversations arrive in a shared inbox, can identify or create a contact from the visitor's email, and can become tickets when follow-up needs a durable support workflow.

From visitor to follow-up

  1. A visitor opens a support widget that has chat enabled.
  2. Scrambl shows the team as Online or Away based on saved hours and recent responder presence.
  3. The visitor starts a session and sends a message. If email collection is enabled, the conversation can link to a contact automatically.
  4. Responders receive a notification and answer from the Live Chat inbox.
  5. The team either closes the conversation or creates a ticket for work that should continue outside chat.

Status meanings

StatusWhat the visitor experience means
OnlineChat is enabled, the current time is inside configured hours, and at least one responder has the inbox open recently.
AwayChat is available but the team is outside hours or no responder is currently present. The offline message sets expectations.
DisabledThe chat option is hidden from every support widget.

Human and automatic replies

Agent replies are written by a teammate from the Inbox. Optional automatic replies can keep the conversation moving when nobody is available, using the business instructions saved in Settings. The transcript labels visitor, agent, assistant, and system messages so the source stays visible.

Design the handoff: Live chat is best for fast clarification. Convert the session to a ticket when the request needs investigation, ownership, attachments, an SLA, or a reply after the visitor leaves.

Next steps