Complete 2026 guide to WhatsApp broadcasts for UK estate agents — new-listing alerts, viewing reminders, market updates, and price-drop notifications.
Estate agents use WhatsApp broadcasts to reach segmented lists of consented contacts at scale, on the messaging channel most UK residents already use daily. The four broadcast patterns that show up across UK, US, and Australian agencies are:
1. New-listing alerts to registered searches. A buyer registers a search (area, budget, bedrooms, property type) with the agency; when a matching listing goes live, a broadcast template goes to that named-search segment. This mirrors the property-portal alert pattern (Rightmove, Zoopla, OnTheMarket, Zillow, Realtor.com), but on the channel where response rates are typically higher than email.
2. Price-drop notifications for a shortlist. A buyer flagged interest in a listing that was above budget; when the listing drops in price, a broadcast template goes to the interest-list segment.
3. Viewing reminders and confirmations. Automated utility templates fire off the CRM's viewing schedule — 24 hours before, 1 hour before, day-of confirmation. These are transactional utility templates, not marketing broadcasts.
4. Market updates to past clients. Quarterly local-market updates (sold prices, average time on market, active listings) to consented past buyers and sellers keep the agency top-of-mind for future transactions and referrals.
What broadcasts should not be used for: cold outreach to purchased or scraped lists (PECR breach and Meta Business Platform violation), broadcasts to recipients whose only prior contact was a portal enquiry without a separate WhatsApp opt-in, or as a substitute for the one-to-one negotiation conversations that are the agent's actual work.
The channel earns its keep when it's used to notify already-consented segments about property information they've asked to hear about — not as a spray channel.
Content types that consistently work in the estate-agent broadcast mix:
New-listing alert. Hero photo + one line on the property (bedrooms, area, price band) + link to full listing or virtual tour. Keep it under a screen-height on a phone — buyers scan on the go.
Price-drop alert. Address (or masked address for privacy), previous price, new price, link. Send to the interest segment that flagged the listing, not the whole list.
Open-house / viewing-day announcement. Property, date, time slots, RSVP link. Common for US brokerages running Sunday open-house tours.
Under-offer / sold-STC notification (past-clients segment). Confirms the market is moving in the area — useful for prospective sellers.
Local-market update (quarterly). Average sold price, average time on market, active listings, one-line takeaway. Link to full report on the agency's site.
Landlord-focused broadcasts (lettings). Tenancy-renewal reminders, rent-review windows, regulatory changes (in the UK: EPC MEES rules, right-to-rent, selective licensing, Renters Rights Bill updates).
Buyer-education content (registered-buyers segment). First-time-buyer schemes, current mortgage rate environment, stamp-duty guidance. In the UK the Stamp Duty Land Tax rates and thresholds change from time to time — do not embed specific SDLT figures in an evergreen template; link to the GOV.UK page which is the authoritative source.
Rich media. WhatsApp handles photos, PDF brochures, video walkthroughs, and virtual-tour links (Matterport, iGuide, Zillow 3D Home) natively. Video and photo attachments raise attention on the recipient side; templates that carry a hero image typically outperform text-only in practice, but attention on the screen is not the same as a viewing booking — measure to the booked-viewing conversion, not the message-open.
What does not belong in a broadcast: personal negotiation on offer level, mortgage-affordability discussion (individual context matters), or any communication touching on protected characteristics that could be construed as discriminatory selection of the recipient pool. On the last point, US agents in particular must be mindful of Fair Housing Act constraints — segmentation criteria for broadcasts must be based on stated search preferences and prior interaction, not on protected-class inference.
Cost is a sum of the WhatsApp Business Platform vendor subscription and Meta's per-template message price since 1 July 2025.
Vendor subscription. Typical tiers across the credible vendors in this market:
- Small-agent tier (1-3 users, basic template management, single team inbox): USD 30-80 per month
- Mid-market tier (5-15 users, workflow automation, richer analytics, CRM integration): USD 100-300 per month
- Enterprise tier (unlimited users, SLA, custom integration): USD 500-2000+ per month
Exact figures vary by vendor — always confirm on the current vendor pricing page.
Meta per-template pricing since 1 July 2025. Per Meta's WhatsApp Business Platform pricing:
- Marketing templates (new-listing alerts, price-drop alerts, market updates, open-house invites) — priced at the country's marketing rate per delivered template.
- Utility templates (viewing confirmations, viewing reminders, listing-status updates, tenancy-renewal reminders) — priced at the country's lower utility rate per delivered template.
- Authentication templates — priced separately.
- Replies from the buyer or seller inside a 24-hour service window remain free — so the reply flow that follows a broadcast doesn't add per-message cost.
Country rates differ by rate zone; the UK and US both sit in Meta's mid-band. For UK / US, per-template cost is typically low single-digit US cents per template for utility and higher single-digit or low-double-digit US cents for marketing (varies by conversation category rules — check the current pricing table before budgeting).
Realistic monthly cost for a small independent UK agency (single office, 2-3 agents, 200-500 conversations per month, one weekly listing-alert broadcast to a ~200-recipient registered-search list, viewing reminder / confirmation templates): vendor subscription USD 30-100 + Meta template line USD 20-80 = approximately USD 50-180 per month total.
Realistic monthly cost for a mid-size agency (multiple offices, 10-20 agents, 2,000-5,000 conversations per month, daily new-listing broadcasts segmented across 5-10 saved-search groups): vendor subscription USD 200-500 + Meta template line USD 100-400 = approximately USD 300-900 per month total.
Real-estate CRM subscriptions (kvCORE, Follow Up Boss, Chime, HubSpot Real Estate, LionDesk, Salesforce Real Estate Cloud) are separate. A WhatsApp Business Platform is added to, not instead of, the agency's CRM.
Six steps take an agency from zero to a working broadcast flow:
Step 1 — Meta Business account and Business Verification. Sign up for a Meta Business account and complete Meta Business Verification. Verification requires company-registration proof, business address, and contact details, and typically completes in a few working days. Business Verification is required before templates can be sent at scale.
Step 2 — Choose a WhatsApp Business Solution Provider (BSP). Credible BSP options include Wati, Respond.io, SleekFlow, Bird (formerly MessageBird), Twilio, 360dialog, and BossBot at the SMB tier. Choose based on: does it integrate with the real-estate CRM the agency uses, does the pricing model fit the volume, is the shared inbox usable by multiple team members, does the vendor sign a UK-GDPR-compliant data-processing agreement.
Step 3 — Register the business phone number. Register a dedicated business phone number with Meta through the chosen BSP. This must be different from any number in use on the consumer WhatsApp Business app — a number can only sit on one product at a time.
Step 4 — Design and submit broadcast templates for approval. Draft the templates the agency will use (new-listing alert, price-drop alert, viewing confirmation, viewing reminder, market update) and submit via the BSP dashboard. Meta reviews and approves per template — usually hours to a couple of days. Categorise correctly: marketing templates for broadcasts to registered buyers / past clients, utility templates for viewing confirmations and reminders. Every marketing template must include an opt-out mechanism.
Step 5 — Integrate with the real-estate CRM. Connect the WhatsApp Business Platform to the agency's CRM so that: portal-forwarded enquiries land in the CRM as leads, viewing bookings trigger utility templates automatically, price-drop events on the CRM's listing record fan out to the interest segment. Most BSPs offer native integrations to the common estate-agent CRMs or a Zapier / Make bridge.
Step 6 — Set up PECR-compliant consent capture at lead entry. For any marketing broadcast (new-listing alerts, price-drop alerts, market updates), capture PECR Regulation 22 consent at the point the buyer / seller registers. Record consent per lead with timestamp, channel-specific scope ('WhatsApp'), and the exact consent statement text. Every marketing broadcast must carry an opt-out (typically 'Reply STOP to unsubscribe') and opt-outs must be processed immediately.
Total setup time: usually 1-2 weeks including Meta Business Verification and initial template approval. Faster if the CRM integration is native to the BSP.
Yes, when set up correctly. The compliance work sits with the estate agency (as data controller), not the WhatsApp platform vendor. Key points:
PECR Regulation 22 — direct marketing to individuals by electronic mail. Per the ICO's guidance on direct marketing and PECR, any marketing WhatsApp broadcast (new-listing alert, price-drop, market update, open-house invite) to an individual subscriber requires prior consent that is: specific to the WhatsApp channel and purpose, freely given, informed, evidenced per recipient, and revocable via a working opt-out on every message. PECR treats WhatsApp broadcasts the same way it treats SMS and email — the medium doesn't change the consent rule.
PECR soft opt-in under Regulation 22(3). Where a buyer or seller previously bought or negotiated with the agency (a genuine prior transaction, not a lead form), the soft opt-in allows the agency to market 'similar products or services' by electronic mail without separate opt-in, provided: contact details were collected in the course of the sale, an opt-out was offered at the point of collection, and each subsequent message includes a simple opt-out. The soft opt-in is narrower than many agencies assume — a portal enquiry that never became a transaction does not qualify.
Penalty exposure. The Data (Use and Access) Act 2025 raised the PECR fine cap from £500,000 to £17.5m or 4% of global turnover — bringing PECR penalty exposure into line with UK GDPR. This raises the stakes for the sector on non-compliant marketing broadcasts.
UK GDPR lawful basis. For inbound property enquiries and transactional messages (viewing confirmations, viewing reminders, offer updates), UK GDPR Article 6(1)(b) — necessary for taking steps at the request of the data subject prior to entering into a contract — is the usual lawful basis. This covers the transactional utility templates. Marketing broadcasts sit on the PECR consent basis in addition.
Data-processing agreement with the BSP. The chosen WhatsApp Business Platform vendor is a processor under UK GDPR. The agency needs a written data-processing agreement covering Article 28 requirements — instruction-only processing, security measures, breach notification, sub-processor management, and safeguards for any international transfer of the CRM / message-log data (Standard Contractual Clauses or an approved adequacy framework, depending on where the vendor hosts).
AML records (UK). UK estate agents are supervised by HMRC for anti-money-laundering purposes under the Money Laundering Regulations 2017. Customer due-diligence records must be kept for 5 years after transaction completion. Broadcast opt-in logs are separate from AML records but both are retained on the CRM side.
Right-to-rent (UK lettings). Lettings agents conducting right-to-rent checks capture immigration documentation — this is not something to store in WhatsApp threads long-term. Route documentation to the agency's secure document-storage system after capture.
US agents. State-level privacy laws (California CCPA/CPRA, Virginia CDPA, Colorado CPA, Connecticut CTDPA, and others) apply to broadcast opt-in and data handling. The federal Telephone Consumer Protection Act (TCPA) governs marketing text-message consent. The Fair Housing Act constrains any bot-driven interaction or broadcast segmentation that could be construed as discriminatory — segmentation criteria must be based on stated search preferences and prior interaction, never on protected-class inference.
The free WhatsApp Business app and the paid WhatsApp Business Platform (via a BSP) serve different scales.
Use the free WhatsApp Business app if: you are a solo agent with under a few hundred contacts, your recipients have your number saved in their address book, your broadcast list stays under 256 recipients (the app's per-list cap), and you do not need CRM integration or a shared inbox. The app is workable for the smallest solo operation.
Use the WhatsApp Business Platform (paid, via a BSP) if: you have multiple agents needing a shared inbox, your broadcast list is over 256 recipients, you want segmented broadcasts driven by CRM data (saved searches, price bands, past-client status), you want utility templates to fire automatically off CRM events (viewing booked → confirmation, viewing tomorrow → reminder), or you need reporting on delivery / template performance. This is the scale where the paid subscription earns itself back.
Do not mix the two on the same phone number. Once a number is registered on the Business Platform, it cannot simultaneously be used on the consumer WhatsApp Business app. Pick one product per business phone line.
Most UK agencies with more than one agent land on the Business Platform once broadcast volume goes past a handful of recipients per message.
The segmentation that reliably works is anchored on stated buyer / seller preferences and prior interaction, held in the CRM:
Registered-search segments. Buyers who registered a search (area + price band + property type + bedrooms) receive matching new-listing alerts. Each registered search is a segment. If a listing matches five saved searches, it fans out to five segments — sized correctly, not the whole list.
Interest-list segments per listing. Buyers who requested more info, saved the listing, or booked a viewing on a specific property go on that listing's interest list. Broadcasts on price drops, under-offer status, and final-viewings notice go to the interest list.
Landlord segment (lettings). Landlords with active tenancies receive tenancy-renewal reminders (utility) and regulatory-change updates (marketing).
Past-client segments. Past buyers and past sellers receive quarterly market updates (marketing), tied to the postcode area they transacted in. These segments compound over time — the past-client list is often the agency's highest-retention marketing channel by year three.
Do not broadcast to: portal enquiries without a separate WhatsApp opt-in captured, contact lists purchased from a third party, WhatsApp groups where members haven't specifically opted in to marketing from the agency, or recipients who previously opted out of any of the agency's marketing channels.
Good segmentation isn't just a compliance play — it also improves the response rate on each broadcast, since recipients see property information genuinely matching what they asked for.
Data + numbers referenced in this article are sourced from these public documents:
Product page with honest feature list, "not for you if" filter, and live demo for this vertical.
See /for/real-estate →BossBot is one of several WhatsApp Business Platform tools available to UK estate agents. For a small-to-mid agency shortlisting vendors, compare BossBot against Wati, Respond.io, SleekFlow, Bird, and Twilio on real-estate CRM integration, shared inbox, template management, and UK-GDPR data-processing agreement. The PECR consent record, the AML documentation, and the Fair Housing / equalities compliance stay with the agency.
Explore BossBot for real estateNot ready to sign up yet? Try the free demo →