Stop customers mistyping their email in Microsoft Bookings

What the booking page actually checks#

What we saw when testing (September 2026)#

We read the code that runs the public Bookings page and captured the calls it makes. The email box is checked in the browser against one format pattern: letters, digits and a few symbols before the @, then a domain with a top-level part of at least two letters. So jane@gmial.com, jane@outlook.co and jane@hotmail.con all pass, and the booking goes through.

One setup does prove the address: pages that require an email verification code. The first time the customer submits, Microsoft emails them a 6-digit code, and the booking is only created once they type it in. A mistyped address never receives the code, so the booking never happens. Our shared test page, on default settings, never asked for a code. Our "Bookings with me" page did.

On shared pages, Microsoft mentions one-time passwords as a business-level setting whose changes "may take up to 10 minutes to apply". Graph (beta) calls it enforceOneTimePassword, off by default. Microsoft doesn't document where to turn it on in the Bookings web app, and the code adds a step for every customer. For how this works on personal pages, see email verification on Bookings with me.

What a mistyped address breaks#

The booking still lands on the staff calendar and staff still get their invite. So nobody notices until the customer doesn't turn up. Meanwhile:

• No confirmation. The Bookings FAQ says that without the customer's email, "there's no way for the confirmation mail to be delivered". A wrong address has the same effect.
• No reminders or follow-ups. They go to the same address.
• No Teams link. For online services, the join link is in the confirmation and reminder emails. See Teams link missing.
• No self-service changes. The Manage booking button that lets customers reschedule or cancel is in the confirmation email.
• Possibly a stranger gets the details. If the mistyped domain exists and accepts mail, someone else receives the confirmation. In our tests, the manage link in a confirmation opened a page with Reschedule and Cancel buttons and no sign-in, even on a service set to stop customers managing bookings. So a typo can be a privacy problem, not only a missed email. See stopping customers rescheduling.

Fix a booking with the wrong address#

The Bookings FAQ says appointments can only be edited in the Bookings web app, not in Outlook. It doesn't publish step-by-step instructions for editing one, so this is the general route:

1. Open the shared booking page in Bookings and select Calendar.
2. Open the appointment, edit the customer's email address and save.
3. Make sure the customer actually got the details. Microsoft doesn't document whether saving sends a new confirmation to the corrected address. If you're not sure, call or message them with the time and join link. Or cancel and re-create it with Calendar → New booking: Microsoft documents that once you enter a valid email there, a confirmation goes to the customer with a calendar attachment.
4. Check the customer's saved record too. Microsoft doesn't say whether editing an appointment updates it, and staff who pick that customer next time could bring the typo back.

For other reasons customers don't get emails (a custom email question instead of the built-in field, notification settings, junk filtering), see customers not receiving emails.

Catch typos earlier (as of September 2026)#

• Keep the built-in email field required. Microsoft makes it required on new services by default. Don't replace it with a custom "Email" question, or confirmations stop entirely. More in custom fields.
• Ask for a phone number. Make Phone number required on the service, so staff have another way to reach the customer. A Microsoft 365 admin can hide phone on every page with Restrict collection of customer data (Settings → Org settings → Bookings), so check that first.
• Say what the email is for. Put a line in the service description such as "Your Teams link is sent to this address". People check an address more carefully when they know why it matters.
• Scan new bookings. When staff are notified of a new booking, look at the customer's domain. Slips like gmial, hotmial, outlok and .con stand out, and you can phone the customer before the day.
• Add a "type your email again" question for appointments that matter. Bookings won't compare the two answers, but staff can.
• SMS as a second channel. Microsoft includes SMS notifications in Teams Premium, and they work only in Canada, the UK and the US. A text message still reaches customers whose email address is wrong.

Doing this with BookingsXP#

The BookingsXP booking widget checks the email in two steps before the booking is sent: first the format, then the domain. It compares the domain with common misspellings of Gmail, Hotmail, Outlook.com, Yahoo, iCloud and Live (such as gmial.com, hotmial.com, outlok.com) and ending slips such as .con, .cmo and .nett. If it finds one, it shows "Did you mean jane@gmail.com (opens in a new tab)?" under the field, and one click swaps in the corrected address. It's a suggestion, not a block. It won't catch mistakes before the @ or in less common domains, and it only covers bookings made through the widget. BookingsXP is independent and not affiliated with or endorsed by Microsoft.