Hi Team,
I’m trying to build a troubleshooting agent for catalog use-cases. I have added steps that the agent should provide to the user in knowledge bases and linked the space to my agent. I want to now integrate the tools and steps that are part of my knowledge bases such that the agent follows the steps, uses the tool and shares the output with the user as the end result.
Can you help me understand how I can do this?
Also, is there an OH session or mechanism for us to connect and seek support?
Hi @Sharvarika,
Welcome to the Quick Suite Community! Since this is a public user forum, we’re unable to provide assistance that involves account-specific details or internal tools. However, I would definitely reach out to AWS Support by creating a support ticket, as they might be able to provide further guidance on integration-related questions and provide next steps.
Thank you!
Hi @Sharvarika,
Hope everything is well! Just checking back in to see if you saw my most recent reply in regard to creating an AWS Support ticket. If you still have any additional questions related to your initial post, please feel free to share them. Any update you’re able to provide within the next 3 business days would be helpful for the community.
Thank you!
Hi Luis,
Apologies for the delay in responding, I was on vacation and am just seeing this now.
I will raise an AWS support ticket for support with integration.
I do have one query or you - I have created separate documents for each issue type and have also provided clear agent instructions. In spite of this, the chatbot hallucinates a lot. It also references other resources available on Amazon platforms (such as wikis) and provides responses which is not what I need. Do you have any guidance on how can I overcome this?
Your support is greatly appreciated!
Thank you!
Hi @Sharvarika,
No worries at all! And in regard to your other question, I am not able to gauge if there is any inherent issue with the chat agent based on hallucination or if that is just intended behavior based on it is developed. For this case, I would recommend trying different approaches until you are able to achieve more consistent behavior, and/or reach out to AWS Support to see if they know of a recurring issue with the chat agent.
Hope this helps!