Skip to main content
Question

Paying €100/month while my business is completely blocked by a ManyChat credit line issue — unacceptable support

  • August 7, 2026
  • 1 comment
  • 18 views

Lamayun

I’m extremely disappointed with how this situation is being handled.

I’m paying around €100/month for ManyChat and my business launch is currently completely blocked because ManyChat cannot share its WhatsApp credit line with my WABA.

The error is:

“Manychat's credit line could not be shared with you.”

I have already followed the official ManyChat WhatsApp Credit Line Troubleshooting documentation step by step.

We verified:

  • WABA currency is USD
  • There is no payment method attached to the WhatsApp Business Account
  • There is no existing credit line visible in Meta Billing Hub
  • ManyChat was removed as a partner and reconnected
  • The WhatsApp number is connected and the account is active
  • The error still remains

Your own documentation then tells me to remove the phone number from the existing WABA through WhatsApp Manager → Phone Numbers → Delete and reconnect it to a new WABA.

The problem is that Meta does not provide any Delete/trash option for my phone number, so I physically cannot complete the troubleshooting procedure ManyChat itself tells me to follow.

WABA ID: 1017027507966419

At this point the problem requires someone from ManyChat who actually has technical access to WhatsApp/BSP/credit-line configuration to investigate the backend association.

Instead, I am stuck waiting for human support while an active business is unable to launch.

And this is the part I find completely unacceptable.

This is not a free tool. I am paying a significant monthly subscription specifically because I need ManyChat to be reliable infrastructure for a commercial funnel. A billing/integration problem that makes a core channel unusable should not leave a paying customer waiting indefinitely for someone to respond.

I have also been dealing with Meta support, where getting access to an actual specialist has taken an absurd amount of time. Now I am experiencing essentially the same situation with ManyChat.

A business cannot operate like this.

When an integration problem completely blocks a customer's primary sales funnel, there needs to be an escalation path to a qualified human technician within hours — not days of bots, generic troubleshooting articles and waiting.

I have already opened a Critical support ticket and supplied screenshots proving all of the above.

What I need now is not another troubleshooting article. I need a ManyChat WhatsApp/Payments specialist to:

1. Identify exactly why the ManyChat credit line cannot be shared.
2. Check whether there is a stale BSP/credit-line association invisible in Meta's interface.
3. Release/reset it from the backend if necessary.
4. If a new WABA is required, provide the exact supported procedure for my configuration, since Meta does not expose the Delete option described in your documentation.

I genuinely hope someone from ManyChat sees this and takes ownership of the case.

Because having a paying customer's business completely stopped by your infrastructure while the customer waits days to reach someone capable of fixing it is, frankly, an unacceptable level of support for a business-critical platform.

If ManyChat wants businesses to trust it as infrastructure rather than as a simple chatbot tool, situations like this need to be handled much better.

1 reply

SumGenius
Forum|alt.badge.img
  • Smooth talker
  • August 7, 2026

You've done more troubleshooting than most. Two things that might explain the missing Delete option, since Meta hides it in specific cases:

1. Meta blocks deleting a number if any paid messages went out from it in the last 30 days. It's in their help center under "delete your phone number from the WhatsApp Business Platform." If that's your situation, the button appears once the 30 days pass.

 2. Delete only shows for people with business admin on the WABA itself, not just the Facebook page. Worth checking your role in Business Settings.

On the credit line itself, you're right that this one isn't fixable from your side. The credit line allocation lives in the BSP's config with Meta, so only ManyChat can see whether there's a stale association on WABA 1017027507966419. Hope they escalate it, this shouldn't block a launch.