A client should understand who you help, why they should trust you, and what outcomes the session is designed to produce.
ConsultaConsultant checklist
Consultant readiness checklist
This checklist is the public version of the readiness bar Consulta uses before listing a consultant. It keeps the platform honest: a profile should feel bookable, paid-ready, and supported before clients are sent to it.
Free intros, paid durations, rates, currency, and policy windows must be configured before a public listing is promoted.
Every booking needs one obvious path for confirmation, Beam access, calendar actions, reminders, and support recovery.
Profile and proof
The profile has to answer the client's first trust questions before the calendar appears. Identity, positioning, outcomes, languages, prep guidance, and a usable photo all matter because the booking page is also the consultant's storefront.
- Public name, photo, headline, languages, timezone, and contact route are ready.
- Focus areas, client outcomes, preparation guidance, and FAQs are specific enough to sell the session.
- No regulated-care, legal, financial, or compliance claim is made unless that offer has a separate approved policy.
Offers and pricing
A consultant should publish a simple menu: one optional free intro and paid sessions with clear durations and rates. Money rules stay visible because paid sessions are confirmed only from server-side payment proof.
- Free intro is enabled or disabled intentionally, with a configured duration.
- Paid durations and BZD rates are configured as offer data, not hardcoded copy.
- Payment-provider mode, hosted checkout, QR/payment links, refund handling, and WOP paths are clear before claiming live paid booking.
Availability and policy
Availability needs to be operational, not aspirational. The public page should only offer slots created from known timezone, weekly windows, buffers, minimum notice, blackouts, and confirmed-booking conflicts.
- Regular weekly windows are configured in the consultant timezone.
- Minimum notice, reschedule window, cancellation window, and buffer rules are set as policy data.
- Known blocked dates and seasonal constraints are recorded before promotion.
Client handoff
The client should never wonder where to go after booking. The confirmation pass is the canonical answer, and notifications should repeat the same details instead of sending clients to scattered links.
- Confirmation pass shows session details, unique Beam join path, calendar actions, and policy actions.
- Email and WhatsApp messages should point back to the confirmation pass when provider delivery is live.
- Expired or missing links route to Account recovery and WhatsApp support at 501-672-3021.
Provider gates
Some parts are intentionally gated while Consulta remains MVP-reviewed. A public profile can be useful before every provider is live, but the page must not overclaim what has not been proven.
- Live Silvatech Payments and WOP/SMTP delivery need credentials, callbacks, templates, and smoke proof.
- Connected calendar sync, full consultant accounts, automatic self-publishing, and private/single-use share links remain later gates.
- Legal/privacy/data-policy wording stays visible and draft/open where final approval is still pending.
How to use it
Use this checklist before requesting review, before sharing a profile with a client, and after changing rates, policy, availability, or provider configuration.
- Prospective consultants can gather the required information before using Sign up.
- Operators can use the protected dashboard to configure offers, availability, policies, readiness, and sharing.
- Clients can use public trust pages to understand what is live, what is simulated, and how to recover access.