WhatsApp Chatbot for UK Event Planners: Lead Qualification, Deposit

A Leeds wedding planner, Thursday 6:48pm — the February bride who booked somewhere else

On a Thursday evening in October 2024, a freelance wedding planner in Leeds was on-site managing a wedding reception until 11pm. Three WhatsApp enquiries came in to her business number during the evening.

The first was a bride asking about availability for February 2026 — a tight timeline for a wedding planner, which usually signals either a firm decision or a cancelled date. The message included a budget range (£8,000-12,000 for coordination), a venue already confirmed in North Yorkshire, and a guest count of 65. This was a qualified lead.

She saw it at 11:47pm. She replied at 9:15am Friday. The bride replied at 9:41am to say she'd booked another planner on Thursday evening who'd responded quickly.

Bridebook's 2024 UK report data shows that UK couples contact an average of 3.2 wedding suppliers per category before booking. First-to-respond advantage in the event planning sector is significant: a planner who acknowledges an enquiry within 30 minutes — even with an automated 'I'll be in touch by 9am tomorrow, here are a few questions to help me prepare' message — keeps the lead engaged. A planner who is silent until the next morning does not.

The five qualifying questions that WhatsApp chatbot sends automatically: (1) What's your event date or date range? (2) How many guests? (3) Do you have a venue confirmed? (4) What's your total event budget? (5) Which element matters most — catering, entertainment, styling, or logistics? The answers arrive before the discovery call. Unqualified enquiries (no date, no budget) self-select out. Serious clients feel attended to before they've spoken to a human.

Three WhatsApp flows that change how a UK event planner manages enquiries

UK event planners using WhatsApp automation consistently use three flows:

Initial enquiry qualification (the pre-discovery call brief). When a new enquiry arrives — from the planner's website contact form, Instagram DM referral, or direct WhatsApp message — an automated chatbot sends the five qualifying questions immediately. The prospect's answers create a brief that the planner reads before calling. Discovery calls that start with a brief run 20-30 minutes instead of 45-60, and the planner can decline clearly unsuitable enquiries by message rather than after a wasted call.

Deposit request and contract link. Once a client has verbally agreed to proceed, the WhatsApp flow sends: (1) a Stripe payment link for the deposit (typically 25-50% of the total fee), (2) a DocuSign or PandaDoc contract link, and (3) a short message confirming that the booking is secured once both are completed. This replaces email chasing and the 'I'll get round to signing the contract' drift that delays commitment. For UK event planners, the contract must include Consumer Contracts Regulations language if signed at a distance (see section 3).

Day-of logistics broadcast to vendors and guests. On the day of the event — or the evening before — a WhatsApp broadcast to the vendor group (caterer, photographer, florist, band, venue coordinator) with the final running order, delivery slot times, and contact numbers for the day. A separate broadcast to guests with parking information, start time, dress code reminder, and the event WhatsApp number for the day. This reduces the planner's inbound call volume on the day itself from 15-20 'what time should we arrive?' queries to 2-3.

UK Consumer Contracts Regulations 2013 and deposits collected via WhatsApp

When a UK event planner takes a deposit via WhatsApp — sending a Stripe payment link and a contract link remotely — the transaction is governed by the Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013. Under Regulation 29, services sold at a distance (which includes a contract agreed via WhatsApp message and signed electronically without a face-to-face meeting) carry a 14-day cancellation right.

For event planners, this creates a specific structure requirement. If the planner wants to begin work immediately (booking vendors, holding date with a venue) within the 14-day cooling-off period, the client must: (a) explicitly request that the service begin within the cancellation period, and (b) acknowledge in writing that they lose their right to cancel once the service has been fully performed. In practice, UK event planners handle this with a specific clause in the contract: 'You request that services commence immediately on signing. You acknowledge that once services have been fully performed, you will have no right to cancel.'

For deposits specifically: UK law does not mandate a fixed deposit percentage. Best practice for event planners is 25-50%. If the client cancels within 14 days before the services have commenced, they are entitled to a full refund. If they cancel after services have commenced under the express commencement request, the planner is entitled to reasonable compensation proportionate to services delivered. The WhatsApp thread serves as a useful evidence record in the event of a dispute — both the payment request and the client's confirmation of receipt create a timestamped paper trail.

UK event management software and the WhatsApp integration gap

The event planning software landscape used by UK planners includes HoneyBook, Aisle Planner, 17hats, Planning Pod, and Dubsado — all of which are US-headquartered products with international pricing in USD. None have native WhatsApp integration as of 2026.

HoneyBook (the most widely used among UK freelance planners) handles contracts, invoicing, project timelines, and client portals. Its automation features cover email sequences and payment reminders but not WhatsApp. Dubsado has similar functionality. Aisle Planner is focused on wedding-specific workflow (seating, guest management, vendor tracking) but has no messaging integration beyond email.

The integration path: WhatsApp Business API via BSP (WATI from £45/mo, AiSensy from approximately £15/mo) → Zapier → HoneyBook or Dubsado webhook (both support Zapier). An enquiry form submission in HoneyBook can trigger a WhatsApp template send within 60 seconds. A contract signed via HoneyBook can trigger a WhatsApp confirmation message with the invoice link. This is the typical setup for a UK freelance event planner operating solo or with one assistant.

For the day-of broadcast to vendors, the integration is simpler: a WhatsApp Business API template broadcast sent manually via the BSP dashboard, using the final running order as the message content. No integration needed — the planner sends it directly from the BSP at 9pm the evening before.

UK GDPR and special category data in event planning — what dietary and health data requires

Event planners routinely collect dietary requirements from guests — vegetarian, vegan, nut allergy, coeliac, halal, kosher. Under UK GDPR, allergy information that indicates a health condition (coeliac disease, severe nut allergy, religious dietary law) may constitute special category data under Article 9, depending on the specificity. The ICO's guidance treats this on a spectrum: 'vegetarian' is typically not special category data; 'severe nut allergy requiring EpiPen' is health data and subject to additional protection.

For event planners collecting dietary data via WhatsApp — either through a chatbot flow or a manual question — the UK GDPR implications are:

1. Purpose limitation: dietary data collected for catering cannot be used for marketing. It should be deleted after the event.
2. Data minimisation: collect only what the caterer needs. 'Please list any dietary requirements' is appropriate; asking for specific medical diagnosis is not.
3. Security: WhatsApp messages are end-to-end encrypted, but event planners often share dietary lists with caterers via screenshot or forward. This transfer must be handled securely — the shared document should ideally be anonymised (Guest A: nut allergy) rather than named where possible.
4. Retention: dietary and health data should be deleted within 30 days of the event, not stored indefinitely in the WhatsApp thread or CRM.

For guest communication generally: UK PECR requires opt-in consent for WhatsApp marketing. A guest attending an event has not consented to future marketing communications — their attendance data cannot be used for a post-event promotional broadcast without a separate opt-in.