OTP+ Phone, SMS & Social Login

We were worried about bot accounts and fake registrations inflating our customer list. The browser and bot detection feature in OTP+ caught a surprising number of suspicious sign-ups in the first week. The detailed logs make it easy to review and act on.

Phone numbers with extensions were getting rejected. Support enabled an automatic extension stripper that removes everything after ext, x, or # before validating. Customers can now enter their full phone number naturally and the system handles the cleanup. Small formatting issue with a clean fix.

Our Hydrogen headless storefront needed OTP integration through the Storefront API. Support provided the API documentation and endpoint details, then helped our developer debug the integration over three support sessions. The headless OTP flow works identically to the hosted theme version now.

Added a prominent resend button with a 30-second cooldown timer after support showed me the resend configuration. Before that, customers who missed the initial SMS had no idea how to get another code. Simple addition that reduced support tickets about 'I never got my code' by about half.

Wanted to pre-register phone numbers for existing customers to avoid a verification wall on their first post-install visit. Support ran a bulk import of 3,400 phone numbers from our customer CSV. Existing customers experienced zero disruption after the install.

Two overlapping popups — OTP and age verification — were confusing customers. Support set the OTP widget to detect other popups and queue behind them. Age verification appears first, OTP triggers after age is confirmed. No more popup collision.

A customer reported receiving an unsolicited OTP code. Support checked the attempt log and found a failed login attempt from an unfamiliar IP. They helped me notify the customer and recommend a password change. Having the ability to trace exactly what happened turns a scary situation into a manageable one.

Made the returns portal OTP optional instead of mandatory after customers complained. Support configured a 'verify if suspicious' mode that only triggers when the return request has fraud signals — different address, high value, or multiple returns in a short period. Legitimate returns go through instantly, suspicious ones get checked.

Evaluated switching from SMS to email-based verification. Support walked me through the email OTP setup and helped me A/B test both methods. Email had a slightly lower completion rate but zero delivery cost. We ended up keeping SMS for new customers and offering email as a fallback. Support helped us run the test properly rather than just giving an opinion.

Monthly subscription renewals were triggering OTP verification even though the customer wasn't actively on the site. Support configured an exemption for automatic recurring charges. Subscriptions renew silently now, verification only fires on manual actions. Solved a problem I didn't realize I had until subscribers started emailing us about unexpected verification texts.