Bookings and stays
Requests, acceptance, payment, check-in, extensions, cancellation and refunds.
Answers and operational guidance for travellers, providers, territories and partners.
Requests, acceptance, payment, check-in, extensions, cancellation and refunds.
Charges, configured fees, receipts, payouts, refunds and payment-status questions.
Stripe Identity, Connect onboarding, missing requirements and verification privacy.
Listings, calendars, rates, messages, provider responsibilities and payouts.
Destination pages, teams, leads, attractions, local services and impact information.
Provider onboarding, capacity, product information, delivery and local-origin rules.
Access, profile roles, privacy, suspicious activity and data requests.
Page errors, email delivery, file upload and dashboard behaviour.
Have the booking code, payment reference or page URL ready when relevant.
The timeline often shows whether an action is waiting for you, the provider or support.
Explain what happened, when, the expected result and any non-sensitive evidence.
Urgent is for time-critical platform incidents, not a replacement for emergency services.
Signed-in users can open a case from the Support area of their dashboard. The requester sees the complete conversation and current status; administrators reply from the network support inbox. Each update creates an in-platform notification and queues an email.
Check spam first, then verify the address in your profile. The case remains visible in the dashboard even if email delivery is delayed.
Do not send identity or banking credentials in the message. Use Stripe-hosted verification or the specific secure document flow indicated.
Each case receives an SLA target based on priority. It is a service target, not an emergency-response guarantee.
Reply from the case history or open a new case when the previous matter is closed and unrelated.