Make platform rulesvisible, linkable, and actionable

Policies should not sit in hidden PDFs or support replies. The operator platform needs explicit product-facing rules for verification, trust ranking, connectivity, and lead response so every workflow can point back to the standard that governs it.

Start onboarding Book demo

Direct anchors

Core operator standards

These are the base rules that onboarding, connectivity, growth, and release messaging should reference by direct link, not by implication.

Identity & compliance

Verification standards

Every operator account must show legal identity, emergency reachability, and operational legitimacy before the marketplace treats it as trusted supply.

Legal business name, registration number, and primary operating address are mandatory before trust review starts.
Emergency and sales contact channels must belong to the operator team and remain current once the account is live.
Accounts missing beneficial-owner clarity or contact continuity can be paused before payouts are enabled.

Visibility rules

Trust and ranking policy

Operator visibility should reward verified proof, service quality, and execution consistency rather than raw spend alone.

Approved trust evidence, traveler media, and clearer guarantees improve ranking quality faster than generic profile copy.
Response speed, resolution quality, and booking follow-through remain part of the public trust story after onboarding.
Featured boosts amplify qualified supply, but they do not override trust or safety blockers.

Systems readiness

Connectivity and payout standards

Integrations must preserve source attribution, traveler privacy, and settlement transparency so the operator can scale without hidden operational debt.

CRM routing must preserve lead source, urgency, and ownership so operator teams can act without losing commercial context.
Payout providers must stay in a ready state before live settlement traffic is considered healthy.
Webhook and sync blockers need visible fallback procedures, not silent failure states.

Execution policy

Lead response and follow-up SLA

Operator teams are expected to acknowledge qualified demand quickly and close the loop on traveler questions, payment blockers, and post-booking follow-up.

Urgent routed demand should be acknowledged within two hours during operator working windows.
Open follow-ups and payment blockers should not remain unattended when a booking is already qualified.
Repeated queue decay can suppress ranking visibility even when the catalog is otherwise strong.

Where these policies are used

Operator platform sections

Operator onboarding

Activation path, readiness checkpoints, and direct next actions for verified marketplace entry.

Start onboarding

Connectivity

CRM routing, payout readiness, and future inventory sync for operators who need system-level control.

Explore connectivity

Growth hub

Commercial playbooks for trust, routing, visibility, and seasonal Central Asia demand shaping.

Open growth hub

North America demand

How to package, price, and route Central Asia tours for US and Canadian travelers, advisors, and premium group organizers.

Launch NA demand

Product updates

Release notes, launch priorities, and operator-facing changes across trust, campaigns, payouts, and mobile.

See updates