---
title: "Live Chat Round Robin - Reroute if No Response"
source_url: https://help.chilipiper.com/hc/en-us/articles/40008316418707-Live-Chat-Round-Robin-Reroute-if-No-Response
article_id: 40008316418707
updated_at: 2026-07-24T18:55:57Z
content_hash: e5b0f418
---

## Who can use this feature?

Available on All Products or Experiences

Available to Admins or Workspace Managers

[Billing Center](https://fire.chilipiper.com/fire/admin/billing/overview) [Get a Demo](https://www.chilipiper.com/request-demo?utm_source=zendesk&utm_medium=help-center&utm_campaign=chili-hub)

 

The reroute if no response toggle allows you to continue routing through your selected team instead of selecting ONE user to route to in a round-robin.

#### Table of Contents

- [Why use the Reroute if no response option](#h_01JQYEY0TXMTBPE70GDBM8DWMV)

- [How to use Reroute if no response toggle](#h_01JQYEY0TXMTBPE70GDBM8DWMV)

## Why use the Reroute if no response option

When using the Round Robin feature specifically, we treat assignments like we would for scheduling. If we assign the conversation through Distribution:

- We select the next user and assign it to them

- If that user is _**Online**_ → Wait for them to join the conversation → If they don’t join → proceed to not available options

- If that user is _**Offline**_ → proceed to not available options

If that selected user is Offline or does not join the conversation, the probability of connecting the visitor to live chat is much lower. 

Thus, we have created a new ‘Waterfall’ option in Live Chat’s **Route to Node.**

****

 

## How to use Reroute if the Reroute if no response toggle

The reroute option is enabled by default in the **Route for Live Chat node**under Team Member via Round Robin. You can disable it to attempt routing to a single assignee. 

![](https://help.chilipiper.com/hc/article_attachments/40008344473235)

 

Only consider available Reps in the Round Robin

- When a rep is marked ‘offline,’ do not include them in the Round Robin. If all reps are offline, then this would justify executing the fallback branch directly.

When enabled, the guest is routed through the team until someone responds the total wait time has passed. 

We allow the Admin to configure the wait time per rep and the total number of reps to route to. In the **Wait For Rep Node,**the Admin will configure how long to try each rep for (default = 30s) and the total number of reps to try. We will calculate the total ‘wait’ time configured based on this. 

In the example below, we will try 3 reps, waiting 30 seconds for each rep, for a total wait time of 150 seconds. If no one joins after the waterfall round-robin, we proceed to the fallback branch.

![](https://help.chilipiper.com/hc/article_attachments/40008316413843)

_Note that the Wait for Rep Node is required to perform the reroute. If this node is removed, the reroute will be automatically disabled._