On this page
A short round of changes to broadcast reports, WhatsApp forms, settings pages and the sending status of a number.
Broadcasts
On a broadcast's report, the two lists that explain the delivery funnel, why recipients were skipped and why sends failed, now use the full width of the card with one reason per row and a line between them. Each reason is a sentence of Meta's words and a next step, and in two narrow columns they ran together into one block.
WhatsApp forms
When Meta refuses to create, publish or change a form, the message now carries Meta's own error code and its reference number, for example "Meta error 139000/4233020, reference ...". Meta Support asks for both, so you can quote them as they are when you contact Meta about a form.
Names that are already in use
Adding or renaming a chat stage, a saved segment, a custom role or a pipeline with a name the workspace already uses now shows "A stage called ... already exists. Pick a different name." beside the field. Before, a chat stage with a repeated name could open an error page instead. Names are trimmed, and a stage name can be up to 50 characters.
Sending status of a Meta test number
A number Meta lends you while you set up (it starts +1 555) cannot send anything until Meta approves its display name, and the channel card says so. Once Meta delivers a message from that number, the card and the broadcast check now follow Meta's own status instead of staying blocked. Meta can keep its "display name has not been approved" note on the number for a while after the approval, and that note alone no longer stops your broadcasts.
What to do
Nothing is required. The changes apply to every workspace. If a figure on screen does not match what you expect, write to [email protected] and we will check it against your data.