> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.flowella.io/llms.txt
> Use this file to discover all available pages before exploring further.

# WhatsApp Conversation Routing on a shared number

> How Conversation Routing decides which app answers on a shared WhatsApp number: entry points, thread owners, the 24-hour idle rule and who may reply.

When more than one app answers on the same WhatsApp number, for example Flowella and a helpdesk, or Flowella and HubSpot, Meta's **Conversation Routing** decides which app receives each customer message. Every conversation gets one **owner**. Only the owner can send free-form replies, while any app can still send templates. The business sets up routing in Meta Business Suite. Apps can't change it.

> [!NOTE]
>
> **In Flowella.** Partly supported. Flowella works as one of the apps on a routed number: it receives the conversations routed to it, replies while it owns them, and sends templates at any time. It doesn't yet read Meta's ownership events, standby copies or handovers, so it can't hand a conversation to another app or see conversations it doesn't own. A Flowella reply on a conversation another app owns fails with **131070**. For a practical set-up, see [Sharing a number with another app](https://knowledge.flowella.io/whatsapp/routing/sharing-a-number.md).

## When routing applies

Routing isn't a switch. It takes effect on a WhatsApp account when both are true:

* More than one app (Meta calls them responders) can answer messages on the account. A third-party app, Meta's own app or [Meta Business Agent](https://knowledge.flowella.io/whatsapp/routing/meta-business-agent.md) all count.
* The business has a routing configuration in Meta Business Suite.

Until a configuration exists, **every connected app receives every customer message**, and any of them can reply. Meta creates a starting configuration automatically in some cases, such as when a second app is connected through Meta's sign-up popup, but never overwrites one that already exists. If fewer than two apps remain, Meta deletes the configuration and every remaining app receives everything again.

## The terms

| Term | Meaning |
| - | - |
| **Thread** | The conversation between your business and one customer on one phone number |
| **Owner** | The app that currently holds a thread. Only the owner can send free-form (service) messages in it. |
| **Primary** | The app the business chose to receive new conversations for an entry point. It becomes the owner when a new thread starts. |
| **Entry point** | How the customer's message arrived, which decides the primary. See the table below. |
| **Idle** | A thread with no owner. The next customer message is routed by entry point. |
| **Escalation partner** | One app per account that can take any thread from its owner, usually where your human team works |
| **Standby** | Copies of messages on threads an app doesn't own, for context only. Off by default. A standby app must not reply. |
| **Thread control** | The API actions an app uses to hand a thread on (`pass`), give it up (`release`) or, as the escalation partner, claim it (`take`) |

Standby, the escalation partner and thread control need the business to accept the **Meta Business Agents and Platform Terms of Service**. Without them, only basic routing by entry point works.

## The five entry points

| Entry point | Label in Meta Business Suite | What sends a message here |
| - | - | - |
| **Service** | Customer sends a message | A message with no marketing or utility template sent to the customer in the last 24 hours, or a reply to a service message. The default. |
| **Click to WhatsApp** | Customer replies to click-to-WhatsApp ad | A customer who arrives from a Click to WhatsApp ad |
| **Utility Response** | Customer replies to a utility message | A reply to a utility template, or any message when your last message in the past 24 hours was a utility template |
| **Marketing Message Response** | Customer replies to a marketing message | A reply to a marketing template, or any message when your last message in the past 24 hours was a marketing template |
| **Call** | Calls with customers | A call, or a reply to a call permission request. Routes call events only, never conversation ownership. |

For the Utility Response and Marketing Message Response entry points, the business can choose **Route to Sender** instead of a fixed app. Replies then go to whichever app sent the template.

## How Meta routes a customer message

**1. Work out the entry point**

A Click to WhatsApp ad wins first, then a call. Next, a direct reply (a quoted reply or a button, list or Flow reply) takes the entry point of the message it replies to. Otherwise Meta looks at your last template in the past 24 hours. With none, it's Service.

**2. Check for a change of intent**

A Click to WhatsApp ad click, or a button, list or Flow reply to a **marketing or utility template**, resets the thread. The message is routed by entry point even if another app owns the thread.

**3. Deliver to the owner, or to the primary**

If the thread has an owner, the message goes to the owner whatever its entry point. If it's idle, it goes to the primary for its entry point, or to the template's sender with Route to Sender, and that app becomes the owner straight away.

**4. Copy to standby apps**

Apps the business gave standby visibility get a copy. They must not reply.

## How long an app owns a thread

| Event | Effect on the thread |
| - | - |
| 24 hours with no message from the customer | Becomes idle. The next message is routed by entry point. |
| The owner releases it | Becomes idle |
| The owner passes it, or the escalation partner takes it | A different app becomes the owner |
| Click to WhatsApp ad click, or a button, list or Flow reply to a marketing or utility template | Reset and routed again straight away |
| A quoted reply or an ordinary message | No change. Goes to the current owner. |
| A button reply to an authentication template or a service message | No change |
| Any app sends a template | No change |
| A call | No change |

The 24-hour idle rule is separate from the [customer service window](https://knowledge.flowella.io/whatsapp/messaging/customer-service-window.md). Both are 24 hours, but they measure different things.

## Who can send what

| Message | Who can send it |
| - | - |
| Marketing, utility and authentication templates | Any app on the account, at any time. Sending one doesn't change the owner. |
| Free-form (service) messages | Only the thread's owner. Other apps' sends fail, even on an idle thread. |
| Service message from the escalation partner | Allowed, and it takes the thread from the current owner |

> [!NOTE]
>
> **In Flowella.** Templates always send, so bulk sends and HubSpot **Send WhatsApp Template** steps aren't affected by routing. Free-form replies from the Inbox and the **Send WhatsApp Message** and **Send WhatsApp Reply** actions need Flowella to own the conversation. When another app owns it, they fail with **131070**. See [WhatsApp error codes](https://knowledge.flowella.io/whatsapp/errors/error-codes.md#sending-messages).

## Configuration levels

The business can set one configuration for the whole account and override it for particular phone numbers. Each number can therefore route the same entry point to a different app.

## When an app is removed

If two or more apps remain, the removed app is dropped from every role, but Meta doesn't pick a replacement. Review the routing straight away, or an entry point can be left with no primary. If fewer than two apps remain, routing is switched off.

## Set up or change routing

**1. Open Conversation Routing**

In Meta Business Suite, open **Conversation Routing** for your WhatsApp account. Choose the account default or a specific phone number.

**2. Choose a primary for each entry point**

Pick an app for each of the five entry points, or **Route to Sender** for the two template response entry points.

**3. Choose the escalation partner and standby**

Pick the app your team uses to take over conversations. Grant standby only to apps that read it.

**4. Save and test**

Send a test template from each app, reply to it from a phone, and check the reply arrives where you expect.

## Related

> [card] [Sharing a number with another app](https://knowledge.flowella.io/whatsapp/routing/sharing-a-number.md)
>
> A recommended set-up for Flowella and HubSpot.

> [card] [Meta Business Agent](https://knowledge.flowella.io/whatsapp/routing/meta-business-agent.md)
>
> What changes when Meta's AI agent answers.

> [card] [Several providers on one number](https://knowledge.flowella.io/whatsapp/accounts/whatsapp-business-account.md#several-providers-on-one-number)
>
> How Meta's account model allows it.

> [card] [Customer service window](https://knowledge.flowella.io/whatsapp/messaging/customer-service-window.md)
>
> When you can send free-form messages.

Checked against Meta's documentation on 18 November 2026: [Conversation Routing](https://developers.facebook.com/documentation/business-messaging/whatsapp/conversation-routing/overview), [Entry points and routing](https://developers.facebook.com/documentation/business-messaging/whatsapp/conversation-routing/entry-points-and-routing), [Thread lifecycle](https://developers.facebook.com/documentation/business-messaging/whatsapp/conversation-routing/thread-lifecycle), [Get started](https://developers.facebook.com/documentation/business-messaging/whatsapp/conversation-routing/get-started) and [Troubleshooting](https://developers.facebook.com/documentation/business-messaging/whatsapp/conversation-routing/troubleshooting).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.