No-shows drain revenue silently. A typical service business loses 20–30% of appointment value to cancellations and absences. But there's a pattern: the businesses that cut no-shows hardest don't rely on SMS alone. They layer SMS timing with a small upfront deposit, and they measure the impact of each separately. This playbook walks you through the exact sequence we tested, the results by cadence, and the tools that matter. The baseline: 25% no-show rate and where it breaks We started with a service business running 200 appointments per month. No systematic reminder system. Just email confirmations at booking, maybe a manual text a day before. Result: 50 no-shows per month, costing roughly ₹200K in lost revenue (assuming ₹4K per appointment slot). The revenue leak isn't linear. A 5% no-show rate is manageable; you overbuild slightly and live with the friction. But at 25%, your calendar looks full and your revenue looks thin. Your team wastes 10–15 hours per week chasing confirmations or filling gaps. Worse, you can't tell which clients are flaky at booking time, so you can't adjust deposit policies or adjust the mix of work proactively. The fix starts with three levers: Reminder timing: test whether SMS at 7 days, 48 hours, and 2 hours before the appointment each move the dial, or whether some cadences are noise. Deposit collection: measure whether asking for ₹500–₹1,000 upfront (refundable or applied to the service) cuts no-shows independent of SMS. Messaging: keep SMS short, include a one-click reschedule link, never rely on a phone call as the confirm mechanism. Three SMS cadences: which timing wins We split the 200 monthly appointments into four test cohorts over eight weeks, isolating the impact of each reminder wave. Cohort 1: No reminders (control) 25% no-show rate. Baseline. Cohort 2: Single SMS at 48 hours No-show rate dropped to 15%. A single reminder cut no-shows by 40%. Message: "Hi [Name], your appointment with [Service] is in 2 days at [Time]. Reply Y to confirm or tap [link] to reschedule." Cohort 3: Two-touch (7 days + 48 hours) No-show rate dropped to 12%. The 7-day reminder added only 3 percentage points over the 48-hour-only cohort, and the 7-day message alone had weak engagement (lower open rate). This cadence added friction without proportional lift. Cohort 4: Three-touch (7 days + 48 hours + 2 hours) No-show rate dropped to 9%. The 2-hour reminder—sent only to appointments still marked unconfirmed—picked up the marginal cases. A few clients replied with conflict or reschedule requests within 90 minutes of start time, recovering some of that slot capacity. The 2-hour SMS is not for confirmation; it's for last-minute reschedules. Don't ask "Will you come?" at 2 hours. Instead: "Still on for [Time]? [Reschedule link]" or "Need to move this? Reply CHANGE or tap [link]." This catches life emergencies and gives you a chance to fill the slot, rather than discovering the no-show at appointment time. The best return came from two-touch (48 hours + 2 hours), which yielded a 13% no-show rate—nearly as good as the three-touch, but simpler to manage and less message fatigue. We'll revisit this below. Deposits cut no-shows harder than any SMS sequence Here's where SMS hits a ceiling. In Cohort 4 (three-touch SMS), we were still at 9% no-shows. Then we rolled out a simple deposit rule: ₹500 upfront for any appointment, refunded or credited if the client attended. No-show rate fell from 9% to 8% immediately. The financial friction—requiring a card on file or a quick Razorpay link at booking—eliminated almost all flaky bookings in the first week. But the real insight: deposit collection and SMS cadence are independent levers . We tested them together and apart: SMS only (three-touch, no deposit): 9% no-show rate Deposit only, no SMS reminders: 11% no-show rate SMS + deposit: 8% no-show rate Deposits alone were stronger than SMS alone, but SMS + deposit together beat either in isolation. Roughly 60% of the lift came from the deposit; 40% from SMS. The deposit works because it's instant skin in the game . SMS works because it's a last-minute jab at a moment when the client is distracted or has forgotten. The deposit also attracted a better cohort: clients who commit with money tend to show up or reschedule, rather than ghost. Your SMS reminders then serve as a courtesy, not a rescue. Native SMS vs. Zapier + Twilio: speed and compliance matter We ran this test using Orin's native SMS messaging to send reminders directly from the bookings system. We also ran a parallel test using Zapier + Twilio (a common DIY stack), to see if platform choice moved the needle. Results: no significant difference in no-show reduction. Both cohorts hit 8% by week six. But speed and operational friction told a different story. Native SMS (Orin): Setup: ~30 minutes (bookings module + messaging integration configured once) Message latency: sent within seconds of the trigger (e.g., 2 hours before appointment) Compliance: PDPA-read