How to use WhatsApp to announce new paid events

You've confirmed the next date, the ticket page is ready, and you have a list of people who enjoyed the last event. Sending them a WhatsApp message feels like the obvious next step. They already know you. Some have even asked when you're doing it again. Why pay to reach strangers before telling those people?

That can be a good decision, provided the list really contains people who agreed to receive these messages, your chosen WhatsApp service can reach them, and someone will answer when they reply. A phone number collected for a booking doesn't settle any of those questions. Neither does a previous conversation about a missing ticket.

For most paid event businesses, I'd start with one relevant announcement to a small audience that has opted in. Tell them what the new event offers, send them to the actual ticket checkout, and judge the result after including the work of handling replies. Expand when you have evidence that the messages help sell additional places at a cost the event can support.

This guide concerns direct WhatsApp Business messages about new events. If you want an optional public feed for general updates, our guide to WhatsApp Channels for event ticket holders covers that different decision. Here, the recipient gets a message from your business and can answer you privately. That changes the promise you're making and the work your team needs to do.

Decide what the announcement is supposed to achieve

Start with the event you need to sell. A useful brief might be, "We want previous beginner workshop buyers who asked for future dates to book the new beginner series." That tells you who the message is for and why it should matter. "We want to use WhatsApp more" tells you very little about either.

The distinction becomes obvious when you look at your past audience. Someone who bought an advanced ceramics workshop may not want a beginner class. Someone who attended in another city may be unable to travel. A person who booked a birthday outing for friends may have no continuing interest in the programme. Your contact list records a past transaction, with whatever permissions accompanied it. You still have to choose a relevant offer.

Use one running example. Imagine a fictional business called Workshop House, selling small, in-person creative classes. It is opening two beginner printmaking workshops, each with 24 paid places. Eight places on each date have already sold through other activity, leaving 32 available across the two dates. The team wants to test a direct announcement to people who explicitly chose future beginner-workshop news on WhatsApp.

Those numbers are invented planning assumptions, not customer results or recommended audience sizes. They let us work through the decisions without pretending every event needs the same campaign. Workshop House has something bookable, a defined audience, and remaining places. If your new date isn't confirmed, you need a different message about registering interest, with no implication that a booking is available.

Set the outcome before drafting. Do you want a completed purchase, an answer to a genuine planning question, or an enquiry for a group booking? Those require different actions. For an ordinary public workshop announcement, a clear route to the ticket page is usually better than requiring everyone to reply before seeing the price.

You can still welcome questions. The important part is avoiding a purchase process that depends on a member of staff being free to explain basic information to every interested buyer. If the message generates the same question repeatedly, improve the offer or page. Don't treat unnecessary conversations as evidence that the campaign is working.

Choose between the Business app and the Business Platform

WhatsApp Business isn't one identical sending tool for every operator. The Business app is the phone-based business product. The Business Platform supports business messaging through software, often through a provider that supplies the inbox and campaign controls. Choose after checking the work you need to do, rather than assuming that a feature demonstrated in one product exists in the other.

For a very small operation, the app may be sufficient if its available tools support the intended messages and you can maintain permissions and replies properly. WhatsApp's help page about app marketing messages describes limited-country availability and notes that the feature is called business broadcasts in some countries. Don't build a plan around an old screenshot or assume every account has identical tools.

A team needing controlled campaign sends, shared handling and records may prefer a Platform provider. Ask it to demonstrate those functions in the service you're considering. "WhatsApp integration" is too vague to evaluate. You need to know who can send, who sees replies, how someone opts out, and what happens to a queued campaign when a person has already purchased.

The Platform also brings specific template rules. Meta's Business Messaging Policy requires approved templates to initiate conversations. A user message opens or resets a 24-hour customer service window in which you can reply without a template. Outside that window, an approved template is required again. These are Platform rules, not a description of every action in the Business app.

For the operator, the practical question is whether the planned announcement can be sent lawfully and reliably using the chosen service. A provider should show the actual template, eligible recipients, sending status and reply process before you commit to a contract. An attractive inbox demonstration doesn't establish that your launch campaign can reach the people you intend.

Avoid tools promising to turn a personal account into an unrestricted bulk sender. An event launch needs a dependable business process. If the proposed method depends on avoiding the normal restrictions, you can't sensibly budget around it. Choose a supported route or use another channel you have permission to use.

Check recipient markets before paying for setup

Check where your intended recipients can receive the proposed message type. Your venue's location and your company's address don't, by themselves, answer that question. An international festival can have buyers with phone numbers from several markets, while a locally based audience can include people using numbers issued elsewhere.

As checked on 27 October 2026, Meta's geographic availability documentation says it does not deliver marketing messages to WhatsApp users in the United States through its Business Messaging APIs, the software interfaces used to send messages. The restriction began on 1 April 2025. A US business number can still message users outside the US, subject to the applicable rules.

If your launch depends on marketing announcements sent through these software interfaces to US recipients, don't buy a service on the assumption that consent alone makes those announcements deliverable. Ask the provider to identify the restriction in your proposed audience and demonstrate an eligible use before spending on implementation. A marketing announcement remains promotional even when the people receiving it have purchased from you before.

The same Meta documentation describes geographic limits on delivery optimisation and click and conversion reporting. These include messages sent from or to several named markets, including the UK and European Economic Area. Check the actual feature you want. Being able to send a message doesn't establish that a particular reporting feature will be available for it.

Keep an account of which recipients are eligible, which are excluded, and why. Do this before estimating delivery costs or promising a presale. If the usable audience is too small, the sensible decision may be to use your established email programme instead. A technically possible campaign can still be a poor use of staff time.

For Workshop House, assume the pilot audience is in a market where the chosen service supports the planned marketing messages. That is an explicit condition of the example. The budget later in this guide is not a workaround for a restricted market, and using US dollars for arithmetic does not imply that the audience is in the United States.

Restrictions change. Save the date and current eligibility check with the campaign brief, then check again before the next launch. Give someone responsibility for this if you're signing a longer provider contract. Otherwise, a campaign that worked for one edition can quietly become the assumption behind several future budgets.

Ask for permission people can actually understand

The clearest starting point is an optional choice that names your business, WhatsApp, and the sort of messages people will receive. Someone should be able to say yes because they want that offer, and buy a ticket without saying yes. A compulsory phone field for event-day contact isn't an adequate explanation of future marketing.

For Workshop House, proposed signup wording could read, "Send me WhatsApp announcements about new Workshop House beginner workshops at our Mill Street studio. We expect to send up to two announcements a month. I can stop them by replying STOP." Put the privacy information and alternative contact route where the person can find them. Use a frequency the team can keep, rather than copying this fictional example automatically.

This is suggested editorial wording for the pilot, not a universal legal form. Check your local requirements and the exact collection process. Meta requires the person to provide their number or username and opt in to subsequent contact, and requires businesses to honour opt-outs made on or off WhatsApp. Collecting a number and obtaining permission are separate parts of that process.

In the UK, the ICO's electronic mail marketing guidance includes stored social direct messages within the rules for electronic mail. It explains consent and a limited existing-customer exception, often called the soft opt-in. That exception has conditions. It doesn't make every past ticket buyer contactable, and it doesn't remove WhatsApp's own requirements. The ICO flags this guidance as under review, so check the current version for your circumstances.

Don't send an unsolicited WhatsApp promotion merely to ask whether someone wants WhatsApp promotions. Offer the choice through a lawful route you already use, such as an appropriate signup page or an existing permitted communication. A public invitation can explain what people will receive and let them make the choice themselves.

Keep enough evidence to understand the permission later. Record the contact, business named, purpose, wording version, time and collection source, together with any withdrawal or changed preference. Limit access and retention according to your actual obligations. A row marked "yes" becomes difficult to trust when nobody can establish what the person agreed to.

Our guide to event email marketing consent explains why buyers, guests and separate marketing choices need careful handling at checkout. Apply the same care to WhatsApp while checking its distinct requirements. An email permission record should never silently become a WhatsApp permission record.

Build the audience from relevance and current permission

Prepare a campaign audience you can explain in ordinary language. For Workshop House, that might be "people who chose beginner workshop announcements at the Mill Street studio on WhatsApp, have not opted out, are eligible for this send, and have not booked either announced date." The final condition is a campaign decision. A person who already booked may still want other dates, but don't assume another sales reminder is useful.

Recheck the list close to sending. Purchases and opt-outs can occur after you prepare it. If your software handles those changes automatically, verify the rules and test them. If it doesn't, assign the checks explicitly. A tidy list prepared last week can produce a very untidy launch today.

Keep different reasons for exclusion separate in your working record. "Already booked" means something different from "withdrew permission" or "market unsupported." A buyer might later become relevant for another date. Someone who opted out needs that preference respected across future campaigns, not rediscovered whenever a different employee imports an old file.

For an event series, choose the narrowest useful interest at first. Asking for beginner workshops in one city doesn't necessarily express interest in every retreat, festival and professional course your company might launch. If you expand the programme substantially, revisit the original expectation before adding people to the new stream.

Be especially careful with group bookings. The purchaser's choice doesn't automatically cover every guest whose name appears on the booking. Likewise, a sponsor, venue partner or performer can't give you permission to message their audience directly merely by sharing a spreadsheet. If the partnership is valuable, agree a lawful invitation process that lets people choose to hear from you.

You also need a way to recognise a corrected number or changed owner. Avoid treating a phone number as permanent proof of identity or continuing interest. When a recipient says the message has reached the wrong person, stop the relevant contact and investigate the record. Don't demand that they prove they never attended your event before you act.

The aim isn't to create a large database of facts about every customer. Collect what helps you honour their choice and send the relevant offer. If a proposed field doesn't change a legitimate campaign decision, question why you need it. More fields create more maintenance and more opportunities for an employee to use information in a way the person didn't expect.

Treat the new event as marketing, even for returning buyers

A new event announcement is asking someone to consider another purchase. Calling it an "update" doesn't change its purpose. This matters when choosing the Platform template category, estimating cost, and deciding who should receive it. Your previous buyers are a useful audience when the offer fits and permission is valid. They aren't automatically recipients of every commercial message.

Meta's template categorisation guidance distinguishes promotional marketing from non-promotional utility messages tied to user actions, requests or essential information. It also treats templates mixing utility and marketing content as marketing. Apply for the category that matches what you're actually sending.

Compare two fictional messages. "The beginner printmaking workshop you booked for 14 November now starts at 10:30am" concerns an existing booking, assuming the change is real. "We've opened another beginner printmaking workshop on 21 November; book your place" promotes a new purchase. Don't combine the second offer with the first simply to make it look like service communication.

Separate the audiences and workflows. The start-time change goes through the process for affected ticket holders, using the appropriate permissions, channel and template where required. The new-date offer goes to people eligible for that promotion. Staff should be able to explain which job each message does without needing to interpret the sender's intention.

Template approval isn't a lasting guarantee of availability or delivery. The content, category and status need checking in the sending service before launch. If a template is rejected or paused, resolve the issue rather than finding a nearly identical template under another label. Protect the rest of your event communications from a rushed attempt to force a promotion through.

For Workshop House, prepare the announcement early enough to complete review and testing before the promised presale. Keep a fallback plan using an independently permitted channel. If the fallback would change who gets early access, explain that before promising exclusivity. A technical delay becomes a customer complaint when people believe you sold their opportunity to someone else.

Keep the approved version with the campaign record, including language and destination. That gives the person handling replies the same offer recipients saw. If a customer says the message promised materials or a discount, the team should be able to check the actual wording immediately.

Write the message around the buyer's decision

The message needs to answer a few practical questions quickly. Who is contacting me? Why might this event suit me? When and where is it? What will I pay, and where can I see the full offer? You don't need a miniature sales page, but you do need enough information for someone to decide whether opening the page is worthwhile.

For the fictional pilot, a proposed message could read, "Workshop House has opened two new beginner printmaking dates at our Mill Street studio: 14 and 21 November 2026, 10am to 1pm. You'll make a small lino print with tutor guidance; tools and materials are included. Tickets are $70 per person, including mandatory booking charges. See the dates and book on our Workshop House ticket page. Questions? Reply here. Reply STOP to stop these announcements."

The dates, studio and dollar price are part of the fictional example. An actual message should use the event's selling currency and verified payable price. The copy is also a proposal for review and Platform submission where required. It isn't an already approved template.

Notice what the offer does. It names the activity and level, gives a real choice of dates, and explains what is included. Someone doesn't have to reply "price?" to find out whether it fits their budget. If your ticket price varies by date or release, say so accurately and make the relevant choices obvious on the linked page.

Avoid fake familiarity. "You loved the last one" is an assumption unless the person actually told you that. "You previously asked for beginner workshop announcements" describes a recorded choice, if true. You can write warmly without pretending to know how a customer felt or why they haven't booked again.

Keep essential details in text even when the message includes an image. The W3C's accessible writing guidance recommends clear instructions, meaningful links and text alternatives. A poster alone can leave someone hunting for the date or unable to read the price. A short written explanation also helps a forwarded message remain understandable.

If you plan a reminder, decide what genuinely changes. A confirmed closing date or a relevant new detail may justify one. "Just bumping this" asks for another interruption without offering much help. Set the contact limit in the brief and respect the promise made at signup. No response is a reason to reconsider relevance, not to send increasingly urgent variations.

Send buyers to a checkout the team can trust

Open the exact link on a phone that isn't already signed into your organiser account. Check both dates, ticket availability, payable price, inclusions, access information and terms. Then complete a controlled test of the purchase journey using your platform's supported process. The message can be excellent and still lose the sale at an incorrect date selector.

Keep one authoritative place for availability. If you tell three people in private chats that the final place is theirs, you can create conflicting promises even while the checkout is behaving correctly. Define whether a chat reply merely provides information or creates a formally recorded reservation. Staff should never invent an informal hold because a buyer sounds enthusiastic.

With Loopyah ticket checkout, buyers can choose ticket types at their current price, pay, and receive a confirmation email linking to QR tickets. That gives your announcement somewhere concrete to send the customer. The messaging team still has to choose the right destination and avoid promising a place before the booking is confirmed.

If the workshop sells out during the campaign, stop any remaining sends where your service allows, review scheduled reminders and update replies. A message already delivered can still be opened later. Its link should show truthful availability and a clear next option, rather than implying that the original message guarantees admission.

Keep payment details out of the chat. Send people to the authorised checkout or support process, and train staff to recognise requests that need private handling. A customer may paste sensitive information without being asked. Have a procedure for that situation, including appropriate access and retention controls, instead of allowing screenshots to circulate around the event team.

A practical question can also reveal that the sale isn't suitable. If a participant asks whether the room can meet an access requirement, get a checked answer from the responsible person. Don't pressure them to buy before you know. Accurate information can prevent an unsuitable purchase and a problem at the door, even if it reduces the campaign's immediate sales count.

Keep the wider campaign consistent. Our event marketing plan guide can help place the announcement alongside other promotion. The WhatsApp price, email offer and public ticket page should describe the same entitlement. If one audience has a genuine presale benefit, document that difference so support can explain it.

Staff the reply inbox before you send

A direct announcement invites conversation, whether or not you write "reply here." Before launching, decide who checks the inbox, during which hours, and who covers breaks or absence. Set an answer you can actually deliver. Sending shortly before the only trained person finishes work can turn a useful announcement into a queue of unanswered purchase questions.

For Workshop House, imagine a campaign owner sends during a staffed morning. The support colleague knows the event details and can handle routine questions. The event manager answers unresolved access or programme questions. These are responsibilities assigned within the existing team, not a recommendation to hire three people for a small workshop campaign.

Prepare responses for likely questions, then allow staff to answer the actual person. "All materials are included" might answer one buyer. Another may be asking whether a specific tool is suitable for them. A saved reply helps only when it addresses what was asked. Repeatedly pasting the ticket link can sound dismissive when someone needs information that isn't there.

Decide what staff can promise. Can they offer a discount, change a booking, reserve a place, or approve a refund? If not, tell them who can. A quick reply containing an unauthorised promise can cost more than a slower but accurate answer. Keep a short record of commitments that affect the booking.

On the Platform, track the customer's most recent message when responding. The 24-hour service window follows user messages; sending a business announcement doesn't by itself give you unlimited free-form follow-up. Configure the provider's controls and train staff so an unfinished question doesn't turn into an unsupported message after the window closes.

Treat requests to stop as work to complete promptly. "Please stop," "wrong number," and an objection sent by email need attention, even when the recipient doesn't type the exact keyword in your message. Record the preference in the relevant systems and check queued campaigns. A polite acknowledgement means little if the next announcement still goes out.

Rehearse an uncomfortable reply too. Give the team a fictional complaint about an earlier workshop, a customer asking for a booking change, and someone reporting an impersonation attempt. Check who takes responsibility and how they find the correct record. The pilot should expose missing decisions before a real buyer is left explaining the same problem to several employees.

Rehearse the send and write down the decisions

Use a short campaign brief that the sender and reply team can both understand. For the fictional pilot, write down the two dates, remaining inventory, audience definition, approved message, tested ticket link, sending time, responsible staff and maximum budget. Add the latest eligibility check and the actual provider quote. That is enough to expose a disagreement before customers see it.

Record what will stop the campaign. For Workshop House, that includes either date becoming unavailable, a template problem, a failure to process opt-outs, or the reply inbox becoming unmanageable. Say who can pause queued messages and who decides when sending can resume. A plan that requires the campaign owner to find the founder for every routine interruption will be difficult to follow during another busy launch.

Test the complete journey with willing staff or other appropriate test recipients using your provider's supported process. One person follows the link and checks both dates. Another asks a question. Another withdraws permission after being added to the proposed audience. Check the saved outcome, including any queued reminder, rather than accepting that the correct button was pressed.

Have the person covering the inbox take over during the rehearsal. They should find the original announcement, understand the buyer's question and identify any commitment already made. If they need the first colleague's personal phone or memory to continue, fix the handover before sending. Your customer shouldn't have to repeat the booking story because somebody went to lunch.

After the first small batch, check actual delivery and replies before releasing more messages. Don't assume that clicking send means the whole audience received the offer. Investigate failures through the provider's supported reports and instructions. Repeated sending without understanding the failure can create duplicates or unwanted contact when the underlying issue changes.

Finally, make the review appointment part of the brief. Allow enough time to handle the resulting bookings and questions, then compare the complete cost with the admissions evidence. If you don't schedule that review, the next event can arrive while everyone still vaguely remembers the first send as a success.

Budget for the work as well as message delivery

Get the current price for the service, recipient markets and message categories you plan to use. Meta's Platform pricing documentation reflects changes effective from 1 October 2026. It charges by delivered message and market-category combination. Your provider may add its own charges, so obtain the complete quote rather than multiplying contacts by an old headline rate.

The October rules also make it unsafe to assume every service reply is free. Meta provides a monthly free tier for service messages per business phone number, then charges beyond it; utility messages inside a customer service window are charged unless an applicable exception covers them. Check current exceptions and the provider's billing. Permission to send a reply and the price of delivering it are different questions.

Use the written quote to estimate message delivery, platform fees, setup, preparation, reply handling and review. State whether tax is included and whether a minimum subscription extends beyond the pilot. If staff are already employed, their time may not create an additional invoice, but it still displaces other work. Show that separately from cash you must pay.

For Workshop House, assume a fictional all-inclusive pilot quote of $60 covers the provider and expected message charges. Preparation and testing take three hours, replies take four hours, and review takes one hour. At an assumed $30 an hour, eight hours of work are worth $240. The total campaign cost is $300: $60 in external cash and $240 in valued staff time. These are invented USD assumptions, not Meta rates or a provider offer.

Each additional paid admission leaves $60 after ticketing charges and ticket-related taxes, then costs $10 in materials and other attendance-related costs. That leaves $50 towards the campaign and event. The fictional $70 buyer price mentioned earlier is consistent with those assumptions, with $10 deducted before the retained $60. Six additional admissions cover the $300 campaign cost. Four leave a $100 shortfall; eight leave $100 after the campaign cost.

This calculation assumes ordinary workshop costs are already committed and the additional admissions fit within the 32 remaining places. It excludes wider business overhead, borrowing costs and income tax, and assumes no refunds or discounts. It measures the extra campaign decision, not the profit of running the whole workshop. If another sale requires an extra tutor or a bigger room, add that cost before using the $50 figure.

Test the assumptions that could change the decision. If support takes four extra hours, total cost rises by $120 to $420, requiring nine additional admissions to cover it. If eight additional admissions each receive a discount that reduces retained revenue by $10, their combined contribution is $320, leaving only $20 after the original $300 campaign. Combine that discount with the extra support work and the result is a $100 shortfall.

Measure what happened without claiming every sale

Keep a simple record of audience selected, messages actually delivered, opt-outs, replies, staff time and paid admissions recorded through the campaign route where reporting supports it. Use the same review period for cost and sales. Don't divide one day's messaging cost by several months of purchases and call that the cost of acquiring a ticket buyer.

Google's campaign URL guidance explains how tracking parameters identify campaigns referring traffic to Analytics. You could use a consistent WhatsApp campaign label for the pilot link, then test that your reporting receives it. Keep names, phone numbers and booking references out of those parameters. A campaign label describes activity, not the person receiving it.

Test purchase reporting separately. A recorded visit doesn't establish a completed payment, and a completed payment can contain more than one admission. Decide which measure the budget uses. Workshop House's calculation uses paid admissions, because each place has the assumed $50 contribution. Counting a two-person booking as one admission would distort that comparison.

Recorded campaign sales still don't prove all those sales were additional. A returning customer might have bought after seeing your email anyway. Someone can forward the link to a friend, or read the message and later arrive through a different route. Keep useful attribution while being honest about what it establishes.

Suppose the pilot records eight paid admissions through its link, but you test the decision using a cautious assumption that only four would not otherwise have happened. The eight attributed admissions represent $400 of contribution under the example's assumptions. The four additional admissions represent $200. Against a $300 campaign cost, that assumption leaves a $100 shortfall. It tests how much your conclusion depends on additional sales; it does not establish how many sales the campaign caused. The distinction can change whether another send deserves funding.

For a larger list, consider a planned comparison with a randomly selected group that doesn't receive the announcement, while keeping essential booking communications available to everyone. Agree the design and limits before sending. A small pilot may produce too few purchases for a confident comparison, so don't dress up a handful of bookings as a precise causal result.

Read the replies as evidence about the offer. If many people ask where the workshop is, the location may be unclear. If they understand the event but can't attend either date, another reminder won't fix the schedule. Improve the specific problem before deciding that the audience needs a stronger discount or more messages.

Review one launch before making it a permanent channel

Workshop House should finish the pilot with a decision, not a promise to send every month forever. Did the eligible audience want this type of announcement? Could the team manage replies? Did additional admissions plausibly cover the complete cost? What happened to opt-outs and unresolved questions? Answer those before expanding the list or adding another campaign.

If email already reaches the same audience effectively, compare the extra work WhatsApp creates with the extra benefit you can identify. Loopyah's attendee email tools distinguish promotions from updates about booked events and provide campaign reporting. Use the channel that fits the customer's permission and the business's needs. A new inbox isn't valuable simply because you can open it.

If you adopt a Platform service for future editions, ask about its delivery route and maintenance responsibilities. Meta's Marketing Messages API overview says new Messaging accounts created from 13 April 2027 won't send marketing through Cloud API, the existing software delivery route. Its marketing support ends on 13 October 2027, with API marketing moving to the Marketing Messages API for WhatsApp. Those dates concern the technical delivery route, not permission to contact customers. Your provider should explain how it will support the service you buy.

Before the next launch, update the event facts, audience rules, eligibility check, approved message and staffing plan. Remove closed dates from scheduled messages and correct links that now point to sold-out events. Review access when staff or suppliers change. Keep the process small enough that someone can maintain it alongside delivering the event.

Write the next campaign brief using what you learned. For Workshop House, the strongest result might be that beginner buyers want early date announcements and ask few questions once materials and location are clear. It might instead be that reply handling costs too much for the additional places sold. Either finding is useful when it leads to a better decision.

Choose one confirmed event and one audience whose permission and eligibility you can verify. Assign the inbox, check the checkout, and agree the maximum total cost before sending. Use the first launch's delivery, support and sales records to decide whether the next date deserves another send, a different offer or the marketing channel you already know works.