> For the complete documentation index, see [llms.txt](https://docs.quickreply.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quickreply.ai/product-modules/journeys/parallel-journeys.md).

# Parallel Journeys

Parallel Journeys lets you process multiple events from the same customer without interrupting an ongoing Journey execution. For example, if a customer places another order while an order-related Journey is running, the new order can start its own execution while the earlier one continues.

By default, Allow Parallel Journey is disabled for new and existing Journeys. When disabled, a new qualifying event from the same customer replaces their existing active execution. When enabled, each qualifying event can start a separate execution, and each execution tracks its progress independently.

### Why Use Parallel Journeys?

Consider an online store that uses QuickReply to send WhatsApp messages after customers place orders.

A customer places an order for a dress, triggering a Journey that sends an order confirmation and schedules follow-up messages. Before that Journey finishes, the customer places another order for shoes.

* When Parallel Journeys is disabled: The new order replaces the earlier active execution. The remaining follow-up steps for the dress order may not be completed.
* When Parallel Journeys is enabled: The dress order continues through its existing execution, while the shoe order starts a separate execution.

This is useful for businesses where customers may place multiple orders, create multiple carts, browse different products, or trigger the same event more than once.

**Note:** Parallel Journeys controls how multiple executions of a Journey run for the same customer. It does not configure the trigger or change the actions defined in your workflow.

### Enable Parallel Journeys

You can enable Parallel Journeys while creating a new Journey or editing an existing one.

1. Navigate to Journeys in QuickReply.

![](https://1325107618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FePPO97Ju334NhhCzTEZP%2Fuploads%2FwwbGmbJ4ABqFkMujpD7L%2FPasted%20image%202026-11-16%2011.52.23.png?alt=media\&token=a8b9d22a-94fd-4c4c-a2a6-205220393227)

2. Open the Journey you want to configure.

![](https://1325107618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FePPO97Ju334NhhCzTEZP%2Fuploads%2FEZBcHIoE9rXO2vSzIweV%2FPasted%20image%202026-11-16%2011.52.27.png?alt=media\&token=0e36d79d-b860-41b2-ad5c-bf82e777f74e)

3. Click Edit.

![](https://1325107618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FePPO97Ju334NhhCzTEZP%2Fuploads%2FWLzuhqKXtBMB2U1DNUCw%2FPasted%20image%202026-11-16%2011.52.30.png?alt=media\&token=fd0735fe-fa4d-4e8b-9db8-17b375660cd8)

4. In Trigger Settings, locate the Re-entry Behavior section.

![](https://1325107618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FePPO97Ju334NhhCzTEZP%2Fuploads%2FCbjNVZhx0IkcUWy34v56%2FPasted%20image%202026-11-16%2011.52.33.png?alt=media\&token=3ddeaf2a-95ca-4ab8-ac5a-cf020fe8f412)

5. Enable the Allow Parallel Journey toggle.

![](https://1325107618-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FePPO97Ju334NhhCzTEZP%2Fuploads%2Flhl8dikLdlj8RcaQfEIN%2FPasted%20image%202026-11-16%2011.52.35.png?alt=media\&token=f437d5ca-1c70-4d0f-9df8-cafa71568d3a)

It is disabled by default. Once enabled, the same customer can run multiple executions of the Journey simultaneously, with each execution tracking its progress independently.

**Conversion tracking:** The information displayed under the toggle states that a conversion is attributed only when a customer reaches the Journey goal.

Before enabling the setting, review your workflow to ensure that processing multiple events independently is appropriate for your use case.

### How Parallel Journeys Works

To understand the feature, it helps to distinguish between a Journey, an event, and a Journey instance.

* **Journey:** The workflow configured in QuickReply, including its trigger, actions, wait steps, and conditions.
* **Event:** Something that happens, such as a customer placing an order.
* **Journey instance:** One execution of a Journey associated with a qualifying event.

#### Example: A Customer Places Multiple Orders

Suppose a customer places two orders while Parallel Journeys is enabled.

1. The customer places an order for a dress. This starts Journey instance A.
2. Before instance A finishes, the customer places another order for shoes.
3. The second order starts Journey instance B.
4. Both instances continue independently, following the configured workflow steps.

Instance A continues processing the dress order, while instance B processes the shoe order. Each instance follows the Journey workflow using the relevant event data available to it.

#### Parallel Journeys: Disabled vs. Enabled

| **Behaviour**                                              | **Disabled**                                                     | **Enabled**                                                                             |
| ---------------------------------------------------------- | ---------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| Default state                                              | Disabled                                                         | Must be enabled                                                                         |
| A new qualifying event occurs while an instance is running | The older active instance exits, and the new instance takes over | A separate instance starts for the new event                                            |
| Multiple instances run independently                       | No                                                               | Yes                                                                                     |
| Message tracking                                           | Existing attribution logic applies                               | Messages are counted per Journey instance                                               |
| Goal attribution                                           | Existing attribution logic applies                               | Goals are attributed to qualifying events according to the applicable attribution logic |

### Understand Unique Users, Events, and Journey Instances

When Parallel Journeys is enabled, one customer can trigger multiple events, each of which can start a separate Journey instance. These are different metrics:

* Unique users: The number of distinct customers involved.
* Events triggered: The number of qualifying events that trigger the Journey.
* Journey instances: The number of individual Journey executions created.
* Messages sent: The number of messages sent across the Journey instances.
* Goals achieved: The number of goal achievements recorded according to the configured goal and attribution logic.

#### Example

Suppose one customer places three orders, and all three events qualify for the Journey.

| **Metric**        | **Example count** |
| ----------------- | ----------------- |
| Unique users      | 1                 |
| Events triggered  | 3                 |
| Journey instances | 3                 |

The number of messages sent and goals achieved depends on the workflow execution and the configured goal. For example, if each instance sends one WhatsApp message and each order achieves the configured goal, the result would be three messages and three goal achievements.

#### What Is Goal Attribution?

Goal attribution tracks whether a Journey leads to a desired outcome, such as a customer completing an order.

For example, when a customer places three orders and each order triggers a separate Journey instance, goal attribution helps track the conversions associated with those orders individually, provided each order meets the configured Journey goal.

This helps businesses measure Journey performance by understanding the conversions associated with individual events, rather than looking only at the number of customers who entered the Journey.

**Note:** A conversion is attributed only when a customer reaches the configured Journey goal.

### When Does Parallel Journeys Take Effect?

Parallel Journeys applies to events triggered after the setting is enabled. Existing instances that started before activation continue according to their original logic.

#### Example: Enabling Parallel Journeys While a Journey Is Running

1. On 16 May, a customer places Order A while Parallel Journeys is disabled. Journey instance A starts under the existing logic.
2. On 17 May, Parallel Journeys is enabled.
3. Later on 17 May, the customer places Order B. Journey instance B starts under Parallel Journeys behaviour.
4. Instance A continues according to its original logic, while instance B runs independently.

**Note:** Existing Journey executions continue as they were before Parallel Journeys was enabled. The new setting applies to events triggered after it is enabled.

### Important Considerations

* Disabled by default: Parallel Journeys is disabled for new and existing Journeys until enabled.
* Independent execution: Each qualifying event can start a separate Journey instance when the setting is enabled.
* Potential increase in activity: Multiple instances may increase Journey executions and messages sent.
* Separate metrics: Unique users are counted at the customer level, while events and Journey instances are counted separately.
* Conversion tracking: A conversion is attributed only when the customer reaches the Journey goal.
* Existing instances: Enabling the setting does not automatically restart instances that began before activation.

### FAQs

<details>

<summary>What happens when the same customer triggers a Journey multiple times?</summary>

When Parallel Journeys is disabled, a new qualifying event replaces the older active instance. When enabled, each qualifying event can start a separate instance that runs independently.

</details>

<details>

<summary>What happens to existing Journey instances when Parallel Journeys is enabled?</summary>

Existing instances that started before activation continue according to their original logic. Enabling Parallel Journeys does not automatically restart them.

</details>

<details>

<summary>Will enabling Parallel Journeys increase the number of messages sent?</summary>

It may. Multiple qualifying events can start separate Journey instances, potentially increasing the number of messages sent, depending on the workflow.

</details>

<details>

<summary>What is the difference between unique users and events triggered?</summary>

Unique users count distinct customers, while events triggered count qualifying events. For example, if one customer triggers a Journey three times, there is one unique user and three events.

</details>

<details>

<summary>When is a conversion attributed?</summary>

A conversion is attributed only when a customer reaches the Journey goal. With Parallel Journeys enabled, goal attribution follows the applicable event-level attribution logic.

</details>

<br>
