The moment it happens

Send a WhatsApp confirmation when someone books

Each new booking or sign-up gets your approved template on WhatsApp with their name and details filled in.

Runs: The moment it happens
Apps: WhatsApp Business
AI: Not needed
Access: whatsapp_business_messaging

Send this to your assistant

Create a ClickRuntime automation: give me a link my booking tool can post to; for each booking, send the customer our 'booking_confirmed' WhatsApp template with their first name, date and time.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

A yoga studio takes a booking through its scheduling tool, a webinar host gets a new registration, a shop gets a subscriber. The person has just acted and is paying attention, and that is the best moment to confirm. Instead the confirmation email lands in a promotions tab, or nothing is sent until an assistant gets around to typing a message that evening. By then the booking feels less certain and no-shows rise.

When your booking or sign-up tool fires a webhook, the automation receives the event, cleans up the phone number into the international format WhatsApp needs, and sends an approved WhatsApp template with the person's name and details filled in. It then logs delivery from the statuses that WhatsApp reports back, so you can see whether it arrived.

It suits any business whose tools can send an event when a customer books, subscribes or buys.

What you get out of it

Confirmation lands while attention is high
A WhatsApp message seconds after booking is read almost immediately, so the customer sees the date and place at the very moment they are thinking about it, and mistakes get corrected early.
Fewer no-shows from forgotten bookings
People who receive a clear personal message on the app they use all day are more likely to turn up or to cancel in time. An empty slot you can resell beats a silent no-show.
Phone numbers fixed before sending
Customers type numbers with spaces, brackets or a leading zero. Normalizing them into one international format stops sends from failing for avoidable reasons and saves chasing the customer for a correct number.
Delivery log shows what happened
Status events are recorded for each message, so when a customer claims they never heard from you, you can check whether it was sent, delivered or read, and respond with facts.
No staff member tied to the task
Nobody has to remember to message each new booking by hand. The same quality of message goes out at midnight on Saturday as on a quiet Tuesday morning. A booking made at 2 a.m. gets the same prompt confirmation as one made during opening hours, with no extra staffing.

How it works

What happens, step by step

When someone books or signs up in your booking tool, it tells ClickRuntime straight away.
ClickRuntime tidies up their phone number so WhatsApp accepts it.
It sends your approved WhatsApp template with their name and booking details filled in, such as "Hi Sam, your table is booked for Fri 24 Oct, 19:30".

Before it runs live

Connect WhatsApp Business
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

Send a WhatsApp confirmation when someone booksjust nowSucceeded

WhatsApp · booking_confirmedHi Sam, your table at Northwind Bistro is booked for Fri 24 Oct, 19:30. Reply to change it.

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Act only on the items that match your own rules, and skip the rest
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other WhatsApp Business steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

send_a_whatsapp_template_when_an_event_webhook_arrives.pyexample

import re
from clickruntime import on_event, credentials, http, log

PHONE_NUMBER_ID = "123456789012345"
COUNTRY_CODE = "44"

@on_event
def handle(event):
    body = event.json
    if "entry" in body:  # delivery status from WhatsApp
        for s in body["entry"][0]["changes"][0]["value"].get("statuses", []):
            log.info("status", {"id": s["id"], "status": s["status"]})
        return {"status_logged": True}
    phone = re.sub(r"\D", "", body["phone"])
    if phone.startswith("0"):
        phone = COUNTRY_CODE + phone[1:]
    res = http.post(f"https://graph.facebook.com/v21.0/{PHONE_NUMBER_ID}/messages",
                    headers={"Authorization": f"Bearer {credentials.secret('WHATSAPP_TOKEN')}"},
                    json={"messaging_product": "whatsapp", "to": phone, "type": "template", "template": {
                        "name": "booking_confirmed", "language": {"code": "en"},
                        "components": [{"type": "body", "parameters": [
                            {"type": "text", "text": body["name"]}, {"type": "text", "text": body["when"]}]}]}}).json()
    return {"message_id": res["messages"][0]["id"]}

FAQ

Common questions

Which tools can trigger this?

Anything that can send a webhook when something happens, such as booking systems, form tools, ecommerce platforms and payment services. The automation reads whatever fields the event carries, so name and phone number must be included in the payload.

What if the phone number in the event is invalid?

The send will fail and WhatsApp returns an error, which is recorded in the delivery log. Normalizing removes common formatting problems, but a number that is genuinely wrong cannot be fixed, so the log tells you whom to contact another way.

Does the customer need to have messaged me first?

No. Because the template is approved by WhatsApp, a business can start the conversation with it. The customer should have agreed to receive messages, usually through a consent tick at sign-up, which WhatsApp's policy requires.

What permissions does it need?

whatsapp_business_messaging. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run for each event the app sends.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

The moment it happens