The quote is the sale
For birthday parties, groups, events and packages, most of the people who write to you are not ready to book.
Mushon Nachmani
vGuest
For birthday parties, groups, events and packages, most of the people who write to you are not ready to book.
They want a price they can show someone else: a partner, a parent, a committee, a finance manager. Until they have that, there is nothing for them to decide.
Most chat flows are built the other way round: a booking form with a chat wrapper, asking for date, time, headcount, extras and payment. That works for a room night. It does not work for a party that four people have to agree on.
One attraction looked at where its chat enquiries actually went and found that most of its chat inquiries were quote requests, yet its flow tried to collect every booking detail up front. People dropped off. Not because they were not interested, but because they were being asked to make decisions they had not made yet.
That is worth checking in your own business. Pull last month's chat enquiries and count how many were asking "how much?" rather than "can I book?". The split will tell you what your chat is actually for.
Collect the minimum
Ask only what you need to send the right quote. Nothing else.
For one business that was just the branch. Price varied by site. Everything else (date, headcount, add-ons) could be settled once the quote was in the customer's hands.
Do the exercise properly. Put your price list in front of you and go through it field by field, asking one question: does this change the number? If it does not change the number, it does not belong before the quote.
Typical answers:
- Branch or venue. Usually yes.
- Package or product. Usually yes.
- Headcount. Only if you price in bands, and then the band is enough. "10 to 20 children" prices fine. You do not need an exact figure from someone who has not sent the invitations.
- Date. Only if you have peak and off-peak rates, and then the month is enough.
- Names, email addresses, dietary requirements, the child's age. No. All of that comes after someone decides to go ahead.
Most flows ask a long list of questions before a price appears. Most could ask one or two.
Make the quote do the selling
- Send a clear PDF quote with photos and a video. The quote gets forwarded, screenshotted and argued over in a family group. A document survives that journey; a chat thread does not.
- Keep prices in the quote, not scattered through the chat. If the price is spread over five messages, the customer has to reassemble it, and the version they remember is usually wrong. One document, one total, one list of what is included and what is not.
- Ask "what date and time would you like to celebrate?" instead of "when is the birthday?" The second asks for a fact about the calendar. The first asks them to choose a slot from you. Small change, different conversation.
And give the quote a next step. A quote that ends with a total gets filed. A quote that ends with "reply here with a date and we will hold it for you" gets replied to. And if you sell those packages as vouchers, what the guest does with the voucher later is a conversation of its own.
Follow up once, at the right time
Send one friendly message at 9:00 the next working morning (for example, no messages on Shabbat): "Hi, we're here for any question. Whenever you want to pick a date, just continue this chat."
No hard sell, and no repeated chasing.
There is a mechanical detail worth getting right. Meta's documentation is plain about it: "When a WhatsApp user messages you or calls you, a 24-hour timer called a customer service window starts", and "When the window closes, you can only send pre-approved template messages" (Send messages, Meta for Developers, read 28 September 2026).
Your 9:00 follow-up will usually fall outside that window. Someone who enquires at 14:00 on Thursday is well past 24 hours by Monday morning if you do not message at the weekend. So write that follow-up as a message template and have it approved before you need it. Templates "must have a status of `APPROVED` before they can be sent in template messages" (Message templates, Meta for Developers, read 28 September 2026).
Two edge cases:
- The enquiry came in late last night. The window is still open, so a normal message works. Build the rule as "template if the window has closed", not "template always".
- They reply to your follow-up. The window reopens and you are back to ordinary conversation. That is the point of the follow-up. Not to sell, but to reopen the door.
And then stop. One follow-up is service. The third one is chasing, and on WhatsApp it is chasing you pay for, since marketing templates are billed per delivered message (WhatsApp Business Platform pricing, Meta for Developers, read 28 September 2026).
For groups
Groups are a different animal. Collect the basics (group name, contact person, phone, email, adults and children, type of group, preferred date), open a request for your sales team, and move the detailed quote to email.
That is not a step backwards. Group bookings involve attachments, terms, invoicing details and more than one recipient. Email carries that. Keep the WhatsApp thread alive as the fast lane for questions.
What to do on Monday
- Count last month's enquiries: quote requests versus booking requests.
- Delete every pre-quote question that does not change the price.
- Build one good PDF quote per package, with photos and a video.
- Write and submit the follow-up template.
- Write down your quiet hours and days, and the single follow-up rule.
Takeaway
If most people come for a quote, design your chat around the quote and the follow-up, not the booking form.
Common questions
What should a chat flow ask before it sends a quote?
Only the things that change the number. Put your price list in front of you and go through it field by field asking whether that field moves the price. Branch or venue usually does. Package usually does. Headcount only if you price in bands, and then the band is enough. Date only if you have peak and off-peak rates, and then the month is enough. Names, email addresses, dietary requirements and ages come after someone decides to go ahead.
Why do booking-form chat flows lose party and group enquiries?
Because the people writing in are not ready to book. They want a price they can show a partner, a parent, a committee or a finance manager, and a flow that asks for date, time, headcount, extras and payment up front is asking them to make decisions they have not made yet. That works for a room night. It does not work for a party four people have to agree on.
What should a quote for a party or group package include?
Send a clear PDF with photos and a video, because the quote gets forwarded, screenshotted and argued over in a family group, and a document survives that journey where a chat thread does not. Keep the prices in the document rather than scattered across five messages, with one total and one list of what is included and what is not, and end it with a next step such as replying with a date to hold.
Do you need an approved template to follow up a WhatsApp enquiry?
Usually yes. Meta's documentation states that a 24-hour customer service window starts when a WhatsApp user messages you or calls you, and that once the window closes you can only send pre-approved template messages, which must have a status of APPROVED before they can be sent. A follow-up at 09:00 the next working morning will often fall outside the window, so write it as a template and have it approved before you need it.
How many times should you follow up on a quote?
Once. One friendly message at 09:00 the next working morning, with no hard sell, is service. The third is chasing, and on WhatsApp it is chasing you pay for, since marketing templates are billed per delivered message. If the customer replies, the customer service window reopens and you are back to an ordinary conversation, which is the whole point of the follow-up.
Keep reading
All articles190+ properties · 6 countries
See it answering your guests
Bring your own property. We will show you what the assistant does with your real questions, in your languages, on WhatsApp.
