Phone Number Validation Enhancement

Overview

We’ve rolled out enhanced phone number validation options across the Jumbo Lottery Platform (JLP), including both the sign-up form and any areas where customer phone numbers are edited in the WebUI and JLP Admin.

This update gives partners greater flexibility and control over how phone numbers are validated, helping to improve data accuracy and reduce the number of incorrect or invalid entries.

By default, all sites remain on Minimal Validation, which accepts any phone number format including invalid ones, such as 9-digit numbers. With this update, partners can now choose from three different validation levels to suit their operational and compliance needs.

Validation Levels

• Minimal (Default)
  • Accepts nearly all phone number formats.
  • No change to the current user experience.
• Basic
  • Restricts phone numbers to approximately 5–14 digits.
  • Note: This does not fully prevent invalid formats like 9-digit numbers.
  • Not recommended for partners dealing with strict compliance requirements.
• Strict (Recommended for partners seeking higher data accuracy.)
  • Full validation based on the customer’s selected country using Google’s phone validation package.
  • Accepts correctly formatted numbers such as:
    • 0412 345 678
    • 0412345678
    • +61 412 345 678
    • +61412345678
  • Rejects invalid formats like:
    • 0412 345 67 (too short)
    • 0412 345 6789 (too long)
       
  • Note: Admin operators will also be impacted by this change. They can still enter phone numbers in any accepted formats listed above, but if the number is invalid, an error message will appear prompting them to correct it before saving.
     

Why This Matters

• Improved Data Quality: Prevents fake or incorrectly formatted phone numbers from entering the system.
• Improved Marketing Outcomes: Ensures consistent, valid formatting for customer communications and integrations (e.g., SMS campaigns, Salesforce click-to-call).
• Configurable by Partner: Each site can choose the validation level that best suits their operational and compliance needs.
   

Next Steps

• Impact Assessment:
  Our engineering team has developed a CLI command to estimate how many recent sign-ups would have been rejected under strict validation.
  1. This helps partners make informed decisions by understanding potential customer impact.
• Partner Discussions:
  Before enabling strict validation, we recommend:
  1. Reviewing the impact report.
  2. Discussing internally to determine the preferred validation level.
  3. Informing customers ahead of any planned changes to reduce sign-up friction.

Contact the Customer Success Team to proceed with adopting this feature.