Restrictions & limits

Why is my number health Unknown or unavailable?

Unknown or unavailable is not a zero score or proof that the number is banned. A health estimate needs enough eligible observations, and its time range, coverage, and reliability matter. It is a diagnostic signal, not a delivery or account-safety guarantee. Review the displayed period and any unavailable reason. Compare the actual connection or send error separately. If the view appears inconsistent, report the number reference, time, and visible health details to support. Do not send message history to fill the gap; health does not require customer conversation content.

Last updated on Oct 04, 2026

Why are safety controls slowing or blocking my sends?

Safety controls can pace or hold sends according to the applicable policy and the number's state. That is different from a WhatsApp account ban. Turning off a local retry loop does not change the actual reason for a held action. Read the displayed limit or hold reason and review your sending pattern and consent. Do not evade it by rotating numbers or duplicating campaigns. If the policy result conflicts with the observed action, send support the reference and time. BanSafe and pacing reduce specific risks; they do not guarantee that WhatsApp will never restrict a number.

Last updated on Oct 04, 2026

Can Polymorfa support remove a WhatsApp ban?

WhatsApp owns its account restrictions and review decisions. Polymorfa support cannot unlock a banned account or promise that a review will succeed. Use the review option in WhatsApp when it is offered for your account. Tell Polymorfa support when the restriction appeared and share a reviewed screenshot of the warning if needed. We can investigate the connection and relevant Polymorfa errors, separately from WhatsApp's decision. Do not send registration codes or pay someone claiming a guaranteed unban. See WhatsApp account bans.

Last updated on Oct 04, 2026

Why is a number suspended when my team still has credits?

The team balance is only one funding check. The number, its customer, and its project can each have a monthly spending limit. Credits reserved or protected for higher-priority demand can also be unavailable to this charge. Read the specific billing reason and inspect the applicable limits in the native number, customer, or Usage controls. Raising one limit does not bypass another or create credit. An owner or administrator can review the intended cap and priority. If all shown blockers are resolved but suspension persists, send support the number reference and time.

Last updated on Oct 04, 2026

Why did setting a spending limit to zero block my number?

Zero is a real cap: it blocks new charges. It is different from an unset limit, which allows spending subject to the team's other safeguards. Already-paid service can continue until the paid window ends even after a new cap blocks its next charge. If you intended to remove the cap, use the relevant Remove limit action or empty limit field and save the change. Review customer and project caps as well as the number's own cap. If a saved change is not reflected, report the value and time to support. Do not repeatedly reconnect to bypass a budget.

Last updated on Oct 04, 2026

Why has my monthly budget not reset on my local calendar date?

Spending limits use the UTC calendar month and reset at midnight UTC on the first day. That moment can fall on a different local date or time. Reserved charges also count against available budget until consumed, released, or expired. Compare the displayed month and timestamps using UTC before treating the total as incorrect. Credit purchases and direct Meta charges are separate from Polymorfa number-service spending. If the new period still shows an unexplained commitment, report the scope, displayed values, and time to support instead of deleting the limit.

Last updated on Oct 04, 2026

Why can I not spend credits that appear in my balance?

Some credits can be reserved for a pending operation or protected for higher-priority number renewals. Total balance is therefore different from the amount available for a new start. A payment hold or monthly cap can also refuse the charge. Check Usage, funding priorities, and the exact billing error. Do not change priorities simply to silence a warning without considering which numbers need protection. If the available amount cannot be explained, send support the time and redacted balance details. Re-pairing the number does not free a valid reservation or override funding rules.

Last updated on Oct 04, 2026

Why am I asked to upgrade before adding a number or project?

A Free team has one active project and one free real number. It also has a testing-number allowance. An action beyond those limits requires Pay-As-You-Go; an invitation to another member does not itself require a paid team. Check the resource type and the selected team's billing mode. Only an owner or administrator can complete the team's upgrade requirements. Upgrading applies to the whole team and is irreversible. If the team is already Pay-As-You-Go but the same prompt appears, send support the action and displayed mode rather than creating another team to avoid the limit.

Last updated on Oct 04, 2026

What should I do after a rate-limit or too-many-requests error?

Read the returned error and any Retry-After instruction before retrying. A request-rate limit, a number's sending restriction, and an exhausted spending budget are different constraints. Increasing concurrency can make a rate-limit problem worse. Reduce or pause the retrying workload and retain request references for a small sample. For supported idempotent actions, preserve the same key on a retry. If the indicated wait has passed and the same refusal continues, report the endpoint, safe error code, time range, and request rate to support. Do not include credentials.

Last updated on Oct 04, 2026

Why is a feature available to another team but not mine?

Availability can depend on the number type, billing mode, project eligibility, or enrollment in a limited release. A visible SDK method or another customer's screenshot does not establish access for your project. Team permissions still apply independently. Check the feature's availability message and the correct project. Ask support about the named eligibility or enrollment requirement if it is unclear. Do not change number tiers or buy an add-on unless that requirement actually calls for it. A support code cannot grant access or bypass a disabled feature.

Last updated on Oct 04, 2026

Why are paid actions blocked across my whole team?

A frozen team, payment dispute, or subscription recovery issue can affect paid actions across projects. Adding credits alone does not necessarily resolve an account-level hold. The billing alert identifies the issue requiring attention. Have an owner or administrator review Billing and the requested recovery action. Use the existing purchase or dispute reference when contacting support. Do not open a replacement team to evade the restriction or repeat uncertain payments. If a confirmed recovery has not restored the expected action, report its completion time and the remaining error.

Last updated on Oct 04, 2026

Why can a healthy number still have a failed send or restriction?

Health is an estimate from eligible observations, not a promise about every future action. Connection state, funding, recipient eligibility, and WhatsApp restrictions can change independently of the score. An older estimate can also describe a different period from the failure. Use the actual send or connection error to investigate the incident. Include the health period only as additional context. Do not treat a high score as permission to ignore opt-outs or sending safeguards. If the estimate and evidence appear inconsistent, send support the references and times without customer message content.

Last updated on Oct 04, 2026

Appearance

Language

Why is my number health Unknown or unavailable?

Why are safety controls slowing or blocking my sends?

Can Polymorfa support remove a WhatsApp ban?

Why is a number suspended when my team still has credits?

Why did setting a spending limit to zero block my number?

Why has my monthly budget not reset on my local calendar date?

Why can I not spend credits that appear in my balance?

Why am I asked to upgrade before adding a number or project?

What should I do after a rate-limit or too-many-requests error?

Why is a feature available to another team but not mine?

Why are paid actions blocked across my whole team?

Why can a healthy number still have a failed send or restriction?