Klook

Use this when the user wants to find, search, or get recommendations for travel activities, attractions, tours, experiences, events, or food for their trip. When the user's intent constraints match those from the previous conversation turn, maintain the same parsed field values to ensure consistency. Autoset guidance: - sub_categories: Default is "ttd". Prefer specific categories when they clearly apply. Multiple categories allowed. "attractions" — specific venues or tickets: museums, theme parks, zoos, landmarks, admission fees. "tour_experience" — guided or structured activities: SPA, guided tours, diving, hiking, outdoor activities, cooking experiences, tour groups, nature experiences. "food" — dining-related: restaurants, food tours, night market snacks, buffets, cafes. "events" — performances and shows: concerts, exhibitions, musicals, competitions. "ttd" — general/fallback ONLY: itinerary suggestions, shopping, seasonal activities. Rules: If "attractions", "tour_experience", or "food" applies, do NOT include "ttd". When query mentions multiple types (e.g., sights + food), include ALL matching categories. - user_intent_dest_detail examples: "Jing'an Temple" → "China,Shanghai,Shanghai,Jing'an Temple" "Tokyo Disneyland" → "Japan,Chiba,Urayasu,Tokyo Disneyland" - sort: Map user sorting intent to the appropriate value. Prioritize distance intent first. "nearby" / "closest" / "around here" / "near" / "surrounding" / "附近" / "周邊" → distance "cheap" / "affordable" / "budget" / "low price" → price_asc "luxury" / "high-end" / "expensive" → price_desc "best-selling" / "most booked" / "high sales volume" → participants (ONLY for explicit sales/booking volume) "highest rated" / "best reviews" / "top rated" → review_score No clear sorting preference → most_relevant Note: "Top" / "Must-see" / "Best" / "Popular spots" / "recommended" without explicit sales context → most_relevant (NOT participants). - radius_meter: When user mentions "near" / "nearby" / "around" / "附近" / "周邊" a specific place without an explicit distance, set radius_meter to 10000. - product_tags: Exclude geographic locations. Keep compound concepts intact (e.g., "glamping", "beach yoga"). Activity types: dining, water parks, aquariums, themepark, museums & galleries, walking tour, boat cruise tour, one day tour, multiday tour, spa & massage, cooking classes, zip-line, camping & glamping, water sport, nightlife & pub crawls, hot spring, ski tours, golf, photography, shopping, music, etc. Feature attributes: season (winter, cherry blossom), environment (indoor, outdoor), style (adventure, luxury, cultural), services (pick-up, includes lunch), qualifications (Michelin, World Heritage), policies (flexible cancellation). - budget_level_tag: "cheap" / "budget" / "affordable" / "economical" → budget "mid-range" / "moderate" / "standard" → mid-range "luxury" / "expensive" / "high-end" / "premium" / "VIP" → luxury When both price level and sorting are mentioned, set both fields. E.g., "cheap activities" → budget_level_tag=budget AND sort=price_asc. - duration_tag: "within 3 hours" / "1-2 hours" → nature_0to3_hours "half day" / "3-5 hours" → nature_3to5_hours "5-7 hours" / "most of the day" → nature_5to7_hours "full day" / "day trip" / "8+ hours" → nature_full_day "multi-day" / "2 days or more" / "overnight" → nature_multi_day - service_filters_tags: "solo booking" / "1 person" → nature_1person_group "small group" → nature_small_group "free cancellation" / "flexible cancellation" → nature_easy_refund "Klook recommended" → klook_choice "Klook exclusive" → deal_klook_exclusive - service_user_group_tags: References to "child", "kids", or "child-friendly" map to "parent-child". - accessibility_tags: "child-friendly" or "family-friendly" belongs to service_user_group_tags unless accessibility facilities are explicitly mentioned. TEMPORAL RULES: - If current date is before requested month in current year → use current year. - If current date is in/after requested month → use next year. - "next [weekday]": Find the next occurrence of that weekday, then add 7 days. E.g., today = Tue Feb 3 → "next Saturday" = Feb 14 (NOT Feb 7). - "this [weekday]": The upcoming occurrence within the current week. E.g., today = Tue Feb 3 → "this Saturday" = Feb 7. - "today" → current date, "tomorrow" → +1 day, "this weekend" → upcoming Sat-Sun, "next weekend" → Sat-Sun + 7 days. - When ambiguous, default to nearest future date.

TravelDiscover