# Customer Glossary * **Account Setup**: Holds user profile: name, contact information, password. **M**ulti **F**actor **A**uthentication is turned on here. * **Agent**: (1) A human tasked to help a customer inquiry \ (2) AI bot designed to help the user with any and all tasks, enterprise or otherwise related. * **APL**: **A**lexa **P**resentation **L**anguage. Software to used when an App runs on an Amazon Alexa device. * **App**: An AI or text/speech recognition-based system that provides a service to a user. * **App Blueprints**: A pre-built template for an App that contains intents, utterances, methods, etc. Blueprints often only need connection information to be fully functional. * **App Template**: A reusable framework for a custom App. Templates are JSON files that can be created, shared, modified, and converted into a custom app. * **AI**: Computer systems capable of performing complex tasks such as reasoning, making decisions, or solving problems. * **AI Content**: The backend that houses and manages all text training data and RAG-trained content for a specific app/assistant * **Assistant**: An AI or text/speech recognition-based system that provides a service to a user. * **Basic Mode**: Simplified bot creation page for employees * **Blueprints**: See App Blueprints above. * **Bot**: AI system designed to help the user with any and all tasks, enterprise or otherwise related * **Category**: A group of assistants. * **Channel**: The method through which end users experience, interact, or engage with an app or assistant * **Chatbot**: An AI-based service that simulates human conversation. * **Chunk Size**: The maximum number of characters that a chunk can contain. * **Chunk overlap:** The number of characters that should overlap between two adjacent chunks. * **Collections**: List of Blueprints * **Connection Admin**: Page to set Log in configurations for external software such as Amazon, Office 365, etc. * **Content**: All required training and structural data associated with a particular app/assistant is stored, categorized and accessed for use. * **Conversations**: Records of user interactions with an App * **Data Sources**: Web sites, data bases, etc. with will hold information to be used by the bot. * **Description**: Text used to personalize a bot's responses. * **Digital Human**: A life-like avatar representing an AI assistant * **Entity**: Entities are specific pieces of information extracted from user input that represent real-world objects, concepts, or values. For example, if a caller in a flight reservation App states "I want to fly to London", the Entity would be "London" * **Input**: Inputs enable channels (e.g. Alexa or Lex) to pass in Slots (parameters) associated with an Intent that can be pre-processed and mapped to one or more internal method parameters. Inputs can contain multiple Input parameters * **Instruction**: Language used to describe tasks to an assistant. * **Integration**: Makes a connection between an ixHello bot and an external data source, cloud service, web page etc. Account passwords or keys are often entered here. * **Intent:** A user's reasons for interacting with an App. For example, booking a flight, getting weather, etc. Intents should be given a descriptive name, often a verb and a noun, such as “BookFlight". * **Knowledgebase**: A repository for uploaded documents or images for an assistant to scan or use * **Large Language Models:** Systems designed to understand and generate human language. * **Methods**: Instructions on how the bot will treat information retrieved in the search. * **MFA**: (**M**ulti **F**actor **A**uthentication) Security measure that requires that the user submit a code from either their phone or email to continue their task. Turned on under **Account Setup** > **Profile**. * **MultiLingual**: Supporting two or more languages. iX Hello currently has support for English, Korean, Spanish, German, and Portuguese. * **Public Apps**: Shared Apps created by iX Hello users. * **Publish**: Publishing creates the working app. * **Q\&A**: **Q**uestion and **A**nswer * **RAG bot**: **R**etrieval **A**nd **G**eneration bots are AI powered chatbots that provide information based on a pre-defined source such as a web page. * **Session Attributes**: Parameters added to a method to assist in processing. * **Slot**: Slots are place holders for a required component of an utterance. For instance, if a user's intent is to book a flight, they would need to give a destination. The utterance would be written as "I want to fly to \" with \ standing in for any number of possible destinations. * **Slot Type**: Slot types are user defined representations of slots of type custom. Slot Types can be assigned to multiple custom slots and they have a collection of Slot Values and Synonyms. Slot types are given a name, such as "Destination" and have related Slot Values like "Chicago" or "Dallas" and can be assigned to custom slots. * **Studio Mode**: Site to build custom AI bots * **Survey**: Bot designed to retrieve information from a user. A Survey is AI-led rather than user-led. * **Template**: See App Template. * **Tool**: An entity that an assistant uses to help complete a task, such as a calculator. * **Training Contents**: Web sites, text files, etc. supplied to an App to assist with responses. * **Utterance**: Utterances are what you expect the user to say to your Custom App. For example: "Book me a flight" or "I need to make an appointment". * **Web Chat**: A web page feature that allows a user to ask questions and get responses from a human or AI assistant. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ixhello.com/ixhc/customer-glossary.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.