Past Calendly, short of Mindbody.
Custom booking app with multi-provider availability, resource constraints, deposits via Stripe, SMS and email reminders. Built for your rules.
Who this is for
Service business (clinic, salon, studio, rental) outgrowing Calendly or Acuity — needs multi-provider, resource-based scheduling with custom rules those tools cannot express.
The pain today
- Calendly hitting limits on multi-provider, resource, or rule complexity
- Acuity/SimplyBook adequate but UX dated, branding limited
- Mindbody or specialized tools costing $200+/mo per location
- No-shows eating revenue with no deposit enforcement
- SMS reminders scattered across plugins with different reliability
The outcome you get
- Availability engine respecting providers, resources, buffers, and custom rules
- Stripe deposits or full prepay to reduce no-shows
- SMS (Twilio) + email (Resend) reminders at T-24h and T-1h
- Branded booking UI matching your site design
- Admin dashboard for schedule overview, overrides, and reporting
Availability engine design
Availability is where booking systems live or die. The engine has to answer 'what slots are available' fast, across multiple providers with individual schedules, resources with capacity constraints (rooms, equipment), service durations that vary, buffer times between appointments, and custom rules (e.g., new clients need 1.5x standard duration, senior stylists only during weekday mornings). Building this from scratch is a classic trap — I use proven open-source availability libraries where possible and layer your specific rules on top. The right abstraction is 'a slot is a tuple of provider, resource, time-range' and rules filter the set. Getting this abstraction right day one avoids rewrites later.
Deposits and no-show handling
No-shows kill service-business revenue. Mitigation options in order of effectiveness. Upfront full payment: maximum reduction, friction at booking. Deposits (25–50%): middle ground, widely accepted, Stripe Payment Intents handle the capture with refund-on-cancellation-up-to-24h. Credit-card-on-file with charge-on-no-show: lowest friction, clear policy language required. SMS confirmation 24h before (reply to confirm): cuts no-show rate ~30% without any charge. I implement whichever combination fits your service category — medical often uses deposit + confirmation, salons often use credit-card-on-file, rentals always full prepay. Policy language on the booking page is as important as the technical implementation.
SMS and email reminders
Reminder stack: email confirmation at booking, email reminder 24 hours before, SMS reminder 2 hours before (for same-day appointments), SMS follow-up after (rating, rebooking). Twilio for SMS (reliable, per-message pricing) and Resend for transactional email. Opt-out honored per compliance (TCPA in US). Templates configurable per service type. Some categories (healthcare, legal) need HIPAA-compliant messaging — I route those through HIPAA-eligible providers instead of generic Twilio. This plumbing sounds boring but it's where 80% of commercial booking systems lose customers — reminders that don't send reliably feel like the whole product is unreliable.
Admin dashboard and overrides
Front-of-house staff need an override path. Book-outside-the-rules (walk-in accommodated manually), reassign to different provider when someone calls out sick, block unavailable time for training or maintenance, view all upcoming appointments across providers/resources, process no-show charges or refunds. I build admin with RBAC (front desk sees scheduling, manager sees reporting and financials, owner sees everything). Reporting covers utilization (percent of available slots booked), no-show rate, revenue per provider, and cancellation patterns. These are the numbers that inform staffing decisions.
Pricing
Custom booking systems fit the Applications Standard tier at $3,499/mo for typical builds (single location, 3–10 providers, standard rules). Multi-location, franchise, or complex rule sets (medical pre-authorization, group classes, recurring series) move to Pro at $4,500/mo. First-version timeline: 5–6 weeks. Subscription continues through refinement as the team finds edge cases (every service business does). 14-day money-back, cancel anytime, Work Made for Hire. Twilio and Stripe fees billed separately at cost.
When Calendly or SimplyBook is enough
For solo practitioners or tiny teams (1–3 providers, simple services, acceptable templated booking page), Calendly Paid or SimplyBook.me covers it at $15–30/month. Custom becomes worth it around 10+ providers, 5+ services, or when your rules can't be expressed in templated tools. I'll tell you honestly in the first call — if your complexity fits Calendly Pro ($144/year), that's what I recommend. Custom booking is a meaningful investment and should match a meaningful constraint, not just 'we want branded colors.' Brand-matching on Calendly via custom CSS is usually enough for brand-focused cases.
Frequently asked questions
The questions prospects ask before they book.
- Does it integrate with Google Calendar and Outlook?
- Yes — two-way sync per provider. When a provider books a meeting elsewhere in Google Calendar, availability updates. When a customer books through the system, the event appears in the provider's calendar. Supports Google Calendar, Outlook 365, iCloud Calendar via CalDAV.
- How does the deposit flow work?
- At booking, Stripe Payment Intent captures the deposit amount (configurable 25–100%). If the customer cancels more than 24 hours before, automatic refund. If they no-show, deposit stays. Policy language appears on the booking page and confirmation email. Refund disputes are manual via admin with audit trail.
- Can group bookings or classes work?
- Yes — classes with max attendee count, group bookings with shared resources (conference rooms, equipment). Multi-person bookings where one payer books for a group. Complex group logic (yoga class series with different attendees per session) configurable.
- What about recurring appointments?
- Recurring bookings (weekly therapy, monthly cleaning) supported with one booking action. Edit or cancel single occurrence vs entire series. Skip dates for holidays. Provider schedule changes propagate to future recurring appointments with customer notification.
- Is it HIPAA-compliant for medical practices?
- HIPAA-compliant configuration possible — HIPAA-eligible Twilio, encrypted PHI fields, BAA with hosting provider (AWS HIPAA-eligible services). Medical practices need your compliance officer's sign-off; I implement the controls to their spec. Non-medical booking uses simpler infrastructure without the BAA overhead.
Ready to start?
Tell me what you need in 60 seconds. Tailored proposal in your inbox within 6 hours.