FluentBooking is a WordPress plugin that lets people book time with you without the back-and-forth. It lives on mosaicatlanta.org and every committee has their own booking page.
Someone fills out a form, picks a time slot from your real availability, and it lands on your calendar. No "are you free Tuesday?" No "how about 3pm?" No DMed screenshots of your week. The system handles the negotiation so you don't have to.
At Mosaic, we use it for orientation calls. Every committee — Outreach, Wellness, Interfaith, Research, Social Media, Public Speaking, Spanish Committee, and Brandyn's general — has a 30-minute call type set up. When a prospective member or interested org wants to talk to a specific committee, they pick a time that works for them, and it appears on that committee host's calendar.
It's Calendly, but it lives inside our own site and talks to Google Calendar directly. We own the data. We control the flow.
The plugin is installed as FluentBooking Pro (both the base and the pro version). The Pro version is what enables the Google Calendar and Google Meet integration — the base plugin handles the booking logic, but the sync to external calendars is a Pro feature. We have it.
From start to finish, here's what happens when someone books a call.
Guest lands on a booking page — either linked from mosaicatlanta.org/portal or a direct share link. They see the committee's 30-min call and a calendar grid of available time slots.
They pick a time — the available slots reflect the host's availability (configured per person, with weekly schedules and buffer times) and conflict-check against the host's Google Calendar.
They fill in their info — name, email, optional message. They can also choose Google Meet as the location if the host has it enabled (auto-generates a Meet link).
Booking is confirmed — the guest gets a confirmation with the time, date, and any location details. The host gets notified via email and the event appears on their Google Calendar.
It syncs to Google Calendar — the event gets created on the host's connected Google Calendar with all the details, attendees, and the Meet link if applicable. Cancel on Mosaic and it cancels on Google too.
FluentBooking Pro connects to Google Calendar via OAuth 2.0 — the same secure protocol Google uses for every third-party app.
Each host (each committee member who receives bookings) connects their own Google account to FluentBooking. They go to their host settings, click "Connect Google Calendar," and authorize it through Google's OAuth screen. The connection is stored encrypted in the WordPress database using a refresh token, so it stays connected indefinitely without re-authorizing.
FluentBooking uses two Google Calendar scopes:
The OAuth setup can use FluentBooking's official verified app (default, recommended — no setup needed) or an Own App if you want to bring your own Google Cloud Console OAuth credentials. For Mosaic, we use the default app — it works out of the box and the tokens are already stored on our host accounts.
The connection is per-person. Every host has their own Google Calendar connected. No shared logins. No centralized access. Each person controls who can book their time.
When a booking uses Google Meet as the location, FluentBooking creates the event with a conference link attached — so nobody has to send a separate invite.
Here's what happens under the hood:
hangoutsMeet conference typeMeet is optional per booking. The guest chooses whether they want an online meeting (Google Meet) or an in-person location when they book. If the host hasn't connected their Google Calendar, the Meet option shows as disabled with a note saying "Connect Google Meet First."
One less email to send. One less link to copy-paste. The meeting room just appears.
Before showing a time slot as available, FluentBooking checks the host's Google Calendar to make sure nothing's already there.
This is the calendar.readonly scope in action. When someone opens a booking page, the system queries the Google Calendar API for busy times in the date range being viewed. Any slot that overlaps with an existing event is hidden. The guest never sees a time that wouldn't work.
The API call is cached for 5 minutes (configurable in Settings) so the page loads fast even if the host has a busy calendar. If the host adds a manual event to their Google Calendar, it can take up to the caching window before FluentBooking sees it — but that's the difference between a 5-second page load and a 30-second one. The default works fine for orientation calls.
Conflict checking can be done against any combination of calendars the host owns — their primary calendar, a specific sub-calendar, or multiple. The host picks which calendars to check when they connect their Google account.
You don't have to remember what's on your calendar. The system remembers for you.
Once a booking is confirmed, the sync doesn't stop. FluentBooking keeps your Google Calendar up to date through the entire lifecycle.
Host changes the time in Mosaic → the Google Calendar event is patched with new start/end times → guest sees the update on their calendar.
Booking is cancelled in Mosaic → Google event status is set to cancelled → it still appears on the calendar (for auditing) but shows as declined.
If a multi-guest booking adds or removes someone, the Google Calendar event attendees are updated. The guest list visibility is controlled by the host's settings.
Each host can choose whether updates send Google Calendar notifications to attendees. Default is on — so guests get email notifications when anything changes.
The connection uses encrypted tokens — the access and refresh tokens are encrypted before they're stored in the WordPress database. If the token expires, FluentBooking automatically refreshes it using the Google OAuth flow. The only time you need to re-connect is if you revoke access from your Google account or if the token gets corrupted.
Set it up once. It just works until you decide it shouldn't.
Here's what it takes to hook up a new host's Google Calendar to FluentBooking. It takes about three minutes.
Go to Settings → Google Calendar / Meet
Choose "Default Verified App" unless you have a custom Google Cloud OAuth setup. Default works for 99% of cases.
Set caching time (5 min recommended)
Lower = more accurate conflict checks, slower page loads. Higher = faster, but up to that many minutes behind on manual calendar changes.
Each host connects in their Host Settings
Go to Calendars → pick your host profile → click Google Calendar → "Connect" → authorize through Google's OAuth screen. Pick which calendars to check for conflicts.
Verify it works
Create a test booking on your own page and check that it appears on your Google Calendar. Cancel it and confirm it disappears.
If something breaks — usually a token expiry or a scope change on Google's end — the error shows in the WordPress admin under the host's calendar settings. The fix is almost always "disconnect and reconnect."