> ## 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.

# Share a WhatsApp number with HubSpot or another app

> How to run Flowella next to HubSpot, a helpdesk or Meta Business Agent on one WhatsApp number: the routing we recommend and what each choice changes.

Since September 2026, one WhatsApp number can be connected to several apps at once, for example Flowella for forms and campaigns, and HubSpot's inbox or a helpdesk for support. Each app has its own Messaging account, templates and billing. What decides whether the combination works is [Conversation Routing](https://knowledge.flowella.io/whatsapp/routing/conversation-routing.md): which app receives each customer message, and therefore which features keep working.

> [!NOTE]
>
> **In Flowella.** Partly supported. Flowella sends templates on a shared number with no restrictions, and handles every conversation routed to it. It doesn't read standby copies or handover events, and can't pass conversations to another app. [Contact Flowella support](https://flowella.io/support) before you connect another app to a number Flowella uses.

## Before routing is set up

As soon as a second app is connected, both apps receive every customer message until a routing configuration exists. If both reply automatically, customers get two answers. Set up routing in Meta Business Suite straight after connecting the second app, and check any configuration Meta created for you.

## What each Flowella feature needs

Flowella can only act on messages it receives. Under routing, that means messages on conversations it owns.

| Flowella feature | Works when Flowella receives |
| - | - |
| **Inbox** and free-form replies | Customer messages on conversations Flowella owns |
| HubSpot **Text Reply** trigger | Replies Flowella receives |
| Keyword opt-outs such as `STOP` | The opt-out message itself. If another app receives it, Flowella doesn't record the opt-out. |
| Answers to Flow designer Flows | The Flow reply message, which is routed like any reply |
| Answers to HubSpot-form Flows | Not affected. Flowella's endpoint submits them while the customer completes the Flow. |
| Click to WhatsApp attribution and lead events | The first message from the ad |
| Entry points (tracked links and QR codes) | The first message from the link |
| Bulk send, template sends and HubSpot **Send WhatsApp Template** | Not affected. Any app can send templates. |

## The set-up we recommend

| Entry point | Recommended primary | Why |
| - | - | - |
| **Marketing Message Response** | **Route to Sender** | Replies, button taps and Flow answers to Flowella's templates come back to Flowella, and the other app's come back to it |
| **Utility Response** | **Route to Sender** | The same, for utility templates such as reminders and confirmations |
| **Click to WhatsApp** | Flowella, if you answer Click to WhatsApp ads with Flowella | Keeps attribution, lead events and the HubSpot workflows that answer ad conversations working |
| **Service** | The app your team answers new conversations in | New conversations that aren't replies to a template land there |
| **Call** | The app that handles WhatsApp calls | Flowella doesn't handle calls |
| **Escalation partner** | The app your team uses to take over conversations | Lets your team step in on any conversation |
| **Standby** | Not Flowella | Flowella doesn't read standby copies yet |

> [!WARNING]
>
> If the other app is the fixed primary for **Marketing Message Response** or **Utility Response**, replies to Flowella's templates go to it instead. Flowella then misses opt-outs, Text Reply triggers and answers to Flow designer Flows sent in those templates.

## Typical problems

| Symptom | Likely cause | What to do |
| - | - | - |
| Inbox replies fail with **131070** | Another app owns the conversation | Answer from that app, ask it to release or pass the conversation, or wait until 24 hours after the customer's last message |
| Replies to a Flowella template don't appear in Flowella | A fixed primary other than Flowella for that template's entry point | Switch the entry point to **Route to Sender** |
| New conversations don't reach the Flowella Inbox | Flowella isn't the Service primary | Expected. Make Flowella the Service primary if your team works in the Flowella Inbox. |
| Customers got two replies | Routing isn't configured yet, so both apps receive everything | Configure routing in Meta Business Suite |
| A STOP doesn't appear on Flowella's **Opt-outs** page | The customer replied on a conversation another app owns | Add the opt-out in Flowella by hand. See [Opt-outs](https://knowledge.flowella.io/app/opt-outs.md). |
| Routing changed after you removed an app | Meta dropped the removed app from every role without choosing a replacement | Review Conversation Routing and fill the empty entry points |

## Billing on a shared number

Each app sends from its own Messaging account, with its own payment method and Meta invoice. A message Flowella sends is billed to Flowella's Messaging account. See [Several providers on one number](https://knowledge.flowella.io/whatsapp/accounts/whatsapp-business-account.md#several-providers-on-one-number).

## Related

> [card] [Conversation Routing](https://knowledge.flowella.io/whatsapp/routing/conversation-routing.md)
>
> Entry points, owners and the 24-hour idle rule.

> [card] [Meta Business Agent](https://knowledge.flowella.io/whatsapp/routing/meta-business-agent.md)
>
> When Meta's AI agent shares the number.

> [card] [WhatsApp error codes](https://knowledge.flowella.io/whatsapp/errors/error-codes.md#sending-messages)
>
> 131070 and other sending errors.

> [card] [Co-existence](https://knowledge.flowella.io/whatsapp/accounts/co-existence.md)
>
> Using the WhatsApp Business app on the same number.

Checked against Meta's documentation on 18 November 2026: [Get started with Conversation Routing](https://developers.facebook.com/documentation/business-messaging/whatsapp/conversation-routing/get-started), [Entry points and routing](https://developers.facebook.com/documentation/business-messaging/whatsapp/conversation-routing/entry-points-and-routing) and [Prepare for Conversation Routing](https://developers.facebook.com/documentation/business-messaging/whatsapp/conversation-routing/prepare-for-conversation-routing).


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