Live Chat
How Octocom makes sure web chat replies reach the customer: the availability rules, the email Octocom sends after ten minutes when a reply goes unseen, and when the conversation moves between chat and email.
Every web chat reply, from your team or from the AI agent, has to survive one hazard: a reply delivered to a widget nobody is looking at is a reply nobody ever receives. It doesn't bounce, it doesn't notify anyone, it simply sits there. Email, by contrast, always arrives.
Octocom handles that in two parts:
Replies go to the chat widget. If a reply sits unseen there for ten minutes, Octocom emails the customer a copy, so they have the answer in their inbox. The conversation itself stays on chat: it only moves to email when the customer replies by email, and it moves back when they return to the widget.
This page explains how a reply counts as seen, what the email contains, what makes live chat count as "available" for a handed-off conversation, and when the reply channel changes.
The principle: observed, not predicted
Octocom does not try to work out in advance whether a customer is still around. It cannot: a minimised window, a background tab, a phone that locked, a customer reading the page below the widget — none of these are distinguishable from someone who closed the tab and left for the day, and treating them as departures sends cold emails to people who are sitting right there.
So the reply goes to the widget, where the customer asked for it, and Octocom watches what happens next. If the customer was there, they saw it and nothing else happens. If ten minutes pass with no sign of them, they get an email with the reply. Getting that judgement wrong is cheap in one direction (a customer reads their answer twice) and expensive in the other, which is why the check is generous and the email always goes out.
This is also why the unseen-reply email cannot be switched off. Disabling it would not make replies reach the widget; it would mean a customer who closed the tab never receives their answer at all.
When live chat counts as available
Live chat availability is checked when the conversation is handed off, and then re-checked continuously for as long as the conversation stays open. All of the following must hold:
| Condition | Detail |
|---|---|
| It's a web chat conversation | Conversations that arrived by email or other channels never switch to the widget. |
| Live chat is enabled | A per-business Handoff setting. With it off, handoffs go straight to email. |
| Someone can actually answer | At least one eligible agent is currently available — see below. |
"Someone can answer" means at least one eligible agent is currently available: not marked as unavailable, inside their working hours (if working-hour availability is enabled for your organization), and with the dashboard open (if activity-based availability is enabled). If an assignment rule routes the conversation to a specific team or person, only that team or person is counted.
If live chat is not available at the moment of handoff, the reply channel is set to email immediately and the customer is told the team will follow up by email. This is not final — see Switching back to chat below.
What the customer sees after a handoff
After the AI agent's handoff message, the bot stays silent. The widget shows a status above the message box instead, so the customer knows what happens next without an automatic reply to every message:
| Status | When |
|---|---|
| Waiting for an agent · Usually replies within 5 min | The team will answer in the chat and nobody has yet. The time is your live chat's expected response time; without one it says an agent will be with them shortly. |
| Our team will reply by email | The reply goes by email instead: nobody was available at the handoff, the chat moved to email later, or the handoff came from a custom action that didn't choose a channel. Shown only when Octocom has the customer's email address. |
| Passed to our team · They'll reply as soon as they can | The team has the conversation, but Octocom can't promise a channel: no email address is known, and the reply isn't coming in the chat. |
- It updates by itself. When the conversation moves to email, or back to chat when the customer returns, the status changes within seconds.
- It disappears once an agent replies in the chat, or the conversation closes. Assigning the conversation alone does not end the wait: the customer is waiting until someone writes.
- The customer can keep writing. Their messages reach your team; the bot does not reply to them.
- It's in the customer's language (English, Spanish, Lithuanian, Norwegian, Greek and Russian), and screen readers announce changes.
- Chats routed into an external live chat show no status. LiveChat shows its own "Connecting you to a human agent" message and locks the message box until an agent joins. Zendesk chats show neither.
How Octocom knows a reply was seen
While the chat panel is open and the browser tab is visible, the widget checks in every fifteen seconds. That signal is a plain "the customer was here at this time" — nothing is torn down when it stops.
A reply counts as seen if any check-in arrives after that reply was sent. That's it. The comparison is per-reply and per-conversation.
What follows from this:
- A background tab is not a departure. A minimised window, another tab, a customer scrolling the page with the panel closed — none of it ends the chat or moves the channel. The widget prefixes the browser tab title with an unread count and plays a short sound when a reply arrives (the customer can mute it in the widget's settings), so a customer who is elsewhere on the page gets pulled back.
- Navigating between pages is not a departure either. The customer carries the conversation with them across your site.
- Each reply has its own ten-minute clock. An agent who keeps typing does not reset the timer on their earlier messages, and does not delay the email.
The unseen-reply email
When a reply has gone ten minutes with no check-in after it, the customer is emailed. It comes from the inbox already used on the conversation, or your business's primary inbox if there is none:
- The email contains the replies they missed, the actual words and attachments, in the order they were sent, with a short line in the customer's language saying these are replies from the chat. Several replies in the same window are combined into one email. It is signed like any other email from the agent who wrote the last reply, or with your bot footer when that was the AI agent.
- The conversation stays exactly as it was. The widget messages are untouched and the reply channel stays on chat. Your team and the AI agent keep replying in the widget, where the customer may still come back.
- A timeline event records it ("Customer didn't see a reply in the chat widget. Emailed them a copy so they don't miss it."), so agents can always tell what the customer received.
- At most one email per conversation per hour. Replies sent during that hour that also go unseen are included in the next email.
This covers both your team's replies and the AI agent's, for example an answer the AI agent sends after a human decision. The AI agent's greeting and other system messages never trigger an email.
Two things must be in place for the email to go out, and if either is missing the reply stays in the widget:
- Octocom knows the customer's email address. An anonymous visitor who never identified themselves cannot be emailed.
- Your business has an email integration connected. Without a mailbox to send from, there is nothing to send with. A helpdesk inbox (Zendesk, Freshdesk, Gorgias, Help Scout, Re:amaze, Commslayer) can only reply to an existing ticket, so it is used only once the conversation already has an email thread.
Playground and test conversations are never emailed, and neither are conversations already replying on another channel. Businesses that hand conversations to an external ticket system (Zendesk, LiveChat, email tickets and similar) are skipped too: their customer conversations run in that system.
When the customer replies by email
The email goes out on the conversation's email thread, so a reply from the customer's inbox lands on the same conversation. That reply is what moves the conversation to email: the reply channel switches to email and a timeline event records it ("Customer replied by email, setting reply channel to email"). From then on, replies go to their inbox.
Switching back to chat
Coming back is just as automatic — and the customer doesn't even need to type. Reopening the widget is enough. Within seconds of the customer returning, Octocom re-checks live chat availability, and if someone can answer, the reply channel flips back to chat and a timeline event records it ("Customer came back to chat widget, setting reply channel to web"). Sending a message triggers the same re-check.
Because nothing was torn down when the conversation moved to email, this is a clean flip back: the conversation was never closed, requeued or reassigned.
The reply channel will not switch back when:
- Live chat isn't available at that moment — nobody available, or outside working hours. The conversation stays on email, which remains the only channel guaranteed to reach the customer.
- The customer ended the chat themselves — closed the conversation, cleared their history, or started a new chat. Ended means ended; only their new conversation is live. Each of these writes its own timeline event and moves the old conversation to email.
- The chat has been quiet for over an hour and your live chat runs through an external provider (LiveChat, Zendesk). A browser tab restored the next morning would otherwise re-queue a customer who gave up hours ago. They can still resume by sending a message.
What your agents see
Agents never choose the reply channel manually: the reply box in the help desk always targets the conversation's current reply channel, and it updates in real time. An agent watching a conversation will see the composer flip to email when the customer replies by email, and back to chat when the customer returns to the widget.
Combined with the timeline events, this answers the most common support questions about live chat: "did the customer get my reply?" and "why is this conversation on email now?" Open the conversation timeline: you will find the reply that went unseen, the email that followed it, and any change of reply channel.
FAQ
A customer wrote in via chat and got an email. Is that a bug? No. It means a reply sat in the widget for ten minutes with no sign of the customer, so they were emailed a copy. They have it in both places. The conversation timeline records exactly when.
Can a customer be emailed while they are sitting in the widget? Only if they went ten minutes without the widget checking in — which means the panel was closed or the tab was hidden that whole time. Simply having the chat open, in a visible tab, prevents it.
My agent replied and nothing was emailed, even though the customer had clearly left. Check that Octocom has an email address for that customer and that your business has an email integration connected. Without both, there is nowhere to send the email and the reply stays in the widget. If the conversation was emailed in the last hour, the new reply waits for the next email.
Why didn't the reply channel switch to email when the customer was emailed? Because the customer may still come back to the widget, and an email about the chat doesn't mean they left it for good. The conversation moves to email when the customer actually replies by email.
Why doesn't the reply channel switch to chat when my agent replies? Because the agent replying tells us nothing about whether the customer can see the widget. The customer returning does, and it flips the channel back within seconds.
Handoffs always go to email even when my team is online. This is nearly always agent availability: agents marked unavailable, outside working hours, or (with activity-based availability) without the dashboard open. An agent whose dashboard tab has been hidden behind other windows for about 5 minutes counts as away. Ask Copilot to list agent availability to see who counts as online and why.
Can we turn the unseen-reply email off so everything stays in chat? No. A chat reply to an absent customer is never delivered: not delayed, never delivered. The email exists so every customer gets their answer, wherever they are.
Does this apply to social and WhatsApp conversations? No — this page is about web chat. Conversations on social channels and WhatsApp are asynchronous and simply stay on their own channel.