Use a free webinar when the goal is education, lead capture, and deciding who needs a paid session next.
Workshops
Workshops and group consulting
Workshops turn Consulta from a one-to-one booking tool into a reusable consulting surface for training, clinics, webinars, and small cohorts. The current product proves the booking, confirmation, Beam, payment, and notification pieces separately; public group-seat checkout remains gated until capacity, roster, provider, and media proof are recorded.
Use a paid clinic when one expert can help several clients work through the same operational topic.
Each attendee should receive their own confirmation pass, join link, reminder path, and policy state once group seats are live.
Workshop formats
The first useful formats are narrow and practical: free automation webinars, paid AI/WhatsApp clinics, booking/payment operations sessions, internal team enablement, and small implementation cohorts.
- A free webinar should collect contact details and point serious clients to a paid session, service package, or reviewed retainer.
- A paid clinic should have one topic, a clear capacity, a fixed price per seat, and a time-bound outcome.
- A small cohort should use repeated sessions only after the operating rhythm, reporting, and cancellation rules are clear.
Capacity and seat rules
Group scheduling needs stricter capacity language than a simple consulting profile. A workshop should expose the host, topic, date, duration, capacity, remaining seats, price or free status, timezone, and policy before a client commits.
- Seats remaining must come from confirmed bookings, not manual scarcity copy.
- Free sessions can reserve a seat without checkout, but they still need contact and confirmation state.
- Paid sessions should confirm only after server-side payment proof, exactly like paid one-to-one bookings.
Per-attendee confirmation
When group seats are live, each attendee should receive a tokenized confirmation pass rather than a shared raw room link. The pass should show workshop details, calendar download, Beam entry, policy actions, and recovery routes.
- One paid seat must not become an open-access room link.
- Host and attendee links should be separate roles.
- Cancellation, reschedule, refund, and waitlist behavior should be explicit before launch.
Beam group-room readiness
Beam is the right video surface for workshops, but large-room behavior needs evidence before public claims. The product should prove browser join, mobile framing, host controls, and a stable session on the real media node.
- Target proof remains a real multi-participant smoke test, not a design promise.
- Host controls such as mute, eject, promote, and raise-hand belong behind the Beam adapter boundary.
- Workshop pages should not expose Beam room IDs, tokens, or provider internals.
Payment and notification gates
Notifications and payments are useful for workshops because attendees need reminders, changes, access recovery, and payment status. Live delivery still depends on provider credentials and smoke proof.
- WOP/WhatsApp and SMTP group messages remain gated until sender, template, callback, and delivery evidence exists.
- Payment links, QR links, and hosted checkout can support group seats later through the adapter architecture.
- Do not treat a WhatsApp reply, checkout return, or demo log as proof of paid attendance.
What is not live yet
Workshops are not a promise that public group checkout is open today. They are a product path for using Consulta as a consulting platform once the group-seat, roster, notification, media, and policy gates are proven.
- No emergency, regulated-care, or unlimited-support use is assumed.
- No attendee roster, waitlist, group-seat checkout, or host-control UI is claimed live yet.
- Use one-to-one booking, free intro, or contact review until the workshop inventory is published.