Customer
Match the person to the reservation.
Capture the booking name and contact used at checkout, plus a current reply address.
- Full booking name.
- Booking email and phone.
- Preferred follow-up method.
Describe your service, policy, and lookup details. Makeform turns the brief into a form customers can use to explain the request and choose a next step.
Route cancellation requests to email, Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt its policy and fields, then send it to the builder.
Audience
Salon clients cancelling an existing appointment
Format
Short request with service and stylist lookup
Prompt size
259 chars
Example form structure
Short request with service and stylist lookup
Client name and booking contact
Appointment date, time, and service
Booking reference
Why are you cancelling?
Would you like to reschedule?
Suggested routing tags
Needs review
Reschedule requested
Cancellation processed
Ask for the booking reference and the email or phone used to book. Staff need both to find records when a customer mistypes one identifier.
Step 1
Identify
booking reference, customer, and scheduled time
Step 2
Explain
reason, affected guests, and supporting notes
Step 3
Choose
cancel, reschedule, credit, or call back
Step 4
Review
staff verifies the booking and confirms the outcome
A cleaner cancellation queue
A structured form ties the customer, booking, timing, reason, and desired next step together.
Require the reference and booking contact, with the date and service as cross-checks.
Show guest counts for partial cancellations and new dates for rescheduling.
Tag requests for review, rescheduling, or follow-up so staff know what to do.
Useful across services
Change the lookup fields, reasons, and policy language to match your operation.
Match the client to a stylist, treatment, appointment time, and booking contact, with an optional rescheduling path.
Distinguish a full cancellation from selected guests leaving a group reservation, then capture the updated party size.
Identify the instructor and class time, release the place, and ask whether another session would work.
Collect the service address, arrival window, job type, and whether the customer still needs a later visit or a call.
Build the workflow
Define what staff must find and decide, then tune the form's conditions and routing.
List what customers book, identifiers, policy, and who handles changes.
Add services and reasons. Reveal dates, guest counts, or notes only when needed.
Send the reference, appointment time, and urgency to booking staff.
Test full, partial, and rescheduling paths, including confirmation and handoff.
Form vs email vs phone
Compare how each channel captures the booking and requested outcome.
Field guide
These six sections reduce lookup errors, clarify scope, and expose the next action.
Customer
Capture the booking name and contact used at checkout, plus a current reply address.
Booking lookup
Use the reference first, with time, service, provider, and location as cross-checks.
Cancellation scope
For group or multi-service bookings, ask which guests or items are affected.
Reason
Use scannable reason choices, an optional note, and a neutral choice.
Next step
Offer another date, credit, or a call only when those choices match your process.
Policy and confirmation
Show your notice policy and explain that staff must confirm the outcome.
Related tools
Build the original reservation, appointment request, customer support, and feedback forms alongside the cancellation path.
Collect the customer, service, schedule, and contact details for a new reservation.
Open toolLet customers request an available time with a provider or service team.
Open toolGather preferred dates and appointment requirements before staff confirms a slot.
Open toolDesign a broader cancellation path with reasons, alternatives, and routing choices.
Open toolGive customers a structured way to ask for help with a reservation issue.
Open toolAsk about the experience after a service issue or completed appointment.
Open toolFAQ
Practical answers for service teams replacing scattered calls and cancellation emails.
It is an online form customers use to request cancellation of an existing reservation or appointment. It captures the customer, booking reference, scheduled service, date and time, cancellation scope, reason, and desired next step in one structured submission.
Start with the booking name, email or phone used to reserve, confirmation reference, service, location or provider, scheduled date and time, and whether the whole booking should be cancelled. Add the reason, optional notes, rescheduling preference, and policy acknowledgment when they support your workflow.
Yes. Ask whether the request affects everyone or selected guests. When selected guests is chosen, reveal fields for names or the revised party size. This gives staff the scope needed to update the reservation without cancelling the remaining guests.
Yes. Add a cancel-or-reschedule choice, then use conditional logic to show preferred alternative dates only to customers who want another time. Keep the wording clear that staff will review availability and confirm the change.
That depends on your booking system and internal process. For a request workflow, state that submission sends the details to staff and that the customer should wait for confirmation. This avoids presenting an unreviewed request as a completed cancellation.
Place your own policy summary near the final acknowledgment, including relevant notice windows and the process customers should expect. Keep the wording consistent with the policy you already use, and provide a contact route for questions or urgent same-day requests.
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and collect cancellation requests. The paid tier removes the Makeform badge.
Submissions appear in your Makeform workflow and can notify the staff responsible for bookings. Use the booking reference and scheduled time in the notification, then route rescheduling requests or urgent appointments to the person who can act on them.
Replace vague cancellation messages with complete requests.