> For the complete documentation index, see [llms.txt](https://trustcenter.syntphony.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://trustcenter.syntphony.com/products/syntphony-ai/conversational-ai-agents.md). # Conversational AI Agents Component Introduction SYNTPHONY CONVERSATIONAL AI is a solution developed by NTT DATA SPAIN S.L.U. belonging to the NTT DATA Europe & Latam group (hereinafter NTT DATA) and designed for for creating and managing virtual agents, uses artificial intelligence with Generative AI to understand and deliver hyper-personalized responses to users. Our tool is developed considering efficiency, security and compliance with the data protection regulations. To learn more, explore our webpage [Syntphony](https://www.syntphony.com/). Main Features: * Improved Customer Experience. * Personalized Brand Engagement. * Reduced Operational Costs. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://trustcenter.syntphony.com/products/syntphony-ai/conversational-ai-agents.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.