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.