OTP+ B2B SMS & Social Login

Noticed a flood of failed verification attempts from one area code. Support investigated and confirmed it was a brute-force attempt. They enabled the rate limiter for that region — after three failed attempts, the IP gets temporarily blocked. The attack stopped within hours. Having someone who understands security patterns respond to that kind of question is reassuring.

B2B retailers logging in weekly found the 30-day trusted device period too short for their patterns. Support extended it to 90 days for accounts tagged as 'wholesale'. My retailers stopped complaining about the verification and some even mentioned they appreciate the security now that it's not intrusive.

Customers were entering phone numbers inconsistently — some with country codes, some without. Support enabled the automatic country code detection based on the customer's IP location. Now the input field pre-fills the country code and formats the number correctly. Small UX improvement that eliminated a common source of failed verifications.

The OTP widget was breaking inside our mobile app's webview. Support identified the webview rendering issue and provided a JavaScript bridge that handles the widget properly in webview contexts. Our app developer integrated it in half a day. They clearly had experience with this specific integration challenge.

Wanted OTP only on the login path, not guest checkout. Support configured the trigger to ignore guest sessions entirely. Guest checkout stays fast, account login gets verified. The distinction makes sense for our customer base where returning logged-in customers are higher value and worth the extra security step.

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.

OTP codes were expiring before the SMS arrived for customers on slower networks. Support extended the expiry window from 60 seconds to 180 seconds on our account. No more expired-code complaints from customers in rural areas with weaker cellular coverage. Simple fix, real impact.

Our store serves Arabic-speaking customers and the OTP input needed to support RTL text entry. Support confirmed RTL is fully supported and showed me the language-direction setting I'd missed. Arabic customers now see the entire widget in right-to-left layout, including the phone input. Inclusive design that actually works.

Wanted to skip verification for our Gold tier loyalty members. Support configured a customer tag exemption — anyone tagged 'gold-tier' bypasses OTP automatically. My best customers get a frictionless experience while new customers still get verified. Exactly the segmentation I was hoping for.

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.

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.

Wanted our brand's orange and white colors on the OTP widget instead of the default blue. Support walked me through every customizable element — button color, input border, background, text, even the timer circle color. The widget now looks like we built it ourselves. The depth of customization options exceeded my expectations.

People were creating fake accounts to abuse our referral program using the same phone number. Support enabled the one-number-one-account restriction and showed me the duplicate detection dashboard. Referral fraud dropped to nearly zero. The dashboard showing blocked duplicate attempts is satisfying to look at.

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

The verification popup was hiding behind our slide-out cart drawer. Support identified the z-index conflict in about Two minutes and sent a single CSS rule to fix it. The popup now appears correctly above every element on the page. They clearly deal with theme-specific conflicts regularly because the diagnosis was instant.

We sell to 40+ countries and I was worried about SMS delivery in some regions. Support sent me a country-by-country delivery reliability report and flagged three countries where alternative delivery methods would work Better. Proactively identifying potential issues before they became customer complaints shows they actually Think about the international use case.

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.

very nice app and the support system is very good , i personally loved this

Our BNPL provider needed verification before approval, specifically at the payment step rather than login. Support configured a custom trigger point at the payment method selection step. Now the verification only fires when someone selects BNPL, not for credit card orders. Surgical precision in where the verification appears.

I changed a setting I shouldn't have and suddenly every visitor saw a verification prompt. Support walked me through the configuration panel and identified the toggle I'd accidentally flipped. Reset it and the behavior went back to normal. They didn't make me feel bad about the mistake, which I appreciated.