Help center · Calendar by J6 Venture
Everything you need to run bookings on your own site — from installing the plugin to connecting calendars, taking payments, and sending reminders. Organized into 13 topics, each with the exact steps and what you'll see on screen.
01 · Getting started
Install the plugin, connect a calendar, set up one meeting type, and share your link. Six short steps — most people are live in about ten minutes.
Plugins → Add New → Upload
Get the plugin from the J6 Venture website or the WordPress plugin directory. In your WordPress admin, go to Plugins → Add New → Upload Plugin, choose the .zip, and click Install Now, then Activate.
Once it's active, a new J6 Calendar menu appears in your WordPress sidebar. That's your home for everything below.
J6 Calendar → Dashboard
Open J6 Calendar from the sidebar. The dashboard is your at-a-glance view: upcoming bookings, how many hosts are connected, and your public booking-page link with Copy link and Open buttons. On a fresh install you'll see zeros and one host that isn't connected yet — that's your next step.
J6 Calendar → Team & Calendars
Go to Team & Calendars. You choose how hosts link Google or Outlook — both options connect the same calendars and give you every feature; the only difference is who runs the app.
You can switch between the two later without losing any bookings or connections.
Sign in with Google or Microsoft
After you continue, you'll sign in with Google or Microsoft and grant calendar access. Only calendar permissions are requested — never your email inbox. Once it's done, the host shows as Connected, and from then on the booking page reflects your real free/busy times and new bookings are written straight to your calendar.
J6 Calendar → Settings → Booking page
Open Settings. On the Booking page tab you set the last part of your public URL (your page address), your default timezone, the default language, and — optionally — a page to send visitors to after they book. Everything else adopts sensible defaults, so you only touch what you want to change.
J6 Calendar → Meeting Types
A meeting type is a kind of appointment people can book — an intro call, a strategy session, a demo. The plugin ships with three examples so you can see the shape of things; edit those or add your own with + New meeting type.
Give it a name, a duration, and a location (an online meeting link, a phone call, in person, or your own link), then Save. The live preview on the right shows exactly how it will appear to invitees.
Dashboard → Copy link
You're live. Back on the Dashboard, use Copy link (or Open) to grab your booking-page URL and share it anywhere — email signature, website button, DMs. Invitees pick a meeting type and an open time, with no account needed, and see times in their own timezone.
02 · Connecting calendars
Connecting a calendar is what turns your booking page from a static form into a real scheduler — it reads your true free/busy times and writes new bookings straight to your calendar. There are two ways to do it, and both give you every feature.
Team & Calendars → Connect your calendar
The choice is only about who runs the connector app — not what you get. Both connect the same Google or Outlook calendars.
Managed by J6
Sign in and you're live in about a minute — nothing technical to set up. One-time purchase per host, with a 7-day money-back window.
Free · self-hosted
Create your own Google or Outlook app with a guided wizard — free and 100% on your server. About 10 minutes, and comfortable with a short technical setup.
When to use which
Pick one-click if you just want it working now and would rather not touch Google Cloud or Azure. It's the right call for most people.
Pick bring-your-own-app if you're comfortable with a 10-minute developer setup, want it completely free, or need the connection to never involve any third party (some IT/compliance teams require this).
You can switch later either way — your bookings and existing connections are kept.
Choose plan → activate key → connect each host
J6 runs a verified Google & Outlook app for you, so there's nothing to create. It's a three-step flow:
J6C-XXXXX-XXXXX-XXXXX) and click Activate. Then each host clicks Connect and signs in with Google or Microsoft — done.
Pick a provider → paste your app keys
Here you create a free app in Google Cloud or Microsoft Azure and paste its keys into the plugin. The connection then lives entirely on your site — J6 never sees your account or data. Pick a provider and click Set up to open its guided wizard.
≈ 10 minutes · one-time
The wizard lays out three steps and gives you the exact Redirect URI to paste into Google. In the Google Cloud Console:
calendar.events and calendar.freebusy. Then publish the app to Production.Do this or your connection breaks weekly
Google leaves a new app in Testing mode, which expires the connection every 7 days. Publishing the consent screen to Production is the one step that prevents constant reconnecting — don't skip it. (You'll see a "Google hasn't verified this app" screen when you connect your own app — that's expected; click Advanced → continue.)
≈ 10 minutes · one-time
Same idea, in the Azure portal under App registrations:
Calendars.ReadWrite, OnlineMeetings.ReadWrite, and offline_access.Two common mix-ups
Copy the secret's Value, not its Secret ID — they sit next to each other and only the Value works. And add offline_access, or the connection can't refresh itself and will drop.
Team & Calendars
You can switch between one-click and bring-your-own-app anytime — your bookings and connections are preserved. To reconnect a host (say a token expired) or disconnect one, open Team & Calendars, find the host in Your team, and use Connect / Edit. Each host has their own connection, so one reconnecting never affects the others.
03 · Meeting types
A meeting type is a kind of appointment people can book. Everything about how it's booked lives in four tabs inside the editor — Details, Scheduling, Limits & Capacity, and Questions & Payment. Most settings have sensible defaults, so you only touch the ones you care about. This topic walks each control and, more importantly, when you'd actually use it.
Meeting Types → + New meeting type → Details
Give the meeting a name (what invitees see), a duration, and a location. The live preview on the right updates as you type. Choose a colour so it's easy to spot across the admin and booking page, and leave Active on so people can book it.
Choosing a location
Online meeting — a video link is created automatically on each booking (Google Meet for Google hosts). Best default for calls.
Custom link / phone / in person — paste your own Zoom/Teams link, ask them to expect a call, or give an address. Use these when you don't want an auto-generated video room.
Editor → Scheduling
This tab decides when the meeting can be booked. Four numbers do most of the work, and each solves a specific real-world problem.
Booking window (days ahead)
How far into the future people can book. Keep it short (e.g. 21–30) if your schedule changes a lot and you don't want commitments months out. Go longer (60–90) for planned engagements like onboarding or coaching.
Minimum notice (minutes)
The shortest lead time before a slot — 240 means "no bookings inside the next 4 hours". Set it to the time you need to prepare or avoid being ambushed. A quick intro call might be 60–120; anything you need to prep for is better at 1440 (24 hours).
Buffer before / after (minutes)
Padding the plugin holds around the meeting so bookings never land back-to-back. Buffer after gives you time for notes or travel; buffer before gives you time to prep. A common setup is 0 before, 10–15 after.
Host's hours vs Custom hours
By default a meeting uses your normal weekly hours (from the Availability screen). Switch to Custom hours when this one meeting should only be offered at special times — e.g. "I only take demos Tuesday and Thursday afternoons." Your days off and real calendar busy-times still apply either way.
One-time vs Recurring
Leave it One-time for a normal single meeting. Choose Recurring only when an invitee should book a repeating series in one go — like a weekly coaching slot or a standing check-in.
Editor → Limits & Capacity
Two independent controls here: how many people can join one slot, and how many of this meeting type can be booked overall.
Attendees per time slot
Keep it at 1 for a normal one-on-one. Raise it only for a group class, workshop or webinar — the same slot stays open until it fills, and the booking page shows how many spots are left. (Group slots are for single-host meetings.)
Max per day / week / month
0 means no limit. Set a cap when you want to protect your energy — e.g. "at most 3 discovery calls a day" — so a busy day can't fill entirely with one draining meeting type. The cap counts this meeting type only.
Editor → Questions & Payment
Ask for what you need before the call, and — if the meeting is paid — send invitees to your payment link after they book.
Booking questions
Invitees always give their name and email; add questions for anything else you need — a short answer ("What's this about?"), a multiple choice (budget range, team size), or a file upload (a brief, a resume). Keep it to what you truly need — every extra field lowers the number of people who finish booking.
Collect payment
Attach any payment link — Stripe, Razorpay, PayPal — and the invitee is sent to it right after booking. Use it for paid consultations so the slot and the payment happen together. (Full setup, including auto-confirming paid bookings, is in Topic 8 · Payments.)
Appears once you have 2+ connected hosts
With a single host, every booking goes to that person. Once your team has two or more connected hosts, an Assignment choice appears so you can decide who takes each booking:
When to use which
Round-robin fits a shared queue — a sales or support team where any qualified person can take the call, and you want fair distribution and the fastest slot for the customer.
Pooled fits meetings that genuinely need specific people together — a panel interview, or a call where both an account manager and a specialist must attend.
04 · Availability
Availability is the frame every booking has to fit inside. It's two layers working together: the weekly hours you set here, and the real busy times read from your connected calendar. An invitee only ever sees a slot when it's inside your hours and your calendar is free — you never double-book, and you never have to block times by hand.
Availability → Weekly hours
Turn on the days you take meetings and set a start and end time for each. Days left off show as Unavailable and are never offered. This is your normal week — individual meeting types can narrow it further with custom hours, but they can never open a time you haven't allowed here.
On a team: whose hours?
The Host selector at the top switches whose availability you're editing. Each host keeps their own weekly hours and time zone, so a booking on a shared meeting type only lands when that host is both open and free.
Availability → + Add a time window
A day can have more than one window. Click + Add a time window and you get a second start/end on the same day — the gap between them simply isn't bookable. Use it for a lunch break, a school run, or a "mornings only until 12, then 3–6" split. Add as many windows as a day needs.
When to split vs shorten
If you just finish earlier some days, one shorter window is enough. Reach for a split only when there's a real protected gap in the middle you never want booked over.
Availability → Date overrides
Weekly hours repeat every week; a date override changes one specific date. Use it two ways: block a day off entirely (a holiday, travel, a conference), or set special hours for a single date (e.g. "open 8–10 only on the 14th"). Overrides win over the weekly pattern for that date, and everything goes back to normal the next day.
Override vs calendar busy
You don't need an override just because you have an appointment — a real event on your connected calendar already blocks that time automatically. Reach for a date override when you want to change your bookable hours for a date, not just mark yourself busy.
Shown next to your hours
Your hours are stored and shown in your own time zone (the "Times are in…" note). Invitees always see slots converted to their time zone on the booking page, so "2 PM" for you shows correctly for someone in another country — no mental maths, no missed calls from a zone mix-up. Each host on a team carries their own zone.
Automatic, once a calendar is connected
This is the half that runs on its own. Once your calendar is connected, the plugin reads your busy times and hides any slot that overlaps one — meetings, all-day events, other bookings, anything already on the calendar. It only reads free/busy, not the details of your events. So the times people can book are always the intersection of "inside my weekly hours" and "actually free right now," kept current without you touching a thing.
If busy times aren't blocking
Almost always the calendar isn't connected (or the token expired) — check Team & Calendars for a green Connected status and use Reconnect if needed. Only events on the connected account block; a separate personal calendar you never linked won't.
05 · Team & hosts
A host is anyone whose calendar can take bookings. On a solo site there's just one; on a team, each person is a host with their own calendar, hours and personal booking link. This topic covers adding hosts, getting their calendars connected — including a link they can use without ever logging into WordPress — and keeping the roster tidy. Team hosting needs the one-click Connect plan; the header shows how many seats you're using.
Team & Calendars → + Add host
Give the host a name and a notification email (where their booking alerts go). Everything else is optional: a role/title and short bio that show on their personal page, a time zone, and a personal booking link — the last part of their URL. Leave the link blank and it's generated from the name. Adding a host just creates the record; their calendar is connected in the next step.
Seats & the plan header
The Team Plan row shows licences used vs available (e.g. "2 of 5"). A seat is taken when a host connects a calendar, not when you add the record — so you can list the whole team first and let people connect as they're ready.
Team & Calendars → Connect Google / Connect Outlook
Every host needs their calendar linked so bookings land there and busy times block automatically. You can do it for them right from the admin — click Connect Google or Connect Outlook on their row and sign in — or let them do it themselves without any admin access (next article). Either way it's one sign-in, no app setup and no keys, because the connection is brokered by J6 on the Connect plan.
Which button?
Match the host's own calendar: Connect Google for Gmail / Google Workspace, Connect Outlook for Microsoft 365 / Outlook.com. A host can only be connected to one calendar at a time; use Reconnect later if they ever switch accounts.
Team & Calendars → Send invite
This is the tidy way to onboard teammates: click Send invite on their row and they get an email with a single Connect your calendar button. They never need a WordPress login, a password, or anything technical — the link is theirs alone and works for 14 days.
The button opens their personal host setup portal. They pick Google or Outlook, sign in once, and land on a "You're connected" screen — no admin, no keys.
On the same screen they turn on the days they work and set start/end times — and can Add a window to leave a midday gap like lunch. They press Save availability and they're live. Nothing they do here touches the rest of your site.
Invite vs connect-for-them
Use Send invite when the host manages their own calendar and you'd rather not touch their sign-in — the cleanest option for real teams. Use Connect Google/Outlook from the admin when you're setting someone up while sitting with them, or connecting a shared inbox you control.
Meeting Types → editor → Assignment
Once two or more hosts are connected, any meeting type can share bookings across them. Round-robin spreads bookings evenly and offers the soonest free person; Collective needs the whole pool free at once. You choose the mode and tick which hosts are in the pool inside the meeting-type editor — the full walk-through is in Topic 3 · Meeting types.
Team & Calendars → Edit / Reconnect / Disconnect
Each host row has the controls you need over time. Edit changes their name, role, bio, time zone and personal link. Reconnect re-runs the sign-in if a token ever expires or they switch accounts. Disconnect unlinks the calendar (freeing the seat) while keeping the host record, so bookings stop landing there until they reconnect.
Before you remove a host
Deleting a host removes their personal link and takes them out of every pool. If they host any round-robin or collective meetings, reassign or re-pool those meeting types first so bookings keep flowing to the rest of the team.
06 · Booking page
Your booking page works out of the box — but it's the face customers see, so it's worth a few minutes making it feel like you. Address, brand, language and where people land afterwards all live under Settings; putting the page inside another site lives under Embed. Every setting has a sensible J6 default, so change only what you care about.
Settings → Booking page
The page address is your public URL — you pick the last part (e.g. /calendar); the rest is fixed to your site. Letters, numbers and hyphens only. Set a default time zone for the page here too. One caution: changing the address updates every booking link, so anything you shared before will need re-sharing.
Settings → Booking page → Default language
The booking page ships in English, Hindi, Spanish, French and German. It auto-detects each visitor's browser language and shows a switcher, so an international audience sees their own language automatically. The default language you set is just the fallback for when a visitor's language isn't one you offer.
Settings → Appearance
This is where the page becomes yours. Set an accent colour (or "Adopt theme" to inherit your site's), pick a font from a curated list, style the buttons (fill, text colour, and shape — pill / rounded / square), choose a page theme (auto / always light / always dark), add a logo, and write a one-line welcome line under your host. Everything falls back to clean J6 defaults, so even untouched it looks intentional.
Fastest way to look on-brand
Set the accent colour to your brand colour and add your logo — those two do most of the work. Leave font and buttons on the defaults unless you have a specific brand font in mind.
Settings → Booking page → After booking, send visitors to
Leave this blank to show the built-in confirmation screen. Or point it at your own thank-you page — ideal for ad funnels, because the plugin appends ?j6_booked=… to the URL so your page can register the conversion. Pair it with the tracking setup in Topic 10 for full attribution.
Embed
You don't have to send people to a separate page at all. The Embed screen builds a snippet you can drop into this WordPress site (there's a Booking calendar block) or any other site — Webflow, a plain HTML page, an email's landing page. Choose what to book (any meeting or a specific one; everyone or one host) and how it appears, and a live preview shows exactly what visitors will see.
Which display mode?
Inline sits in the page and auto-grows (no scrollbar) — best for a dedicated "Book a call" section. Popup button opens the calendar in a centered overlay — good beside a call-to-action. Floating button pins a button to the page corner on every page it loads — good for "always reachable" across a whole site.
07 · Notifications & messaging
Good booking software is quiet in the right way: the invitee gets a clean confirmation, a nudge before the meeting, and updates if anything changes — without you lifting a finger. All of it is on by email out of the box. This topic is about turning messages on or off, changing their wording, adding reminders, and (optionally) sending on WhatsApp too.
Notifications
One screen controls every message your invitees receive. Each row is an event — Booking confirmation, Rescheduled, Cancelled, and any Reminders — and each has a channel toggle for Email, SMS and WhatsApp. Toggle a channel on or off per message, or hit Edit to change the wording. Email is ready immediately; SMS and WhatsApp stay greyed out until you connect a provider.
Reminder timing
Two reminders come set up — 1 day before and 1 hour before. Keep both for meetings people forget; drop to one for quick calls. Use + Add reminder for a third (e.g. "3 days before" for a paid session). Each reminder is its own row with its own channels.
Settings → Emails
Set the from name and from email so booking mail looks like it's from you, not the site default. There's also a toggle to email the host when a new booking comes in — leave it on so you're never surprised by a meeting on your calendar.
If emails land in spam
Use a from-address on your own domain (not a free Gmail/Yahoo) and make sure your site can actually send mail — most hosts need an SMTP plugin or a sending service (Resend, SendGrid, Amazon SES) wired into WordPress. Deliverability is a mail-server thing, not a calendar thing — see Troubleshooting.
Settings → WhatsApp
Booking reminders reach people far more reliably on WhatsApp than in an inbox. Two ways to connect: Periskope (a third-party gateway — a quick separate signup) or the official WhatsApp Business API. Set one up, choose which is live, and the WhatsApp toggles in Notifications light up. For WhatsApp to reach invitees you also need their number, so turn on the phone field in Settings → Booking page.
Periskope vs the official API — be honest with yourself
Periskope sends through an ordinary WhatsApp session, so it can send free-form text with no template approval — but it uses WhatsApp's consumer service, which breaks WhatsApp's Business terms and can get the number banned. Fine for testing or low volume. For anything you depend on, use the official Business API — approved templates, but it won't get you banned.
Messaging
Beyond the built-in notifications, the Messaging screen lets you build reusable templates (Email, SMS or WhatsApp) with merge fields like {invitee_first_name}. On their own they do nothing — you wire a template to a booking event under Automations (e.g. "when a Deep Dive is booked, send this WhatsApp"). Use it for anything the standard confirmations don't cover, like a prep checklist or a follow-up.
08 · Payments
Paid consultations work in two layers, and it helps to keep them straight. Layer one — collecting the money — is a payment link you attach to a meeting type; the invitee is sent to it right after booking. Layer two — auto-confirming — is optional plumbing that flips the booking to "paid" the instant the money actually clears, so you're not reconciling by hand.
Meeting Types → editor → Questions & Payment
Any payment link works — Stripe, Razorpay, PayPal, a hosted checkout. Paste it into the meeting type and the invitee lands on it immediately after choosing a time. This alone is enough to charge for a call. Until the auto-confirm below is set up, a paid booking simply sits as awaiting payment until you mark it paid from Bookings. Full field details are in Topic 3.
Settings → Payments
To skip the manual step, connect a webhook. Under Settings → Payments pick Razorpay or Stripe, copy the webhook URL shown, paste it into that gateway's dashboard, and paste the gateway's signing secret back here. From then on, every payment event is signature-verified and the matching booking is marked paid automatically — no manual reconciliation.
One webhook per gateway
Set up the gateway you actually use to charge. Each has its own URL and its own signing secret — don't cross them. The signature check means a forged "paid" call can't sneak a booking through, so the secret matters: paste it exactly.
Bookings → a booking → Mark paid
You don't need webhooks at all if your volume is low. Take payment however you like, then open the booking in Bookings and mark it paid. The auto-confirm webhook simply automates this one action — it's a convenience, not a requirement.
09 · Managing bookings
Every appointment someone books lands in Bookings — the running record of who's meeting you, when, and everything they told you on the way in. It's also where you act after the fact: reschedule, cancel, or mark a payment received. The calendar event and the invitee's emails are already handled automatically; this screen is for the human follow-ups.
Bookings → Upcoming / Past / All
Three tabs split the list by time: Upcoming for what's ahead, Past for history, All for everything. Each row shows the invitee, the meeting type, the time, and status. Open a booking to see the full picture — their answers to your booking questions, any files they uploaded, the video link, and the host it's assigned to.
Shown on every booking
A booking's status tells you where it stands at a glance. Confirmed is a normal live booking. Awaiting payment means it's a paid meeting whose money hasn't cleared yet (see Payments). Cancelled is off — the time is freed and the calendar event removed. Reschedules keep the same booking with a new time. You act on a booking by opening it and using the controls there.
Bookings → open a booking
Open a booking to reschedule it (the invitee gets the "Rescheduled" note and the calendar event moves), cancel it (they get the "Cancelled" note and the slot reopens), or mark it paid if you took payment outside an auto-confirm webhook. Each action fires the right notification from Topic 7 automatically, so you never have to email the invitee yourself.
Reschedule vs cancel-and-rebook
Always reschedule when it's the same meeting at a new time — it keeps the history, the answers and the payment attached. Only cancel when the meeting genuinely isn't happening, since cancelling frees the slot and closes the record.
10 · Integrations & automation
A booking is a useful event for the rest of your stack — a Slack ping to the team, a new row in a CRM, a conversion counted in Google Ads. The Integrations screen pushes every booking event out to wherever you want it, and the Tracking settings tie bookings to your ad spend. None of it is required; add only the pieces you'll actually use.
Integrations
When a booking is made, paid, rescheduled or cancelled, the plugin can send it to a Slack channel, Microsoft Teams, a generic webhook, or expose it through the read API. Slack and Teams give your team a live feed; webhooks connect everything else.
Integrations → Webhook → + Add webhook
Paste a Zapier/Make "Catch Hook" URL, an n8n endpoint, or your own server, and each booking event is sent as a signed JSON payload. The signature lets your receiver verify it really came from your site. If your endpoint is down, the request is retried — so a brief outage doesn't lose a booking. This is the bridge to anything with an API: CRMs, spreadsheets, internal tools.
Debugging a webhook
Use the Recent deliveries tab to see each attempt and its response — the fastest way to tell "my endpoint rejected it" from "the plugin never fired." Start in a Zapier/Make test step so you can watch the payload arrive before wiring the real automation.
Settings → Tracking
If you run Google Ads, count a completed booking as a conversion so Google can optimise toward it. Add your Google Ads Conversion ID and label (and optionally a Tag Manager ID), and the plugin fires the conversion the moment a booking completes. Enhanced Conversions can send the booker's hashed email for better match rates.
If the booking page is embedded elsewhere
Every booking also pushes a j6_booking event to the dataLayer and posts it to the parent window. When the calendar is embedded in another site, drop the snippet from Settings → Tracking on the parent page so the conversion fires there — that's where your ad pixels live, and it gives the cleanest attribution.
Messaging → Automations
Separately from the outbound webhooks, Automations wire your reusable message templates to booking events — "when a Deep Dive is booked, send this WhatsApp; three days later, send that email." It's how you build sequences beyond the standard confirmation and reminders, all inside the plugin.
11 · Insights
Insights turns your bookings into a simple read on demand for your time: how many meetings you're taking, how often they cancel, when your busy times fall, and which meeting types actually get booked. It's not a vanity dashboard — the point is to spot patterns you can act on, like a meeting type nobody books or a day that's always overloaded.
Insights
Pick a date range — 7, 30, 90 days or a custom span — then narrow by meeting type and, on a team, by host. The numbers below update to match. Export CSV pulls the underlying bookings out for your own spreadsheet or finance.
Volume · cancellations · busy times · best types
Volume is your booking trend over the range — is demand rising or flat? Cancellations are worth watching as a rate: a type that cancels a lot may have the wrong notice window or too little qualification up front. Busy times show when bookings actually cluster, which is your cue to open or protect hours in Availability. Best meeting types tells you where to focus — and which starters to retire.
12 · Settings & privacy
A few settings don't fit neatly under a feature but matter for quality and trust: keeping fake bookings out, deciding what you ask invitees for, and knowing what happens to your data. This topic gathers those, plus a quick word on your plan and seats.
Settings → Booking page → Require email verification
Turn this on and a booking only completes after the invitee enters a one-time 8-digit code sent to their email (it expires in 10 minutes). Repeat bookers with a known email skip it, so it's low-friction for real people but stops bots and fake addresses cold. Worth enabling the moment you get any junk bookings.
Settings → Booking page → Ask for the invitee's phone
Three choices: don't ask, ask (optional), or ask (required). This adds a phone field to the booking form, checked in international format (e.g. +91 …). You need it if you want WhatsApp or SMS reminders to reach people — no number, no message. Otherwise keep the form short and leave it off.
Settings → Data
By default your bookings and settings survive deactivating or reinstalling the plugin — so an accidental deactivation never wipes your history. One toggle, delete all bookings and settings if the plugin is uninstalled, opts into a clean wipe instead. Leave it off unless you specifically want removal to erase everything.
What leaves your site — and what doesn't
Bookings live in your own WordPress database. On the free bring-your-own-app path, calendar tokens are yours and never touch J6. On the one-click Connect plan, OAuth is brokered by J6 to keep setup keyless — it reads only free/busy and writes the event, never your event details.
Team & Calendars → plan header
Solo use is free on either connection path. Team hosting — more than one connected host, round-robin and collective meetings — runs on the one-click Connect plan, where the Team & Calendars header shows seats used vs available. A seat is consumed when a host connects a calendar, and freed when they disconnect, so you're only ever paying for people actually taking bookings.
13 · Troubleshooting
Most snags trace back to one of three things: a calendar that isn't actually connected, an email that can't be sent, or a piece of plumbing (webhook, provider) that isn't finished. Here are the ones people hit, with the fix that usually clears them.
Almost always the calendar isn't connected, or its token expired. Open Team & Calendars and check the host shows a green Connected — if it's grey, connect it; if it was connected before, hit Reconnect. Remember only the connected account blocks and receives events; a separate personal calendar you never linked won't.
Licence keys only work on the one-click Connect path. If activation is refused, the site is almost certainly still in bring-your-own-app mode — switch it to Connect in one click first, then paste the key. The key and the plugin version are rarely the problem; the connection mode usually is.
Expected while your own Google app is still unverified — it's your app, so it's safe. Click Advanced → continue to (your app) to proceed. Two ways to make it go away: publish/verify the app in Google Cloud, or switch to the one-click Connect plan, where J6's verified app is used and you never see this screen.
An unverified Google app in "testing" mode issues tokens that expire after 7 days — so the calendar keeps disconnecting. Fix it by moving the app from Testing to In production in the Google Cloud consent screen (or by verifying it). Or sidestep it entirely with the one-click Connect plan, whose tokens don't expire this way.
Two different causes. If no email arrives, it's deliverability — WordPress can't send mail reliably on its own; add an SMTP plugin or a sending service (Resend, SendGrid, SES) and use a from-address on your own domain. If email works but WhatsApp/SMS doesn't, check that the provider is connected in Settings → WhatsApp, that channel is toggled on for that message, and that you're asking invitees for a phone number.
Landing in spam
Sending from a free Gmail/Yahoo address through WordPress is the fastest route to the spam folder. Use your own domain and a real sending service, and set the from-name/from-email under Settings → Emails.
The webhook isn't finishing the loop. Check that you pasted the webhook URL into the right gateway (Razorpay or Stripe — the one you actually charge with), and that the signing secret in Settings → Payments matches that gateway exactly. A mismatched secret means events fail signature verification and are ignored. In the meantime the booking sits as awaiting payment — you can always mark it paid by hand from Bookings.
The booking page always shows each visitor slots in their own time zone, and your hours are read in yours — so "wrong" usually means a host's time zone is set incorrectly. Check the host's zone in Availability (each host has their own) and the page default under Settings → Booking page. Once those are right, the conversions take care of themselves.
Note exactly what you did, what you expected, and what happened instead — including the meeting type, the host, and any on-screen message — and send it along. The Recent deliveries tab under Integrations is gold for webhook issues, and a host's Connected status is the first thing to check for anything calendar-related.