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

# What Is a BSP — and Can You Move to ChatSyncs From One?

> Whether an existing WABA on another BSP (Twilio, Interakt, Wati, AiSensy, Gallabox) can move to ChatSyncs without losing your number, templates, or quality rating.

A **BSP (Business Solution Provider)** is a Meta-authorized partner — Twilio, Interakt, Wati,
AiSensy, Gallabox, and others — that resells access to the WhatsApp Business API. See
[What Is a WABA (WhatsApp Business Account)?](/meta-api/concepts/whatsapp-api-glossary) for the full definition.

The question that actually matters if a business already has one: **can they switch to
ChatSyncs without starting over?**

## The short answer: yes

* The phone number and WABA belong to the business's **Meta Business Portfolio** — not to the
  BSP.
* A BSP is just the middleman that was given permission to use it.
* Moving to ChatSyncs means swapping who has that permission — not creating a new WABA from
  scratch.

## What moves over automatically

Because these live in Meta, not in the old BSP:

* The phone number itself
* The WABA and its **approved message templates**
* The number's **quality rating and messaging tier**
* Meta's own conversation history record

## What does NOT move over automatically

Anything the old BSP stored on its own side has to be rebuilt in ChatSyncs:

* Its bot flows, automations, and keyword replies
* Its own contact tags, segments, or custom fields
* Its own local chat log / mirror (separate from Meta's own record)
* Any custom integrations built specifically on that BSP's platform

## How to actually switch

<Steps>
  <Step title="Remove the old BSP's access in Meta">
    A WABA can only have one partner with Full access at a time. Follow [How to Disconnect
    Another Partner From Your WhatsApp Number](/learn/chatsyncs-setup-and-configuration/disconnect-another-partner-from-your-whatsapp-number-in-chatsyncs) — including the extra
    phone-side step if the old setup used Coexistence.
  </Step>

  <Step title="Connect the number to ChatSyncs">
    Use [How to Connect Your Number to ChatSyncs](/learn/chatsyncs-setup-and-configuration/connect-your-number-to-chatsyncs) if you don't have your own Meta app
    credentials handy, or [How to Connect Your WhatsApp Account Manually (Alternative Method)](/learn/chatsyncs-setup-and-configuration/connect-your-whatsapp-account-manually-alternative-method-in-chatsyncs) if you do.
  </Step>

  <Step title="Re-sync templates and rebuild automations">
    Pull existing approved templates into ChatSyncs — see [Sync Templates from WhatsApp
    Manager](/learn/chatsyncs-message-templates/create-templates-in-whatsapp-manager-and-sync-to-chatsyncs) — then rebuild any bot flows or
    automations that lived only in the old BSP.
  </Step>
</Steps>

## Frequently asked

<AccordionGroup>
  <Accordion title="Will I lose my number switching from another BSP to ChatSyncs?">
    No — the number stays yours in Meta regardless of which BSP or platform currently has API
    access to it.
  </Accordion>

  <Accordion title="Will my approved templates carry over?">
    Yes, templates live on the WABA inside Meta, not inside the old BSP. See [Sync Templates
    from WhatsApp Manager](/learn/chatsyncs-message-templates/create-templates-in-whatsapp-manager-and-sync-to-chatsyncs) to pull them into
    ChatSyncs.
  </Accordion>

  <Accordion title="Will my quality rating reset when I switch?">
    No — quality rating is tracked by Meta against the phone number itself, not against whichever
    platform is currently connected to it.
  </Accordion>

  <Accordion title="Do I need to tell my old BSP I'm leaving?">
    Not required for the technical switch — removing their partner access in Meta is enough.
    Cancel any separate subscription you had directly with them on your own.
  </Accordion>

  <Accordion title="Can I run ChatSyncs and my old BSP at the same time?">
    No — only one partner can hold Full access to a given WABA at a time.
  </Accordion>
</AccordionGroup>

## Gotchas & common mistakes

<Warning>
  * **Coexistence connections need an extra step.** If the old BSP connection used Coexistence
    (the WhatsApp Business App active on a phone), disconnecting in Meta alone isn't enough — the
    app itself also remembers the old partner. See the second half of [How to Disconnect Another
    Partner](/learn/chatsyncs-setup-and-configuration/disconnect-another-partner-from-your-whatsapp-number-in-chatsyncs#if-the-number-uses-coexistence-also-disconnect-from-the-phone).
  * **Don't wait to remove old access before connecting to ChatSyncs** — the new connection will
    fail with an "already linked" error until the old partner's access is removed first.
</Warning>
