OTP+ Phone, SMS & Social Login

I had a few queries regarding Apple Connect, and the support team was incredibly helpful, patient, and thorough in addressing each of my concerns. I really appreciate their professionalism and the time they took to clarify everything.

Australian customers were getting codes from US shortcodes that their carriers blocked. Support switched us to a local Australian sender ID for the AU region. Delivery rates in Australia jumped from about 70% to over 95%. The per-region sender configuration made all the difference.

Wanted OTP verification on our newsletter signup form, not just account creation. Support expanded the widget trigger points to include any custom form with a phone field. Newsletter signups now get verified, which means our SMS marketing list has confirmed numbers only.

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 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.

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.

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.

Wanted to share one OTP+ account across US and Canada Shopify stores. Support explained each store needs its own installation but showed me how to replicate configuration between stores using the settings export. Set up the second store in under five minutes with identical settings.

Our accessibility audit flagged missing aria labels on the OTP input. Support confirmed the issue and pushed a widget update within the week that added proper aria labels, keyboard navigation, and screen reader announcements. Our next audit passed clean. Responsive to accessibility concerns without pushback.

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.

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.

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.

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.

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.

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