How do we handle emergency or SOS information?
Emergency FAQs should include the support channel, local vendor contact flow, hospital or police escalation guidance, and the expected response window for urgent travel issues.
Clear answers for travelers, curators, and local operators working with Hiddengem Thailand.
Website Owner
Emergency FAQs should include the support channel, local vendor contact flow, hospital or police escalation guidance, and the expected response window for urgent travel issues.
Explain that premium support helps travelers access deeper planning, insider recommendations, and curated vendor coordination. Avoid promising instant confirmation until operations validates availability.
A strong answer should be specific, calm, operationally true, and useful for travelers who want authentic local experiences with premium-level reliability.
Local Experience Curator
Website Owner and Local Experience Curator accounts can review every FAQ group from the backend FAQ CMS before it is visible to guests, vendors, or internal teams.
Use real local context, practical logistics, sustainability notes, and clear next actions for high-intent travelers who want more than a generic travel list.
Look for local ownership, low mass-tourism exposure, meaningful story, safe access, host readiness, and a reason the experience cannot be easily copied from a generic travel list.
Verify access route, host availability, weather sensitivity, language support, restroom access, payment expectations, photo rules, cancellation rules, and emergency contact flow.
Use evidence-based wording. Mention who benefits, what fee reaches the host or community, how group size is controlled, and what behavior guests should avoid.
Start with the traveler concern, add local context, explain what happens on the ground, and end with a practical next step. Avoid generic destination marketing language.
Curators may use field interviews, local vendor notes, Thai travel forums, guest reviews, community pages, and partner updates. Any sensitive local detail should be checked before publishing.
Mention the best season, tide or rain limitations, possible route changes, and the Plan B experience. This helps guests trust the platform before booking.
Explain etiquette, dress guidance, photography rules, artisan payment flow, group size, translation support, and whether guests can purchase directly from the maker.
Use controlled booking capacity, avoid publishing exact sensitive locations when needed, guide guests through vetted hosts, and keep community consent as the main publishing standard.
Repeat visitors already know the famous places. Give them deeper context, slower pacing, lesser-known neighborhoods, host stories, and clear reasons why the experience feels different.
Request review when the answer discusses safety, refunds, medical needs, sacred sites, vulnerable communities, controversial local issues, or promises that affect vendor operations.
Owner Company
Every paid booking should be checked with the local vendor and confirmed to the traveler within 24 hours. If availability is not confirmed, the team should offer a Plan B or refund path quickly.
Check the booking record, Stripe payment status, and customer email first. If payment succeeded but booking status did not update, mark the order for manual review and notify operations.
Website Owner and Local Experience Curator accounts can manage FAQs for every profile. Owner Company and Operation Manager accounts can manage only FAQs assigned to their own profile.
Use plain language with timing, eligibility, payment method, and vendor confirmation requirements. Luxury FIT travelers need clarity before payment, especially for weather-sensitive or community-led routes.
No. Owner Company accounts can manage only FAQs assigned to their own profile. This keeps each company responsible for its own service promises and operational answers.
Update inventory as soon as a date is full, blocked, or manually confirmed. If the booking is paid but not confirmed, contact operations before changing the customer-facing answer.
Include hotel lobby timing, driver contact process, vehicle type, waiting policy, baggage limits, meeting point photos if available, and what guests should do if they are late.
Confirm passenger name, flight number, pickup time, drop-off area, luggage count, child seat needs, and after-hours surcharge before the traveler receives final confirmation.
Check pier conditions, tides, local safety advisories, and alternative routes. Offer a safer time, a land-based Plan B, or a cancellation option based on the published policy.
Tell guests where the airport representative waits, what documents they need, whether the service is arrival or departure, and how delays are handled.
Confirm treatment time, therapist availability, room type, gender preference if relevant, cancellation window, and whether hotel transfer is included.
Reply politely, acknowledge the guest experience, explain operational context if needed, and avoid sharing private booking details. Review responses should build trust for future guests.
State pickup airport or delivery point, passport requirement if applicable, activation steps, data package validity, and support channel if the SIM does not activate.
Include pickup cutoff time, delivery window, storage process, luggage size limits, insurance note, and what happens if the hotel cannot receive luggage.
Contact support when inventory conflicts, payment status is unclear, the customer asks for a major route change, safety conditions change, or a local host cannot accept the booking.
Do not change the price for a paid booking unless the customer requests an add-on or the published terms clearly allow the surcharge. Any change must be confirmed with support first.
Operation Manager
Do not publish passport numbers, full phone numbers, private LINE IDs, internal payout rates, private vendor notes, or sensitive customer information. Keep public answers helpful without exposing private data.
Yes. Operation Manager accounts can create, update, and delete FAQs assigned to their own profile. They cannot manage FAQs owned by other company profiles.
Confirm booking ID, customer name, date, service option, vendor contact, guide or driver assignment, pickup details, payment status, and any traveler special requests.
Prepare one realistic alternative for weather, access closure, vendor cancellation, or transport delay. The Plan B should preserve the traveler vibe as much as possible.
Contact the guest through the approved support channel, inform the vendor or driver, record the time, and apply the waiting policy based on the product terms.
Record guide name, phone, language ability, license or vetting status, meeting time, route notes, and whether the guide is company-based or freelance.
Block the date, remove the option from active selling if needed, notify sales or support, and prepare the closest substitute that matches location, budget, and traveler style.
Collect travel date, group size, budget, must-see interests, mobility needs, language preference, and non-negotiables. Then ask the vendor or curator to validate feasibility.
Include pickup and drop-off locations, Google Maps link if available, flight or train number, driver name, vehicle plate, luggage count, and emergency contact.
Record the time, booking ID, issue summary, people involved, immediate action taken, photos or documents if relevant, and whether a refund or goodwill offer is being considered.
Check host availability, dietary restrictions, market timing, prayer or cultural considerations, translation support, hygiene expectations, and transport route.
Ask the curator when the guest wants deeper local context, a route touches a sensitive community, the vendor story needs verification, or the experience should be adjusted for authenticity.