Require on Signup
Overview
The fields you can require Customers complete during Profile creation flow are:
First and Last Name (mandatory)
Birthday (optional)
Gender (optional)
Phone Number (optional during signup)
Location selection (optional)
Before you require it...
Every required field at Profile creation adds friction, and phone number is one of the highest-friction fields (alongside password, captcha, and address).
At signup a Customer has low commitment, so a required phone field can feel unnecessary and raise privacy or spam concerns. That shows up in the numbers: forms that require a phone number see roughly 55% completion versus roughly 62% for forms that don't, a 7-point drop, and a required phone field can account for up to 37% of all form abandonments. In one signup flow with 9 fields, overall abandonment was 68%, and most of that drop-off happened at the phone field.
Reducing upfront fields, including deferring phone, cut abandonment to 18% and increased signups 2.5x. Baymard Institute finds that unexplained or early requests for personal data like phone are a major source of abandonment in registration flows.
Requesting a phone number later, right before a Customer completes a Reservation, costs less. By then they have intent and momentum, so tolerance is higher. Surprise or unexplained requests still cause drop-off: about 14% of shoppers abandon checkout when a phone field is simply required without explanation, and step-level drop-off for a required phone at final stages typically runs 10 to 20%, higher on mobile.
Account creation vs. late booking flow
During account creation (early)
~55% completion vs. ~62% without (7-point drop); can drive up to 37% of form abandonments
Low commitment, feels unnecessary, privacy and spam concerns
Late in booking flow (right before completion)
~10–20% step-level drop-off, higher on mobile; ~14% abandon if required without explanation
Higher intent and sunk-cost momentum, though surprise requests still cost signups
Recommendation
Avoid requiring phone during account creation. If you need it, defer to the booking flow and keep it optional with a clear explanation of why you're asking. The best practice for most Clubs is to collect it optionally later, at Profile completion or after a booking, for SMS reminders and confirmations. That maximizes new-account acquisition while still covering operational needs.
Require Phone Number
When this feature is enabled, Customers must verify a working phone number before their Profile is created. Every new account is tied to a real, reachable number, which cuts down on fraudulent and duplicate accounts. Requiring more information at signup also adds friction, so this page covers both how to turn the feature on and the tradeoff to weigh before you do.
How to enable this feature
Open Company Settings.
Go to the Feature Flags tab.
Scroll to the Login / Sign Up section.
Toggle Require Phone Number on Signup on.

Once enabled, the phone verification step is added to the Customer signup flow automatically. No other configuration is required.
What Customers experience during signup
When a Customer creates a new Profile, they see an added step to verify their phone number:
Enter their phone number.
Receive a one-time verification code by SMS.
Enter the code to confirm the number.

Once the code is verified, the Customer continues and completes account creation. Signup is blocked until a valid phone number is confirmed.
Last updated
Was this helpful?

