Change or cancel a booking
template.
The Change or cancel a booking template is a ready-made Dazza workflow for moving and cancelling bookings. Dazza collects name, email, current booking and what should change, asks the customer to confirm, then sends the request to your team’s inbox. Every detail, check and message can be changed.
The questions
it answers.
Dazza uses it when the customer wants to move, change or cancel an existing booking. You can change that sentence, and Dazza follows the new one.
“Can I move my appointment to Friday?”
“I need to cancel tomorrow.”
“Can I change it to 3pm?”
“Can I add a colour to my cut?”
What it asks for.
Nothing more.
Dazza asks only for what’s missing, never for what it’s already been told, and checks emails, numbers and dates as it goes. Add, remove or reorder details, up to 10.
| DETAIL | TYPE | REQUIRED | CHOICES OR HELP |
|---|---|---|---|
| Name | Short text | Required | — |
| Required | — | ||
| Current booking | Short text | Required | Date and time |
| What should change | Long text | Required | — |
Where the job
goes next.
This template uses Send to your team. Switch to another way to finish, or add decisions that choose between them.
Send to your team
The request lands in the Team queue of your inbox with every detail, and your team gets an email.
AS IT COMESShare a link
Dazza shows a button to a page, such as your booking page or a form, with details filled into the address.
SWITCH TO IT ANY TIMECall your system
Dazza sends a signed request to your system and answers from the reply. Scale and above.
SWITCH TO IT ANY TIMEThanks. We’ll confirm the change by email.
The checks,
out of the box.
Every check runs in code before the workflow does, so none of them rely on the AI behaving. Change any of them per workflow.
| Check | As it comes |
|---|---|
| Customer confirms first | On. Dazza shows the details and waits for the customer to press Confirm. |
| Customer verifies their email first | Off. Turn it on for anything about a customer’s own account (Growth and above). |
| Team approves before it goes ahead | Off. Turn it on to have your team approve or decline each one in the inbox (Growth and above). |
| Starts in | Test, so it only runs in your preview until you set it to Live. |
| Email and messaging apps | Web chat and apps only while Confirm is on. Turn Confirm off to use it on email and messaging apps. |
| Plan | Every plan. Starter includes 3 workflows. |
Who it suits.
How to adapt it.
The groups are a guide, not a rule. Any business can use any template, renamed to fit.
Who it suits
- Salons, clinics and studios
- Restaurants and venues, renamed “Change a reservation”
- Tutors, trainers and anyone who takes bookings
Tips for adapting it
- Turn on Customer verifies their email first (Growth and above) so only the person who booked can change it.
- Put your cancellation policy in your knowledge, so Dazza explains it before it takes the request.
- If your booking system sends customers a link to manage their booking, add a decision that shares it for simple changes.
Does Dazza change the booking in our calendar?
Not by itself. Your team confirms the change. To make changes directly, switch it to Call your system (Scale and above) or connect your booking system’s tools over MCP.
How does the customer hear back?
Your team replies by email from the inbox. The customer is told that straight away.
Can people cancel on WhatsApp?
Not as it comes. It asks the customer to press Confirm. Email and messaging apps have no buttons, so Dazza only uses workflows there that don’t need one. Turn Customer confirms first off if you want Dazza to use it on email, WhatsApp and the rest.