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

# This channel is already connected

> If Cura says a channel is already connected — to another workspace, to your own workspace, or to another tool — here's what each message means and how to move the channel to Cura safely.

When you try to add a channel, Cura checks whether that exact page, number, or bot is already in use — so two inboxes never fight over the same channel. If you see an "already connected" message, it's one of three situations below. Each has a safe fix.

This article is also worth reading if you're **moving to Cura from another chatbot or provider** — it explains how to reclaim a channel that's tied up elsewhere.

***

## "Already connected to another Cura organization"

**What you see:** A modal telling you the page / number / bot is *already connected to another Cura organization*, with an option to **take it over** (reclaim it).

**Why it happens:** This exact channel is already an active inbox in a **different** Cura workspace. Cura won't let two workspaces receive the same channel's messages, so it offers to move the channel to yours instead.

<Warning>
  Only reclaim a channel you are certain belongs to you. Taking over **archives the inbox in the other workspace** and moves the channel here — the other workspace stops receiving those messages. If that other workspace isn't yours (for example, an agency or a previous owner still uses it), **do not reclaim it**. Stop and contact **[support@cura.so](mailto:support@cura.so)**.
</Warning>

<Steps>
  <Step title="Confirm the other workspace is really yours">
    Think about where else this page, number, or bot might already be connected — a test workspace, an old account, or a partner's Cura. Only continue if you're sure it's yours to move.
  </Step>

  <Step title="Reclaim the channel (admin only)">
    Click the **take-over / reclaim** option in the modal. This must be done by an **organization admin** — if you don't have the option, ask an admin on your team to do it.
  </Step>

  <Step title="Confirm the move">
    Cura archives the other workspace's copy and connects the channel to your workspace.

    <Check>The channel now appears under your **Integrations → Channels** and starts receiving messages here.</Check>
  </Step>
</Steps>

***

## "Already connected in your organisation"

**What you see:** A message that this WhatsApp / Messenger / LINE / etc. is *already connected in your organisation*, and Cura refuses to add it again.

**Why it happens:** You already have this exact channel connected in **your own** workspace. There's nothing to add — it's already here. This usually happens when someone tries **Add Channel** to refresh a channel that just needs reconnecting.

<Steps>
  <Step title="Open the existing inbox">
    Go to **Integrations → Channels** and open the channel that's already listed. You don't need to add it a second time.
  </Step>

  <Step title="Use Reconnect, not Add Channel">
    If the channel needs refreshing (for example it shows *needs reconnect*), use the **Reconnect** button on the existing inbox — not **Add Channel**. See [A channel shows as disconnected](/faqs/channel-disconnected).

    <Check>Reconnecting refreshes the credentials on the inbox you already have, without creating a duplicate.</Check>
  </Step>
</Steps>

***

## WhatsApp: the number is live on another tool

**What you see:** WhatsApp appears to connect in Cura, but the inbox **never receives customer messages** — even right after connecting.

**Why it happens:** A WhatsApp number can effectively deliver its incoming messages to **only one tool or provider at a time**. If your number is still live on another chatbot, BSP, or the WhatsApp Business app, that other tool keeps receiving the inbound messages — so Cura connects but stays silent. This is a WhatsApp (Meta) rule, not a Cura limit.

<Steps>
  <Step title="Remove the number from the other tool first">
    Deactivate or remove the WhatsApp number from any other messaging tool, BSP, or app so it's only on Cura.
  </Step>

  <Step title="Check your Business Manager access">
    Make sure the Facebook account you connect with has **WhatsApp business management** rights on that number, and that the WhatsApp Business Account lives in a Business Manager you control.
  </Step>

  <Step title="Reconnect in Cura">
    Reconnect the WhatsApp channel. With the number free of other tools, inbound messages will route to Cura.

    <Check>Send a test message to your WhatsApp number from another phone — it should now appear in the Cura Inbox.</Check>
  </Step>
</Steps>

<Note>
  If WhatsApp still receives nothing after removing it from every other tool, contact **[support@cura.so](mailto:support@cura.so)** — the number's subscription may need to be re-registered on our side.
</Note>

***

### Moving to Cura from another chatbot?

If you're switching from another provider, the pattern is the same across channels: the channel is "taken" until you free it from the old tool. For **Meta channels** you may also need to remove Cura's predecessor from your Facebook Business Integrations before reconnecting — see the full-reset steps in [A channel shows as disconnected](/faqs/channel-disconnected).

***

### Related articles

* [I can't connect a channel](/faqs/cant-connect-a-channel)
* [A channel shows as disconnected](/faqs/channel-disconnected)
* [Connect WhatsApp Business](/setting-up-cura/connect-whatsapp-business)
* [Archiving a channel](/setting-up-cura/archiving-a-channel)