Browse documentation

Contact and import problems

Rejected numbers, members who never receive anything, and limits.

The import was rejected

MsgOrb rejects a bulk import in full if any row has a number it cannot read, and names the offending values. This is deliberate — a half-import leaves contacts that look present and silently never receive anything.

Fix the file so every number is in full international format with a leading + and the country code, then import again.

A number was accepted but never receives anything

Check the contact in Team Access:

  • Pending status — approve them, or turn on auto-accept.
  • Opted Out health — they replied STOP. They cannot be re-added from inside MsgOrb.
  • No group — workflows target a group. A contact with no group receives nothing.

If the contact looks fine on all three, search their number on Delivery and Queue Health and read the error on the failed rows. Meta error 131026 means the number has no WhatsApp account.

You have reached your limit of N members

Every plan caps stored contacts. See Plan limits and upgrade on Billing.

Two entries for the same person

MsgOrb matches on the normalised number, so this only happens when the two records genuinely differ — for example one saved before a country code was added. Delete the older one.

The same number appears in two groups

That is supported: membership is per group, and a number may be listed under a different name in each. The Inbox shows the group alongside the name so an ambiguous number is never silently collapsed.