BEAUTY STUDIO
A booking tool and a CRM that finally talk to each other.
A studio already happy with its scheduling tool, but paying for that choice with manual work every time an appointment was made or moved.
The problem
What was going wrong
Bookings lived in a separate scheduling tool that did not talk to the CRM, so reminders and follow-ups were manual.
The studio did not want to replace the booking platform, and there was no good reason to. The tool worked. The problem was the gap between it and everything that was supposed to happen after a booking.
What I built
The system, piece by piece
A two-way connection through Zapier
The existing booking platform was connected to GoHighLevel so every appointment creates and updates a CRM record automatically. Updates matter as much as creation: an appointment that is moved has to move in both places, or the reminders go out for a time that no longer exists.
Four workflows on top of the synced data
Confirmations, reminders, no-show recovery, and rebooking prompts all run from the CRM record. Because the record is kept current by the sync, these fire against real appointment times rather than a stale copy.
A2P 10DLC approval for compliant texting
The business was taken through 10DLC registration so reminder and confirmation texts reach clients reliably. For an appointment business this is not optional: a reminder that gets filtered is the same as no reminder.
A subdomain DNS fix
A DNS issue was resolved so the booking pages load on the studio's own domain rather than a generic one. Clients booking through a URL that matches the business they just spoke to is a small thing that affects whether they complete the booking.
Reasoning
Why it was built this way
Why one-way syncs quietly break
A connection that only creates records looks correct on the day it is built, because the first test is always a new booking. It fails later, silently, on the first reschedule or cancellation, and by then nobody associates the wrong reminder with the integration.
What changed
The result
Every appointment lands in the CRM on its own, so confirmations, reminders, no-show recovery, and rebooking prompts all send without manual work. The booking pages load on the studio's own domain, and the account is cleared for compliant SMS.
Described in terms of what the system does. No performance figures are published here, because none have been independently verified.
Next Step
Recognise any of this in your setup?
Every project starts with an audit of what you already have, sent to you in writing before any building starts.