Connect your existing Square account to take card payments from your clients. Payment links ride along with booking confirmations; in-chair sales on your Square reader sync back to the customer record so totals stay honest.
Calendar sync, payments, SMS, email — connected, not bolted on. We don't sell add-ons or charge a markup. Each integration runs the same job in production today.
Square for taking card payments from your clients. Stripe for your own StudioStudio subscription.
Connect your existing Square account to take card payments from your clients. Payment links ride along with booking confirmations; in-chair sales on your Square reader sync back to the customer record so totals stay honest.
Runs your StudioStudio subscription — seats, the SMS add-on, your trial, your invoices. Update your card or download receipts through the Stripe-hosted customer portal. Not used for client payments; that's Square.
How confirmations, reminders, follow-ups, and campaigns reach your clients.
SMS delivery for booking confirmations, 24-hour reminders, and bulk campaigns. We run the Twilio number for you and pass per-message cost through at Twilio rates — no markup.
Transactional email — confirmations, reminders, receipts, and a calendar invite attached so it lands in the client's calendar — plus bulk marketing campaigns. Sent from a verified sender so it lands in the inbox, not spam.
Your existing Google Calendar and your StudioStudio schedule, kept in sync.
Two-way OAuth sync, per provider. Bookings made in StudioStudio land on the provider's Google Calendar; busy events on Google block their StudioStudio availability so nothing double-books across your work and personal life.
Type-ahead addresses anywhere you enter one, and real travel time between stops for mobile services.
Address autocomplete for studio locations (in admin) and for clients booking a mobile or onsite service. Selecting a suggestion populates street, city, state, postal, country, lat/lng, and a stable place_id so the address stays canonical instead of drifting on every retype.
For mobile services, we query Google with a future departure time to get traffic-aware drive time between the provider and the client. That becomes the travel buffer on the schedule, so back-to-back mobile bookings respect actual driving distance — not just a flat 15-minute guess.
We're a small team and we ship integrations on real signal — what our actual customers ask for. Tell us what you're using today and we'll look at it.
Request an integration →