Resources / guide
Plan availability, payments, reminders, rescheduling and support for an astrology, psychic, coaching or wellness consultation business.
01 / Start here
For individual practitioners or teams selling scheduled astrology, psychic, wellness or coaching sessions. Use it to define the complete appointment journey before choosing a calendar plugin.
Decide whether a booking is confirmed when a slot is selected, after payment, or after a practitioner accepts it. Each rule has different effects on double booking, abandoned payments and the messages sent to customers.
02 / Core guide
A booking widget only works when the service behind it is clear. Define each consultation’s duration, price, delivery channel, languages and eligibility. Decide whether clients select a named practitioner or the business assigns one. If availability changes by country or time zone, document the rules before selecting software.
Client-facing hours are not total working hours. Add buffers for preparation, notes and overruns. Decide whether overlapping services share the same calendar and what happens when two people try to reserve the last slot. A practitioner dashboard must show confirmed, tentative and unavailable time distinctly.
Choose full payment, deposit, pay later or prepaid packages. Write down refund and cancellation windows, no-show treatment, taxes, practitioner share and settlement frequency. Test partial refunds and failed payments rather than testing only a successful checkout.
At minimum, define an appointment record, customer contact details, payment state, service and practitioner, consent, timestamps and support notes. Restrict access to sensitive notes. If a CRM, video meeting service or messaging provider is connected, document how duplicate records and failed synchronisation are resolved.
Use a phone to book across two time zones; cancel inside and outside the allowed window; switch practitioners; simulate a missed video link; and send a reminder when a slot has changed. Verify that both customer and practitioner see the same final time and price. Assign someone to support exceptions manually at launch.
Launch checklist: published services and prices · slot rules · terms and cancellation policy · payment and refund tests · reminders · practitioner training · support owner · basic reporting.
Once the flow works, measure visit-to-booking rate, payment success, show rate, repeat bookings and support contacts. Use the consultation capacity calculator ↗ to see what the roster can actually deliver, then explore booking system scope ↗.
03 / Make the choice
The right choice depends on customer expectations and the team’s ability to deliver it consistently. Use the trade-offs as a starting point for a scoped pilot.
| Model | Best fit | Operational consequence |
|---|---|---|
| Instant confirmed booking | Services and practitioner hours are predictable. | Hold the slot during checkout, release it on failed payment and send both parties the same confirmed time. |
| Request and approve | A practitioner must review suitability or preparation time. | Display that the request is pending; set an approval deadline and avoid taking a final payment prematurely. |
| Package or membership | Customers buy multiple sessions or ongoing access. | Track remaining entitlements, expiry, reschedules and refunds separately from ordinary one-off bookings. |
04 / Build and test
Give each stage a named owner and a concrete acceptance test. Advance when the working journey and support response are clear.
List each service, duration, buffer, practitioner, delivery channel and bookable hours. Separate administrative time from client-facing capacity. Test daylight-saving changes, holiday closures and what happens when a practitioner is removed from a service.
Specify selected, held, paid, confirmed, rescheduled, cancelled, completed and no-show states. For each, assign an owner, message and money rule. A customer should always know whether the appointment is actually confirmed.
Connect payment, calendar, video links, CRM and reminders in a defined order. Use idempotent booking and payment references so retries cannot create two paid appointments. Record failed integrations and provide a support queue rather than silently dropping an appointment.
Test on mobile with a real calendar account and payment method. Book the last available slot from two browsers, fail a payment, reschedule across time zones and try a cancellation near the deadline. Review support cases before expanding services or automation.
05 / Worked example
A coaching practice offers 45-minute video consultations. Each booking blocks 60 minutes to allow notes. A visitor chooses a slot shown in their own time zone; the system holds it briefly during payment. The appointment is confirmed only after capture, and both parties receive the same calendar time and meeting link. If payment fails, the hold expires and the slot returns. A cancellation inside the published window triggers the documented refund path.
For each region, record practitioner time zone, customer time zone, displayed currency, language of confirmation, cancellation terms, payment availability and customer support hours. Test dates where daylight-saving rules differ.
06 / Measurement
Agree on the numerator, denominator and time window before launch. Segment by market or service when different customer journeys would hide a problem in the average.
| Signal | How to define and use it |
|---|---|
| Booking completion | Paid confirmed bookings ÷ booking starts, segmented by device and payment method. |
| Show rate | Completed sessions ÷ confirmed sessions, excluding approved reschedules. |
| Utilisation | Completed paid minutes ÷ truly bookable practitioner minutes. |
| Support burden | Booking-related tickets per 100 confirmed sessions, with reasons such as time zone or refund. |
07 / Launch gate
Use this as a team sign-off, then store the owner, evidence and test result beside each item in your project tracker.
08 / Questions
You need a reliable source of availability and a way to prevent conflicts. The implementation can vary, but each practitioner must see only the appointments they can fulfil and be able to block unavailable time.
A short temporary hold can prevent two buyers selecting the same slot. Release it after failed or abandoned payment and do not call it confirmed until your chosen confirmation condition is met.
Store a consistent canonical time, display the customer and practitioner local times clearly, and include the time zone in confirmations. Test daylight-saving transition dates.
Use a channel that the customer agreed to use and that your provider permits for the message type. Keep essential appointment details available through email or the account as well.
A clear service catalogue, honest availability, secure payment, reliable confirmations, rescheduling rules and a human support path. Add packages or matching after the basic booking flow works.
09 / Research notes
These sources informed specific implementation checks above. Product features and regional requirements can change; verify the current documentation before committing to a vendor or launch market.
Editorial review: September 2026. The example and planning metrics are illustrative. Regulatory, tax and contract questions require review for the countries and services you choose.
