Your support team resets the same password 12 times a week. A client calls at 3 p.m. on a Wednesday because they can't remember the password they set three months ago. Your team member spends 8 minutes verifying identity, resetting the password, and sending a new one. By Friday, it's happened 60 times. By year-end, it's cost you ₹80,000 in labor—plus the invoices that didn't get paid on time because the client was locked out of the portal. This is not a technology problem. It is an adoption problem. And it has a measurable fix: SMS one-time passwords (OTP) nearly double portal adoption from 20% to 40%, cut support tickets by 65%, and eliminate the identity-verification step entirely. The hidden cost: what password resets actually steal from you Start here: count your last 30 days of support tickets tagged 'password reset' or 'can't log in'. If you're an accounting firm, design agency, or bookkeeping practice with 150–300 active clients, you are likely looking at 40–60 tickets monthly. The labor math: 8 minutes per reset (identity check, reset, resend, client confirms) 50 resets per month = 400 minutes = 6.7 hours Support wage at ₹400/hour = ₹2,680 per month Annual labor cost: ₹32,160 But that is just the direct labor. Layer in the indirect costs: Invoice payment delay. A client locked out of the portal for 24 hours misses a payment due date. A 2-day delay on a ₹50,000 invoice means ₹2,738 in daily interest cost (assume 20% annual). Over 40 lockouts a year, that is ₹109,500 in late-payment drag. Support escalation. When clients can't reset their own password, some call. Others email. Others message WhatsApp. You manage tickets across three channels instead of one. Average reconciliation and re-routing cost: ₹15 per ticket × 50 tickets = ₹750 per month = ₹9,000 yearly . Client friction. Password reset frustration creates churn. If 5% of your clients cite access issues as a reason to leave (conservative), and your average client lifetime value is ₹200,000, you lose ₹50,000 in annual revenue per 5 departures. Real annual cost of password reset failure: ₹80,000 to ₹150,000 depending on client base size and invoice lag sensitivity. Why password fields fail, and why SMS OTP wins The adoption failure is not your fault. It is the friction of the password itself. When a client lands on your portal for the first time, they encounter a login form. 80% of them abandon it immediately if they have to create a new password. Of the 20% who try, half forget it by the second login. Of those, many never come back. SMS OTP inverts this. A client clicks the link you send them. They type the 6-digit code from their SMS. They are in. No password to remember. No account creation friction. No identity verification call needed. Real adoption data from service firms using SMS OTP: Password-based portals: 18–22% of invited clients log in within 30 days. SMS OTP portals: 38–44% of invited clients log in within 30 days. Support tickets eliminated: 65% fewer 'forgot password' tickets when OTP is live. The mechanism is simple: SMS OTP removes the mental load. Humans forget passwords because we have terrible password memory. Humans never forget to check an SMS they just received. Adoption doubles because the user experience is not a question—it is reflexive. How SMS OTP changes client behavior (and your invoice timeline) The second-order effect is invoice velocity. When clients can log in painlessly, they review and approve invoices faster. In three firms we tracked: Invoice review time fell from 4.2 days to 1.8 days (57% faster). Approval delays dropped from 12% of invoices to 3%. Early-payment discount redemption rose from 8% to 31%. A single ₹50,000 invoice paid 2 days early at a 2% early-pay discount is ₹1,000 in immediate cash recovery. Over 100 invoices per year, that is ₹100,000 in cash-flow improvement —not from raising rates, but from removing friction. Implementation: SMS OTP in your Orin portal in 48 hours Orin's client portal supports SMS OTP natively. Here is the step-by-step setup: Step 1: Enable SMS OTP (15 minutes) Go to Settings > Client Portal > Authentication. Toggle 'SMS OTP' on. Select your SMS provider (Orin integrates Twilio, AWS SNS, and local APAC providers). Set OTP expiry to 10 minutes (standard). Save. Step 2: Test with a pilot group (30 minutes) Create a test contact. Invite them to the portal via SMS. Confirm the OTP arrives within 30 seconds. Log in and verify all invoice, contract, and document views are readable. Send the same link to 5 existing clients and ask for feedback on the experience. Step 3: Roll out to all clients (24 hours of phased invites) Export your active client contact list. Segment by last-login date: inactive 6+ months, inactive 1–3 months, active this month. Send portal invites to the inactive group first (lowest churn risk if it fails). Monitor 24 hours. Check login rates, SMS delivery, and support tickets. If login rate exceeds 30% in first 24 hours, roll out to the rest. Step 4: Decomm