International consultation booking that customers can trust
A visitor in another country needs more than an available slot. They need to understand when the session takes place, what it costs, what information to provide and what happens if either side cannot attend.
For astrology, psychic and spiritual consultations delivered across borders. Check processor eligibility, tax, consumer and privacy requirements with qualified advisers for each market.
Write down what the customer receives.
A bookable offer needs a delivery format, duration, price basis, preparation, cancellation terms and response owner.
Separate a live video consultation, a call and a written chart report when they have different delivery times or input needs. State whether the session is one-to-one, recorded, translated or followed by written notes. Avoid hiding fulfilment limits behind a generic “contact us” page. Decide who handles a booking when the practitioner is unavailable or has not received the required birth information in time.
Before launching a country page, check whether the practitioner actually serves that market, what hours overlap, whether payment and support work there, and whether a clear local-language explanation can be maintained.
Show a local time and store an unambiguous instant.
A customer should see the date, time and time zone before payment and in the confirmation. A practitioner should see the same booking in their own calendar. Store the underlying instant with a timezone-aware representation and the customer's chosen zone; do not merely paste a local clock time into an email. Test daylight saving transitions, half-hour offsets and customers travelling after booking.
| Moment | Customer sees | Operator verifies |
|---|---|---|
| Selection | Available date, local time, zone and duration | Capacity and buffer rules |
| Payment | Same slot held with transparent expiry | No double-booking on failed payment |
| Confirmation | Calendar entry, joining details and change policy | Slot and payment references match |
| Reschedule | New time and confirmation | Old event released; reminder changed |
Write the failure paths: a payment succeeds while confirmation fails, a slot expires during checkout, or the practitioner cancels. Allocate a support owner and a manual recovery procedure. “24/7 booking” is meaningful only when these states can be recovered.
Distinguish display currency from what settles.
A customer-facing price, charged currency, processor fees, conversion and settlement currency can differ. Confirm country and account eligibility, supported methods, tax handling and payout timing with the actual processor before advertising a market. Stripe's currency documentation illustrates that payment amounts have currency-specific minor units and that presentment and settlement are separate implementation choices; it does not mean every Stripe product is available to every business everywhere.
Show the payable amount and currency before the customer commits. Keep a record of the amount and policy displayed at checkout, payment reference, booking ID, refund and support decision. Chargebacks are a distinct process from ordinary refunds; define who gathers evidence and who responds in time. Do not promise a “guaranteed” outcome from a spiritual consultation.
A client pays in one currency for a session next week, then the practitioner cancels. The support team needs the charged amount and currency, the original cancellation terms, processor reference, refund status and a replacement option. A spreadsheet of calendar slots alone cannot resolve the financial side.
Ask for details when they are needed.
An astrology session may require a birth date, time and place; a general introductory call may not. Explain why the information is requested and who receives it. Provide a path for unknown birth time and location ambiguity instead of forcing visitors to guess. For other guidance services, distinguish a question the adviser needs from optional sensitive personal history.
Do not put sensitive intake answers in public URLs, analytics events or routine email subject lines. Limit staff access, decide retention and deletion rules, and provide a safe way to correct an input. The UK's ICO explains data minimisation as collecting information adequate, relevant and limited to the purpose, and storage limitation as not keeping identifiable information longer than necessary. Apply the requirements relevant to the business and its markets with local advice.
Make the next-step message useful: the appointment time and zone, what to prepare, how to join, the change policy and a support contact. A reminder should not expose private consultation details in a notification preview.
Test the international journey end to end.
- Customer and adviser in different time zones see the same instant.
- Payment success creates one booking and one confirmation.
- Payment failure releases the held slot and shows recovery guidance.
- Unknown birth time has a truthful intake route.
- A reschedule updates both calendars and reminders.
- A refund can be reconciled to the original booking.
- Support can find the customer's displayed terms.
- Mobile and keyboard users can finish the journey.
Start with the countries and service hours the team can genuinely support. Measure completed bookings, failed checkouts, no-shows, reschedules, support requests and contribution after processor and fulfilment costs. Separate attempted bookings from paid confirmed sessions. Our booking system guide covers tool selection, and the capacity calculator helps test schedule assumptions.
Frequently asked questions.
Should every customer see a price in their own currency?
Only when the payment provider, rate presentation, settlement and refund handling support it accurately. Otherwise show the charged currency prominently and explain any uncertainty before checkout.
What if a client does not know an exact birth time?
Explain how the service handles uncertainty and which interpretations are affected. Provide an “unknown” option or a different service if appropriate; do not force a fabricated time.
Do we need separate pages for every country?
No. Create one only when availability, language, payment, fulfilment or relevant local information differs enough to help that market. Keep the operational details accurate.
Can this be done with an off-the-shelf booking tool?
Often yes for a simple practitioner journey, provided the chosen tool can handle the required zones, intake, payment and exceptions. Custom software is justified by needs the tool cannot reliably meet.
Scope the first market and complete session.
Primary references: Stripe currency handling, payment disputes, ICO data minimisation and storage limitation. Check current provider and jurisdiction requirements before implementing.