Announcements

An announcement takes an offer and pushes it to your customers, instead of waiting for them to ask. Announcements only exist on campaigns for existing customers.

​

Sending one

Press Announce on the offer’s card or page, or go to Announcements: the Send an announcement box sits above the list of announcements Sent so far.

1. Offer: one of your running offers.
2. How it opens: the approved template the announcement opens with, filled in if the offer carries one. An offer with its own template always opens with it; to change it, change it in the offer.
3. Who gets it: leave Labels empty to reach every customer on the campaign, or pick labels to narrow it, such as Premium, Milan, lapsed. A customer with any of the labels you pick is included. The box counts as you choose: how many customers will receive it, how many are left out because they asked you to stop, and about how long the send takes.

Press Send announcement. Nothing goes out until you confirm: the confirmation repeats the count, the offer and the template. Press Send now, or Not now. Read the number: an announcement can’t be unsent. The send is refused, with the reason, when nobody matches, when the audience is too large for one announcement (narrow it with labels), when the offer has ended, or when WhatsApp has not approved the template.

​

What your customer sees

They get your approved template — the short opener you chose. When they reply, the assistant takes over: it sends any photos attached to the offer, explains the offer properly, asks anything you wanted to know, and then goes back to being available for whatever else they need. When the offer opens with its own template, the template already said it all: the assistant skips the explanation and goes straight to your questions.

​

A photo, a PDF or a video in the announcement

If the template was approved with a header file, every announcement that uses it carries that file above the text — so the customer sees it straight away rather than after replying. The file is chosen on the template, under Integrations, and is fixed for as long as the template exists. If a template expects a header file and none is set for it, the announcement is not sent to anyone and says so, naming the template — rather than each customer getting a message with a blank at the top.

​

Template variables

If the template has variables, they are filled in for each customer from what you know about them:

• {{name}}, {{nome}}, {{nombre}} and the like → the customer’s name; {{phone}} / {{telefono}} and {{email}} likewise.
• Any other named variable → the matching column from your import, matched loosely: {{Piano_Attivo}} finds a piano attivo column.
• A numbered {{1}} → the customer’s name. A template with {{2}} and beyond can’t be announced, because nothing says what they stand for — use named variables instead.

A customer who has no value for a variable is not sent a blank: that send is marked failed with the reason, and everyone else is reached.

​

It goes out slowly, deliberately

An announcement to a large customer base takes hours or days, not minutes. Several things pace it, and all of them are protecting your WhatsApp number:

• Your sending hours. Nothing goes out outside the hours set in Settings. Nobody wants an offer at 3am.
• Your pacing. The interval in Settings applies here too.
• A daily ceiling. There is a limit on how many people one business messages in a day, regardless of your plan.
• Recent conversations are skipped. Anyone who has messaged you — or been messaged — in the last 24 hours is left out and reached later. Somebody mid-conversation should not be interrupted by an unrelated promotion, and two announcements should never stack on the same person.

You can change the 24 hours with Leave recent conversations alone in Settings, or set it to 0 to switch it off. An announcement whose whole audience was contacted recently therefore sits at 0 sent until they go quiet — which is the rule working, not a stuck send. The announcement says so itself: “2 customers are waiting (contacted too recently); sending resumes around …”, with the time the first of them becomes reachable. If you need it out sooner, lower the quiet window in Settings and the next pass picks them up.

​

Who is left out

Three groups never receive an announcement:

1. Anyone who opted out of marketing. Checked at the moment of sending, not when you chose the audience — so somebody who says STOP halfway through a send is not reached by the rest of it.
2. Anyone without any of the labels you picked, when you picked some.
3. Anyone in a recent conversation, as above — they are reached on a later pass.

​

Following and stopping one

Each announcement in Sent so far shows its status (Queued, Sending, Finished, Stopped, or Paused: campaign stopped) and how many were Sent, are Remaining, were Skipped and Failed. Press Stop sending to stop one. Nobody who has not yet been reached will be. Messages already sent are already on someone’s phone, and stay in the record. Stopping the campaign also pauses the send; starting it again resumes it where it stopped. While the campaign is stopped, the page says This campaign is stopped: nothing goes out and the assistant answers nobody. Start campaign starts it from there.

​

Several at once

You can queue a second announcement while the first is still going out. Nobody gets both in the same afternoon: the quiet window above skips anyone messaged in the last 24 hours, so a customer who just received the first offer is reached with the second on a later pass — exactly as if you had sent them one after the other. Both sends share the same daily ceiling and pace. If you set the quiet window to 0, two announcements can reach the same person back to back. That is your call, not the default.