ccaia_create_support_ticket
ChatGPTUse this when the user wants to submit a request that requires human review. REQUIRED STEPS: 1) Call ccaia_get_ticket_types to get available ticket types and their formFields. 2) For the chosen ticket type, identify the exact field.id values from the formFields array. 3) ONLY use those exact field IDs as keys in the fields object - do NOT add any other fields. Example: if formFields contains [{id: "cancellation_reason", ...}, {id: "account_email", ...}], your fields object must ONLY contain those keys: {"cancellation_reason": "...", "account_email": "..."}. NEVER invent field names like "reason", "effective_date", etc. If no ticket types exist, inform the user that ticket submission is not available. Do not use for questions answerable from the knowledge base. Do not use without user confirmation.
ccaia_create_support_ticket
ChatGPTUse this when the user wants to submit a request that requires human review. REQUIRED STEPS: 1) Call ccaia_get_ticket_types to get available ticket types and their formFields. 2) For the chosen ticket type, identify the exact field.id values from the formFields array. 3) ONLY use those exact field IDs as keys in the fields object - do NOT add any other fields. Example: if formFields contains [{id: "cancellation_reason", ...}, {id: "account_email", ...}], your fields object must ONLY contain those keys: {"cancellation_reason": "...", "account_email": "..."}. NEVER invent field names like "reason", "effective_date", etc. If no ticket types exist, inform the user that ticket submission is not available. Do not use for questions answerable from the knowledge base. Do not use without user confirmation.
ccaia_get_ticket_types
ChatGPTReturns available ticket types with their exact field definitions. MUST be called before ccaia_create_support_ticket. Each ticket type includes a formFields array with field.id values that you MUST use as keys when creating tickets. If the result is empty, ticket creation is not available.
ccaia_get_ticket_types
ChatGPTReturns available ticket types with their exact field definitions. MUST be called before ccaia_create_support_ticket. Each ticket type includes a formFields array with field.id values that you MUST use as keys when creating tickets. If the result is empty, ticket creation is not available.
ccaia_search_knowledge_base
ChatGPTUse this when the user asks questions about CCAIA company policies, procedures, internal processes, guidelines, or documentation. Returns synthesized answers from the knowledge base, with optional web fallback if no KB match is found. Do not use for general web searches, real-time information, or questions unrelated to CCAIA.
ccaia_search_knowledge_base
ChatGPTUse this when the user asks questions about CCAIA company policies, procedures, internal processes, guidelines, or documentation. Returns synthesized answers from the knowledge base, with optional web fallback if no KB match is found. Do not use for general web searches, real-time information, or questions unrelated to CCAIA.
