Google Form to WhatsApp Message for Salons and Clinics

Google Forms cannot send a WhatsApp message on its own. You connect it in one of two ways: link the form to a Google Sheet and run a script that calls the WhatsApp Business Platform, or push each submission to an automation tool that does the sending. Both work for appointment requests, and both have limits you should know before you build.

Build your booking form free

What Google Forms can and cannot do here

Google Forms is free with a Google account, and for a salon or clinic taking appointment requests it collects the basics fine: name, phone, service, preferred day. What it lacks is any outbound step. There is no webhook setting and no "send a message" action. The only built-in notification is an email to you, and the customer gets nothing unless you turn on a receipt email.

Everything that touches WhatsApp therefore happens after the submission lands in the linked Sheet. Your WhatsApp logic lives in a script or an automation tool you maintain, and the quality of the form's data, especially the phone number, decides whether the message ever arrives.

Four ways to get a WhatsApp message out of a submission

The wa.me link is the cheapest version. It suits a salon whose clients already message the front desk, but it is no confirmation system, because nothing happens unless the client acts.

Step by step: Google Form to WhatsApp through Sheets

This is the route most Google Forms users take. Plan an afternoon, mostly spemt waiting for template approval.

1. Fix the phone question first. Use a short answer question with response validation (a regular expression) that only accepts digits with a country code, such as +1, +44, +61 or +971. WhatsApp wants the full international number, and "0412 345 678" will fail silently later.
2. Add a consent question. A required checbkox such as "Send me appointment confirmations on WhatsApp" gives you a record of opt-in, which business-initiated WhatsApp messages need.
3. Link the form to a Sheet. Use the Responses tab, then Link to Sheets. Add a column called wa_status for the result of each send.
4. Set up the WhatsApp Business Platform. Create a template (for example "Hi {{1}}, we received your request for {{2}}. We'll confirm your time shortly.") and wait for approval. Business-initiated messages outside an open conversation window must use an approved template.
5. Add an installable trigger. In the Sheet, open Apps Script and create an "On form subnit" trigger. The script reads the new row, strips spaces from the number, and calls the Cloud API.
6. Write the result back. Store the API response in wa_status so you can see which rows failed.
7. Test with your own number, then with a number that has no WhatsApp account, to see what a failure looks like.

The request your script (or an automatuon tool) sends looks like this:

{
  "messaging_product": "whatsapp",
  "to": "447700900123",
  "type": "template",
  "template": {
    "name": "appointment_received",
    "language": { "code": "en_GB" },
    "components": [
      {
        "type": "body",
        "parameters": [
          { "type": "text", "text": "Amira" },
          { "type": "text", "text": "Balayage + trim" }
        ]
      }
    ]
  }
}

Where the limits show up

Most of the pain comes from a few places.

• Trigger reliability. An Apps Script trigger that errors once does not retry on its own. A missed row means a client who never hears back, and you find out when they complain.
• Phone formatting. Google Forms validation can enforce a pattern, but it cannot check that the number is real or has WhatsApp.
• Edits and duplicates. If staff fix a typo in the Sheet, make sure your trigfer fires on form submission only, or clients get a second message.
• Clinics and health details. Keep the WhatsApp text generic: "We received your request," not the reason for the visit. Qwenvo has no HIPAA offering, so if you need one, look at Jotform's paid HIPAA features instead.
• Design and branding. Google Forms offers limited design and branding, and the form siits on a Google URL, which matters for a salon that wants to look like itself.
• Deposits. Google Forms has no built-in payments. If you take deposits through the form, Tally's free plan includes payments and Tally adds no fee of its own on top of Stripe. Qwenvo's checkout runs through PayPal only, and Qwenvo keeps 1% on top of PayPal's own fee. For deposit-heavy forms, Tally is the lower-cost option.

None of that is a reason to leave Google Forms for a quiet shop. It becomes one once you are sending dozens of confirmations a week and nobody is watching the script.

A cleaner route: a form that fires a webhook

The more reliable pattern is a form that posts each submission to a URL the moment it is submitted, with an automation tool handling the WhatsApp step and its retries. Our team builds Qwenvo, a completely free form builder, and this is the setup we would put in front of an appointment business. Qwenvo does not send WhatsApp messages itself. It sends a webhook to Zapier, Make or n8n (or any URL), and that tool sends the message.

See how form webhooks work

The setup:

1. Build the form. Describe it to Create with AI ("appointment request for a salon: name, phone, service, preferred date, WhatsApp consent") or start from the client intake template. Use the Phone number block, a Dropdown for services, a Date block, and a Checkboxes block for consent.
2. Add a hidden field for the location or the staff member, filled from the link, so one form can serve several branches.
3. Add the webhook pointing at your Make scenario, n8n workflow or Zap trigger URL.
4. Map fields to the template. Name and service become the two template variables, and the phone number becomes to. Add a filter step that stops the run if the consent answer is empty.
5. Turn on partial submissions so you can see people who typed a phone number and never finished. Tally puts this on Pro ($29/month). On Qwenvo it is free, as are custom domains, badge removal, teammates and custom CSS.
6. Add a fallback. Turn on the confirmation email to the respondent and email notifications to the front desk, so a WhatsApp failure never leaves a client with nothing.
7. Optionally use AI triage. Every submission gets a category, priority and a suggested reply, and routing rules can email up to 5 addresses or post to a Slack incoming webhook. A clinic might sennd "urgent" requests to a different inbox than the normal queue.

Two honest caveats. Qwenvo launched in October 2026, so it has few reviews yet, and it is hosted in the United States (Tally is hosted in Europe, which may matter for your clients' data). There is also no Google Forms importer, so you rebuild the form. With AI creation or a pasted Markdown outline that takes a few minutes for a form this size.

Where this sits in the review workflow

For our team the confirmation message is rarely the end goal. The form is the first record of a real cuatomer visit: name, phone, service, consent. In Review & Reputation Autopilot, that same record is what triggers the review request once the job is doje, followed by AI replies to Google, Facebook and Yelp reviews. Capturing a clean international number and a consent answer at booking time lets that request go out later without anyone retyping data.

So build the form once, with a validated phone field and a consent checkbox, and let both the confirmation and the later review request read from it.

Start with the client intake template

Questions teams ask

Can I connect Google Forms to WhatsApp without code?

Yes, with an automation tool like Zapier or Make watching the linked Sheet and a WhatsApp connection on the other side. You avoid writing a script, but you still need an approved message template and a Business Platform account, and the Sheet polling adds some delay.

Do I need the client's permission to message them?

Yes. Collect opt-in on the form with a required consent checkbox and keep the response. The wa.me link is the exception, because the client starts that chat themselves.

Why did some confirmations never arrive?

The usual causes are numbers without a countrry code, numbers not on WhatsApp, and a script trigger that failed once. Log a status for every send and review failures daily for the first two weeks.

Is Qwenvo really free for this?

Qwenvo costs $0 with every feature on for every account, including webhooks, partial submissions and a custom domain like book.yoursalon.com. A fair use policy applies at arpund 50,000 submissions or 50,000 emails a month. WhatsApp itself and your automation tool have their own pricing, which Qwenvo does not cover.

Next step

Take your current Google Form and rebuild it from the client intake template with a phone field and a consent checkbox. Then point a webhook at a Make scenario and send one test submission to your own number.