OTP+ Phone, SMS & Social Login

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.

Expected 10x traffic for a popup sale and asked about SMS throughput. Support pre-scaled our SMS allocation for the sale window and monitored it live during the first hour. Zero delivery delays during peak traffic. The proactive scaling was something I didn't know to ask for.

Our support team couldn't access customer accounts because of OTP blocking them. Support configured a support agent bypass using specific IP ranges from our office network. Agents can log into customer accounts for troubleshooting while the OTP protection stays active for everyone else.

Asked about verification funnel analytics and support showed me a report I didn't know existed — completion rate, average time to verify, drop-off at each step, segmented by device type. The data showed mobile users complete faster than desktop users. Changed how I think about our checkout optimization priorities.

The app offers a useful OTP verification widget with potential to improve the customer experience for Arabic-speaking users. The support team provides an opportunity to help resolve RTL configuration questions, and clearer language-direction settings would make the setup even easier. With improved Arabic text alignment and phone input support, this app could become an excellent solution for stores serving multilingual customers. Overall, a helpful tool with room for further improvements.

New theme caused the OTP widget to overlap with our header navigation specifically on tablets. Support tested on multiple tablet resolution and found the breakpoint where the collision happens. They sent me a targeted media query fix for that specific screen range. Works perfectly on every device size now.

We wanted phone verification on returns, not just login — to make sure the person requesting the return actually placed the order. Support confirmed the API supports custom trigger points and helped us hook the verification into our return form. Now the phone number on the return request has to match the order. Fraudulent return requests dropped noticeably.

Asked about WhatsApp as a Verification channel for our Latin American customers. Support showed me the WhatsApp verification option in the channel settings. Customers in supported countries now get a WhatsApp message instead of an SMS by default. Delivery rates in Mexico and Brazil improved significantly Because WhatsApp is more reliable there than SMS. Thanks

We wanted phone verification on returns, not just login — to make sure the person requesting the return actually placed the order. Support confirmed the API supports custom trigger points and helped us hook the verification into our return form. Now the phone number on the return request has to match the order. Fraudulent return requests dropped noticeably.

I asked about conditional verification based on cart value and support set it up remotely during our chat. Orders under $150 go straight through; anything above triggers Phone Verification. Checkout friction dropped noticeably on small orders, while High-value ones still get the fraud check. Exactly the balance I was looking For.