Group coaching bookings: seat limits, payments and reminders

To set up group coaching bookings, create one session with a seat limit, a price per person and the joining details. Then send reminders that match each attendee's status. The tricky part is the last seat. You need to know what happens when two people try to book it, or when someone stops halfway through paying.

A spreadsheet can't tell you that. Picture a workshop for eight people. Six have paid, one says they're still checking out, and another asks if there's space left. Your group coaching booking system has to keep the session, its seats and each payment in sync.

Group events and collective meetings solve different problems

A group event lets several clients book seats in the same session. A collective meeting needs several hosts to be free at the same time. An eight-person coaching workshop is a group event, while a panel interview is usually a collective meeting. Adding a co-coach to a workshop doesn't change that, and you still need a seat limit for attendees.

Caletus offers group events with a seat limit and takes paid bookings through Stripe, which comes with the Professional and Enterprise plans. See how Caletus group scheduling handles seats and attendee lists.^[1][2]

Run your first paid group session as a small pilot. The checks in this guide show you how seats and payments behave together in your own workspace before you open it to clients.

Write down the session details first

Before you publish, add the date, the time zone, the coach and where to join. Say who the workshop is for and whether everyone gets speaking time. Eight seats is only an example, so pick a size you can run well.

Say whether people are buying one session or a series. Leave subscriptions, bundles, waitlists and recordings off the page unless you've actually set them up. Each one is a separate feature and a separate promise to keep.

Decide what one booking buys

The simplest rule is one booking, one seat. Put that rule next to the price. If someone books for a colleague, tell them whose name and email to enter. If one purchase can cover several people, test the quantity limit and check that each person gets their own joining details.

Count attendee seats separately from the coach. Check whether guests, co-hosts or observers use up seats. Check your video account's participant and time limits too, because a seat limit on the booking page doesn't change your Zoom or Google Meet plan.

What happens to a seat during checkout

For example, a session has eight seats. Six people have paid, and one is partway through checkout with a temporary hold on a seat. If holds reserve seats, only one place is left. The six payments of USD 60 add up to USD 360 before fees, tax or refunds.

The rule matters more than the exact hold time. Find out when a seat is reserved, what releases it, and what happens if a payment goes through after the hold has expired. That late payment should be checked against the seat count, so you don't quietly end up with a ninth attendee.

Don't free a seat by hand just because someone closed their browser. Check whether their payment is still pending first. Give clients one clear contact for “I paid but didn't get a seat,” so they don't keep retrying while you're changing the seat count.

Set up a paid group coaching session in Caletus

1. 1Ask Caletus support to confirm that paid seats work for group events on your plan.
2. 2Create one group session. Set the real date, length, host and seat limit.
3. 3Connect your Stripe account, set a price per attendee and pick the currency. The steps match our guide to accepting payments for online consultations.
4. 4Write the outcome, prep instructions, final price and cancellation terms so people see them before checkout.
5. 5Choose the meeting location and check that someone outside your company can join.
6. 6Set up confirmations and reminders, then book test seats in Stripe's test mode and compare what the attendee and the host each see.

Keep the first session unlisted until you've seen how seats and payments behave. Note your plan and the setting names you used, so you can repeat the setup for the next date.

Joining instructions for a group session

Every attendee needs the date, start and end time, time zone, joining details and a contact for access problems. Say whether they'll need a camera, a microphone or a workbook. Give people a private way to ask about accessibility instead of a question on a public booking form.

Check what attendees can see about each other. Don't put every attendee's email in one shared confirmation because it's quicker. And only promise privacy or anonymity if your invitation and video settings actually provide it.

Find out whether everyone shares one meeting link or gets their own. Anyone holding a shared link can try to join, so use your video tool's host controls and explain how joining works in plain words.

When an employer buys a seat for someone else, the payer and the attendee are different people. The receipt may belong with a finance contact, while prep and joining details go to the attendee. Make sure one email address doesn't overwrite the other.

Give your team a quick way to check that each paid seat has the right person in it. If someone sends a replacement, update the booking and send the new person fresh joining details. Forwarding a private booking link isn't a safe way to hand over a seat.

Send reminders that match each attendee's status

Treat these timings as a starting point to test. Someone who books an hour before the session shouldn't get three overdue reminders at once. Send reminders to the attendee, not only to whoever paid. For wording, borrow from these appointment reminder email templates. Text (SMS) reminders are on the Professional and Enterprise plans.

When one attendee cancels and when you cancel the session

When one person cancels, check that only their booking changes. Decide whether their seat reopens right away or after you review it, and handle any refund in Stripe. Removing one attendee should never cancel the whole session.

When you cancel the session, every attendee needs an explanation and a clear choice under your terms. Moving the date may take one-to-one follow-up. Don't assume everyone accepts the new time, or that their payment moves to the new session on its own.

A Stripe refund and the seat count are separate records. Issuing a refund doesn't prove the seat was released, so check both, plus the messages that went out.^[3]

Test group booking payments down to the last seat

Use Stripe's test mode or a sandbox for these checks. Don't run real cards in live mode to fake a test.^[4]

After a retried checkout, check the attendee list too. A repeated email address won't reliably tell you whether someone paid twice, so use the booking and payment references. Blur those references in any screenshot you share outside your team.

Group coaching bookings launch checklist

• The page describes one session: who it's for, the outcome, the date and the time zone.
• The seat limit matches the group size you want and your video account's limits.
• You've tested a paid booking, the last seat, a failed payment and an expired hold.
• Every attendee gets the right confirmation, joining details and reminders.
• One attendee cancelling and you cancelling the session are handled differently.
• Someone owns refunds and client questions, and any manual steps are written down.

Start with a session you can comfortably run. Afterward, look at what attendees asked and what you had to fix by hand, and sort those out before adding dates or seats. A reliable eight-seat session beats a big setup nobody can keep track of.

• paid group coaching sessions
• group event seat capacity
• coaching booking reminders
• group booking payments