Most booking tools were designed for gyms, coaches, and consultants. Solicitors are an afterthought — which is why, when you look at what the popular tools actually do with client data, the picture is not comfortable for a profession with confidentiality obligations baked into its regulatory framework.
This article is not about whether Calendly or Acuity are trustworthy companies. They are. It is about whether a solicitor should route client enquiries — names, email addresses, the nature of the matter they want advice on — through a third-party platform’s infrastructure at all, when a simpler alternative keeps everything on the firm’s own server.
The data question that most booking guides skip
When a prospective client books an appointment through Calendly, the following data is processed by Calendly’s servers: the client’s name, email address, phone number, and — if you use the notes field — whatever they chose to write about why they want legal advice.
That last part is the uncomfortable one. A person enquiring about a divorce, a redundancy dispute, or a property fraud will often say so in the booking notes. They are trying to help you prepare. That information — before any formal retainer exists — is passing through a US-headquartered SaaS company’s infrastructure under their data processing terms.
A WordPress plugin that stores booking records in your own database, on your own hosting server, removes that third party from the process entirely. The client’s details go from your website to your server and nowhere else.
What solicitors actually need from appointment booking
The practical requirements are not complex. Most solicitor firms offering initial consultations need three things to work reliably:
Accurate availability. The booking widget must show only times that are genuinely free. Not times that were free when the sync last ran. Not slots that ignore a client meeting added this morning. The Google Calendar that holds the fee earner’s day needs to be the live source, not a periodically updated copy of it.
A record of who booked and why. When a client books an initial consultation, you need their name, contact details, and — ideally — a brief description of the matter. That information needs to be in your Google Calendar event and in your system, ready before the call begins.
A professional booking experience on your domain. A firm that has invested in a website that conveys authority, expertise, and reliability should not send clients to a third-party page to complete their booking. The impression built by the website should carry through to the moment of commitment.
What the client actually experiences
Walk through the booking journey from a client’s point of view.
They have found your firm online, read the practice areas page, checked the team profiles. They have decided to make an enquiry. They click “Book an initial consultation.”
With a third-party tool: the URL changes to calendly.com/yourfirm or acuityscheduling.com/yourfirm. The design changes. The navigation disappears. They are on a different website filling in a form for an unknown scheduling company. They proceed — most do — but the professional continuity is broken.
With CalNative Booking embedded on your page: the URL stays the same. The firm’s header and footer remain visible. The booking form sits inside the same page they were already reading. They pick a date, pick a time, fill in their details, confirm. A confirmation email arrives from your domain with the appointment details and a calendar file. The experience is seamless because the booking never left your website.
How the Google Calendar connection works
CalNative Booking connects to the Google Calendar API using a service account — a server-to-server credential that gives your WordPress site permission to read availability and create events. It does not use OAuth, which means there is no login flow, no token that expires, and no reconnection required when the authorisation lapses.
Every time a visitor opens your booking page, the plugin reads your calendar’s free/busy data directly from the API. It does not maintain its own availability database. If a hearing was added to the diary this morning, that time is unavailable in the widget now. The calendar is the single source of truth.
When a booking is confirmed, a Google Calendar event is created immediately with the client’s name, email, phone, and their description of the matter in the event notes. The solicitor receives an email notification. The client receives a confirmation with an ICS calendar attachment and a cancellation link.
Blocking court dates, hearings, and out-of-office time
Any event in the connected Google Calendar automatically blocks the corresponding slots in the booking widget — no separate management required. Court dates, client meetings, supervision sessions, and personal commitments all remove themselves from availability the moment they are added to the calendar.
For firms with a dedicated consultations calendar separate from the main diary, the plugin can be pointed at either. If you want the booking widget to check multiple calendars for conflicts, share those calendars with the same Google account that the service account accesses — the free/busy query covers all calendars on the account.
One setup, permanent connection
The setup requires creating a Google service account in Google Cloud Console — a one-time process that takes about 20 minutes. A complete guide is available at How to Set Up a Google Service Account for WordPress. Once done, the connection does not expire. There are no annual re-authorisations, no prompts to reconnect after a Google security update, no maintenance tasks. It runs.
CalNative Booking is $39 per year for one website. For a firm currently paying for Calendly ($120/year) or Acuity ($240/year), the saving is immediate. More relevant for most solicitor practices: the booking data stays where it should — on the firm’s own server, under the firm’s own control.
