booking_assistance
ChatGPTPerforms all Paradise Beach booking operations. Use this tool for: - New bookings - Booking modifications - Booking cancellations - Booking confirmations - Booking recaps - Guest list updates - Fun Pass - Day Bed - Top Shelf - Booking availability - Every reply during an active booking or add-on flow Input - Send only the user's latest message in message. - Preserve the user's message exactly as entered. - Do not paraphrase, summarize, normalize, infer, or supplement the message. - Reuse conversationId only when continuing the same booking flow. Tool Responsibilities The tool manages the booking workflow, including: - Conversation state - Required field collection - Validation - Option selection - Booking execution Output Display the complete user-facing response returned by the tool. Option mapping (menus & lists) When a list of selectable options has been presented, intelligently map the user's response to one of the available options. Supported input formats: - Option numbers - 1, 2, #3, option 4 - Exact matches - Partial matches - Synonyms and natural language variants — map casual, colloquial, or emphatic expressions to their closest option (e.g. 'yeah', 'yep', 'for sure', 'absolutely' → Yes | 'nope', 'nah', 'not really' → No) - Intent-based responses Example Available options: Guest List · Fun Pass · Day Beds | User input | Mapped value | |------------|--------------| | 2 | Fun Pass | | option 2 | Fun Pass | | fun pass | Fun Pass | | add passes | Fun Pass | > Send the mapped option value to the tool - not the number. Multilingual handling - Normalize multilingual responses intelligently as per the mapped value. - Example: - “Sí”, “si”, “SI” → “Sí” - “Nope”, “nah” → “No” - Apply the same intent-matching behavior for all supported languages. - If multiple options could match, ask for clarification. - Preserve the exact option wording while making the tool call. MANDATORY SKILL PREREQUISITE This tool is governed by the attached Paradise Beach Concierge Skill (paradise-beach-concierge). BEFORE invoking this tool: 1. Check whether the Paradise Beach Concierge Skill has been loaded and its instructions are available in the current context. 2. If the Skill has not been loaded, load and read its SKILL.md instructions before executing this tool, if Skill access is available. 3. If the Skill was loaded earlier in the conversation, reapply its instructions to the current request. 4. Do not assume that the Skill's instructions remain available merely because they were followed in an earlier message. 5. Apply all Skill rules governing: - MCP tool routing - Conversation continuity - Booking flow isolation - FAQ handling during active flows - Approved information sources - Response preservation - No personalization - No unsupported implications 6. Apply the Skill's response-preservation rules again AFTER receiving the MCP tool result and BEFORE generating the final answer. 7. This prerequisite applies to every tool invocation, including follow-up messages where the user does not @mention the plugin. If the Skill cannot be loaded, do not claim that its instructions were verified. Continue according to applicable available instructions.
booking_assistant
ChatGPTBooking & add-on assistant rules\n\n## Scope\n\nThis tool is meant to assist users with the following booking-related queries thi tool needs to be invoked the user has asked for booking related assistance or is responding to booking flow:\n\n- New bookings\n- Booking modifications\n- Guest list updates\n- Fun Passes\n- Day Beds\n- Top Shelf\n- Booking confirmations\n- Booking cancellations\n- Booking recaps\n\n## Core rules\n\n### Always prioritize the active flow\n\nIf the assistant is currently collecting information for a booking or add-on, treat the user's next message as the answer to the requested field. Do not evaluate the message against menu options until the current flow is completed, cancelled, or explicitly changed by the user.\n\n### Use the user's input exactly as provided\n\nDo not rewrite, paraphrase, infer, normalize, reformat, or modify the user's response. Pass the user's response to the tool exactly as received unless option mapping is required.\n\n## Trigger detection (read before anything else)\n\nBefore evaluating intent or menus, check if the user's message matches any of these\nraw-data patterns and treat it as input to the active flow field immediately:\n\n| Pattern | Examples | Treat as |\n|---|---|---|\n| Phone number (any format) | '3051234567', '(305) 123-4567', '+1 305 123 4567' | Phone number field answer |\n| Date (any format) | 'June 14', '6/14', 'mañana' | Date field answer |\n| Pure number | '4', '12' | Quantity field answer OR menu selection (see Option mapping) |\n| Name only | 'Maria Lopez' | Name field answer |\n\n> Rule: If an active flow is waiting for a field AND the message matches a pattern\n> above, route it to that field. Do not decline such inputs.\n\n\n## Option mapping (menus & lists)\n\nWhen a list of selectable options has been presented, intelligently map the user's response to one of the available options. Supported input formats:\n\n- Option numbers - '1', '2', '#3', 'option 4'\n- Exact matches\n- Partial matches\n- Synonyms and natural language variants — map casual, colloquial, or emphatic expressions to their closest option (e.g. 'yeah', 'yep', 'for sure', 'absolutely' → Yes | 'nope', 'nah', 'not really' → No)\n- Intent-based responses\n\nExample\n\nAvailable options: Guest List · Fun Pass · Day Beds\n\n| User input | Mapped value |\n|------------|--------------|\n| '2' | Fun Pass |\n| 'option 2' | Fun Pass |\n| 'fun pass' | Fun Pass |\n| 'add passes' | Fun Pass |\n\n> Send the mapped option value to the tool - not the number.\n\n### Multilingual normalization\n- Normalize multilingual responses intelligently as per the mapped value.\n- Example:\n - 'Sí', 'si', 'SI' → 'Sí'\n - 'Nope', 'nah' → 'No'\n- Apply the same intent-matching behavior for all supported languages.\n- If multiple options could match, ask for clarification.\n- Preserve the exact option wording while making the tool call.\n\nDo not infer. Do not paraphrase. Map the user's input to exactly the value in the\nCanonical value column and pass that to the tool.\n\n### Yes / No\n| User says | Canonical value |\n|---|---|\n| yes, yeah, yep, yup, for sure, absolutely, correct, sure, ok, okay, sounds good | 'Yes' |\n| sí, si, SI, Sí, claro, dale, órale, por supuesto, sí claro, sí por favor | 'Sí' |\n| no, nope, nah, never, not really, don't, nope, cancel that | 'No' |\n\n> Critical: 'Sí' (with accent) and 'si' (without) both map to canonical 'Sí'.> Never output 'Yes' for Spanish affirmatives. Preserve the language of the session.\n\n## One add-on at a time\n\nComplete the current add-on before starting another. Follow this sequence:\n\n1. Collect required information\n2. Make tool call\n3. Wait for successful confirmation\n4. Only then allow another add-on\n\n## No context bleeding\n\nNever carry values from one add-on or booking action into another. Each add-on must be treated as a separate, independent flow.\n\n## Clarification\n\n- If multiple options could match the user's intent, ask for clarification.\n- If no valid match exists, politely ask the user to clarify.\n\n## Prior…
send_message
ChatGPTSend a message to the chatbot and receive a response based on the predefined FAQ data, such as questions related to Paradise Beach Cozumel, greetings, or fetching availability or weather related details, day pass availability, pharmacy related details, also help with clear session data.
