Directory, profile, offer, day, time, and intake details stay in one guided path.
ConsultaBooking guide
How booking works
This guide explains the Consulta client journey before you book. It is the plain-English version of how the scheduling, payment, confirmation, notification, and Beam handoff pieces fit together.
Free intros confirm immediately; paid sessions stay pending until server-side payment proof.
The confirmation pass is where clients join Beam, download calendar files, reschedule, cancel, and recover access.
1. Choose a consultant
Start from the consultant directory or a shared consultant profile link. Each active profile shows the consultant, headline, rates, free intro availability, regular availability, policy windows, and next booking action.
- Use the directory when comparing active consultants.
- Use the profile when you already know who you want to book.
- Current MVP discovery is public; private booking details stay off public pages.
2. Pick free or paid
Consulta treats session type as the first booking decision. A free intro is for quick fit/context; paid sessions reserve consulting time at the displayed BZD rate.
- Free intro booking is live when the consultant has it enabled.
- Paid sessions keep their configured duration and price for the selected booking.
- The booking form collects contact and prep context before the final handoff.
3. Select a day and time
Available days and times come from consultant availability, policy windows, buffers, active holds, and existing confirmed or pending bookings.
- Times are shown in the public booking flow with the configured timezone context.
- Temporary holds protect a slot while booking or checkout is in progress.
- Connected Google/Outlook calendar sync remains a later gate; current calendar handoff uses downloadable files and shortcuts.
4. Confirm or pay
Free intro bookings skip checkout and confirm directly. Paid bookings open a payment link, but the booking becomes confirmed only after server-side payment status says it is paid.
- A browser return page is not payment proof.
- Silvatech Payments and WOP-mediated hosted checkout stay behind server-side adapters.
- Simulator checkout remains available for demos until live provider credentials and smoke proof are complete.
5. Save the confirmation pass
After confirmation, the tokenized confirmation pass becomes the source of truth. Save that page instead of relying on a single email, chat message, or raw meeting link.
- The pass shows session details, Beam client join link, calendar options, policy actions, and preferences.
- Email and WhatsApp content should point back to the same pass.
- Live WOP/SMTP delivery remains gated until credentials, templates, and smoke proof are verified.
6. Join and manage the session
Use the pass to join Beam from the browser. The pre-join screen lets the client confirm their name, camera, microphone, and device state before entering.
- No app install should be required for the MVP join flow.
- Expired or invalid Beam links route to recovery instead of exposing private room details.
- Real Android Chrome, iPhone Safari, desktop, and 30-minute media proof remain acceptance gates.
7. Recover or change plans
If a message is delayed or a link is lost, use Account or Sign in with the same booking contact. WhatsApp support stays available for recovery cases.
- Recovery lookups stay generic when details do not match.
- Reschedule and cancel actions remain policy-bound.
- Support recovery does not bypass payment state, token validity, or consultant policy.