Mobile booking form: can customers finish on iPhone?

Your mobile booking form works on iPhone only if a customer can choose a service and time, send their details and receive a clear confirmation. I wouldn't judge it by how neatly it fits the screen. Test it from the public booking link through to the entry in your diary, rather than stopping when the page looks right.

Why test before festive bookings begin

On 17 September 2026, WebKit's Safari 27.0 announcement introduced customisable native dropdowns: built-in menus for choosing an option whose appearance a website can change. Safari is Apple's web browser, the app used to open websites. The announcement says these menus retain keyboard controls, support for software that reads the screen aloud, submission of answers and checks for missing or invalid details.

That doesn't mean your site has adopted them or that an existing form has broken. I'd use the release as a prompt to test, not a sales pitch for new software.

Edinburgh's Christmas is scheduled to run from 14 November 2026 to 3 January 2027. If you're taking festive salon appointments in Musselburgh or table bookings in Edinburgh city centre, that gives you a useful deadline. Make the checks before you point more customers at the booking page.

How to test the complete mobile booking form

Start on a real iPhone using Safari. A shrunken page on a laptop won't tell you what happens when the phone keyboard opens or someone taps a date with a thumb. Then repeat the check on another phone your customers use, including an Android phone if you can borrow one.

Use details you control and choose an appointment you can safely remove afterwards. If payment is involved, agree a safe way to test with your booking provider before proceeding.

• Open the same booking link a customer would use. Check you reach the right service or location without needing to sign in as the owner.
• Choose a service and appointment time. Try changing your choice and check that the selected date stays visible.
• Fill in your details. Check that the phone keyboard doesn't cover the next question or the button you need to continue.
• Leave a required answer blank. The form should explain what is missing without wiping the answers you have already entered.
• Complete the booking. Read the final screen and check it says whether the appointment is confirmed or awaiting your approval.
• Check the business diary and the customer's message. They should agree on the service and appointment time; remove the test booking afterwards.

Don't coach the person testing through a confusing step. If you have to explain where to tap, write that down as something to investigate.

Booking form not working on iPhone? Record the fault

Write down the booking page address, the phone model, the software version and the last action that worked. A report saying the calendar opens but won't accept an afternoon appointment is useful. Saying it doesn't work on mobile leaves the person fixing it guessing.

Take a screenshot if it helps, but hide customer details before sharing it. Note whether the problem happens every time and whether it also happens on another phone.

If the problem starts after the customer moves to another company's booking page, send that company the same evidence. Your website maintainer can help trace where it fails, but cannot necessarily change software owned by a separate booking provider.

While it is being fixed, put a clear alternative beside the booking link, such as your phone number and when you'll answer. Don't leave customers tapping a button you know is broken.

Ask only what you need to make the booking

The W3C Forms Tutorial recommends asking only for information needed to complete the transaction or process because unnecessary questions make abandonment more likely. W3C is the organisation that develops standards for websites. I'd review each required question against that rule before changing the design.

A garage in Livingston may need a vehicle registration number and the work requested to arrange an appointment. It should question whether a full postal address belongs in that first form. Keep necessary safety or suitability questions where the service requires them, but don't make a booking depend on answering marketing questions.

Give each question a visible label that remains there while someone types. If an answer needs correcting, explain what to change beside that answer. Test that correction on the phone too, rather than assuming a warning will be easy to find.

Confirmation is part of the booking

Decide what booked actually means for your business. If an appointment needs your approval, the final screen should say that the request has been received and explain what happens next. It shouldn't tell the customer an appointment is confirmed while leaving you to check availability later.

Check the message the customer receives as carefully as the form itself. Can they see the appointment details, find the address and work out how to change or cancel it? A successful test should leave neither side guessing.

When you measure results, count confirmed bookings rather than visits to the form. If your booking service records unfinished attempts, look for the stage where people stop. If it doesn't, start by watching someone make a test booking and recording where they get stuck.

When you should keep your existing booking form

If your existing booking form works reliably on real phones, keep it. A Safari update is a testing prompt, not evidence that you need bespoke software built just for your business.

You also don't need a paid maintenance arrangement if someone already takes responsibility for security updates, saved copies of your site and booking checks, and those jobs are getting done. Doing nothing to the design is fine when customers can complete the booking and the diary receives the right details.

Consider a change when you can point to repeated failures, missing booking options or avoidable work that matters to your business. Even then, ask whether a setting, a clearer instruction or a repair to the existing form would solve it. Replacing the whole system should need a better reason than its age or appearance.

What I would include in booking maintenance

I offer management and maintenance as an optional extra on top of your site's running costs. I keep your site current, apply security updates and keep saved copies in case something needs restoring. You also get a local number to ring.

For a booking website, I'd agree which tests are included and who deals with faults in a separate booking service. After a relevant change, I'd repeat the booking check and record the result. That gives you something more useful than an assurance that the page still opens.

For a wider maintenance review, I also cover whether to block automated tools that read websites for AI services. That's a separate question from whether customers can book; I wouldn't sell you a bundle of unrelated changes to fix a stuck calendar.

WebLothian is affordable on purpose. I want local businesses to get the help they need without being pushed into a rebuild when a small repair will do.

If you'd like me to check your mobile booking form, book the consultation (opens in a new tab). It's free, and every job gets a written quote before any work begins.