Skip to main content
There are valid reasons to disconnect your WABA — switching to a different workspace, moving providers, ending a pilot, or resetting a stuck connection. This page explains exactly what disconnecting does, what it doesn’t do, and how to come back.
Disconnecting stops all message sending and receiving on that number via Xobito. Running campaigns fail. Active chats can’t be replied to. Read this whole page before you click Disconnect.

What disconnecting actually does

When you disconnect a WABA in Xobito, three things happen:

1. Meta token is revoked

Xobito can no longer call Meta’s API for this WABA. Sends stop immediately.

2. Webhook is unsubscribed

Meta stops forwarding events to Xobito for this WABA. Inbound messages stop arriving in your inbox.

3. Account marked as disconnected

The Setup → Account page shows status Disconnected for this WABA.

What disconnecting does NOT do

It does not delete your WABA — your WABA continues to exist in Meta Business Manager, owned by you.
It does not release your phone number — the number remains registered to your WABA with Meta.
It does not delete your contacts, campaigns, templates, staff, settings, or any other data in Xobito.
It does not cancel your Xobito subscription — billing continues until you explicitly cancel it.
It does not delete your chat history — past conversations stay fully searchable.
It does not affect Meta’s billing — any charges already incurred by Meta for conversations are still owed.
Think of disconnecting as “pause the live connection to Meta”, not “delete everything”. Nothing you’ve built is lost.

When you should disconnect

Moving to a new Xobito workspace

A number can only be on one Xobito workspace at a time. Disconnect in the old one, then connect in the new one.

Changing providers

If you’re moving to a different BSP or back to Meta’s own tools, disconnect first, then connect the number elsewhere.

Resetting a broken connection

When the webhook or token is stuck in an error state, disconnect + reconnect is the clean fix.

Ending a trial or pilot

If you’ve decided Xobito isn’t for you (sorry to see you go), disconnect to stop any accidental sends.

When you should NOT disconnect

  • To “save money” — disconnecting doesn’t reduce your Xobito or Meta bills. Cancel the subscription for the former; for the latter, just stop sending.
  • To “reset” a campaign or template issue — those are fixable without disconnecting. See Troubleshooting.
  • To test something — it’s disruptive. Use a staging number if you need to experiment.

How to disconnect

1

Go to Setup → Account

In the left sidebar, expand Setup and click Account.
2

Find the WABA you want to disconnect

If you have multiple WABAs, make sure you pick the right one.
3

Click 'Disconnect'

A confirmation dialog opens.
4

Read the confirmation carefully

The dialog lists everything that will happen — running campaigns, active chats, webhook.
5

Type the confirmation word

To prevent accidents, Xobito asks you to type DISCONNECT (case-sensitive). This only appears if you have active campaigns or chats.
6

Click 'Confirm Disconnect'

The disconnection happens in seconds. Status flips to Disconnected and a confirmation banner appears.
Disconnecting is immediate. There is no “undo” button — but you can always reconnect afterward. If you accidentally disconnect, just run the connect flow again. Nothing is lost.

What happens to in-flight campaigns

If you disconnect while a campaign is sending:
  • Messages already sent — delivered as normal. Meta still processes them.
  • Messages queued but not yet sent — these are cancelled. They won’t be sent later even if you reconnect.
  • Campaign status — marked as Partially sent — disconnected in the Campaigns list.
If you’re actively mid-campaign, let it finish first before disconnecting. Or pause the campaign cleanly from Campaigns → [name] → Pause instead.

What happens to active chats

  • Session windows stay open with Meta, but Xobito can no longer send replies (the token is revoked).
  • Incoming messages stop arriving because the webhook is unsubscribed.
  • Chat history remains visible and searchable in Xobito.
  • Agents see a red banner on each chat: This WABA is disconnected. Reconnect to resume replies.

What happens to your data in Xobito

Nothing is deleted. Specifically:
DataStatus after disconnect
ContactsIntact, unchanged.
Tags, groups, custom fieldsIntact.
TemplatesIntact — but Xobito can no longer sync status updates from Meta for this WABA.
Campaign history & analyticsIntact.
Chat historyIntact.
Bot flows & message botsIntact — they simply don’t fire because no events arrive.
Staff, roles, permissionsIntact.
Workspace settingsIntact.
Billing & subscriptionUnchanged — continues until you cancel.

Reconnecting later

Good news: reconnecting is as simple as the first-time connection. Your existing data stays put — it just resumes flowing.
1

Go to Setup → Connect WhatsApp

The connect screen looks just like the first time.
2

Click 'Login with Facebook'

Meta’s embedded signup opens.
3

Pick the same WABA

Choose the WABA you previously had connected.
4

Pick the same phone number

You don’t need to re-verify if the number is still on the WABA.
5

Grant permissions

Xobito receives a fresh access token.
6

Wait for the success screen

Status flips back to Connected. Webhooks resubscribe automatically.
After reconnecting, incoming messages resume, templates sync, and you can send again right away.

Reconnecting to a different Xobito workspace

A phone number can only be connected to one Xobito workspace at a time. Here’s how to move it:
1

Disconnect in the old workspace

Follow the disconnect steps above. This frees the number from that workspace’s tokens.
2

Log in to the new Xobito workspace

Switch accounts.
3

Run Connect WhatsApp in the new workspace

The same WABA and number are now selectable.
The chat history from the old workspace stays in the old workspace. It does not migrate. Templates and contacts also don’t migrate — each workspace is independent. If you need data across, export/import manually.

Permanently leaving Xobito

If you’re disconnecting because you’re leaving the platform:
1

Disconnect the WABA

Stops message traffic via Xobito.
2

Export any data you want to keep

Go to Contacts → Export, Campaigns → Export, and Chat → Export to download CSV copies of your data.
3

Cancel your subscription

Profile → Billing & Subscription → Cancel Plan. See Billing.
4

Request workspace deletion (optional)

If you want all your data removed from Xobito, email support. Deletion is permanent.
Your WABA in Meta remains entirely yours. You can connect it to any other provider — or use Meta’s own tools — without any involvement from Xobito.

Troubleshooting

This usually means Meta has already revoked Xobito’s token (e.g. from a change in Business Manager). The disconnect still succeeds on Xobito’s side — refresh the page and you’ll see the WABA marked Disconnected.
No. Reconnecting restores the connection with no data loss. Any messages queued for delivery during the disconnect window won’t be sent retroactively, but everything else is intact.
Meta charges for conversations that happened before the disconnect. If you see a charge for a period after the disconnect, check that no other BSP has the number connected. If Xobito’s billing shows charges after disconnect, contact support immediately.
The number is linked to a different workspace, a different BSP, or a stale Meta session. In Meta Business Manager, go to the WABA → Partners / Integrations, remove any unexpected integration, then retry connect in Xobito.
Templates stay visible but Xobito can’t sync their status from Meta without a connection. Reconnect to resume syncing.
Email support from the email on your account with the subject “Delete my workspace”. We permanently delete within 14 days after verification. This is irreversible.

Where to go next

Reconnect

Run the connect flow again — your data is waiting.

Billing & Subscription

Manage your plan and payments.