-
AI CHATBOTS
Howdy!
You’re not alone
For testing purposes, just now, I entered the message: “What are your hours of operation?” into our AI Chatbot - and after 2 days of bot training - 10 minutes have elapsed still with no answer. Details: Screenshot by Lightshot
Hoping Team Elfsight can fix this soon.
Cheers!
One more example: I entered the message: “How many employees do you have?” into our AI Chatbot - and after traning the bot with a Q&A entry for the exact same question - it took the bot two (2) minutes to answer. Details: Screenshot by Lightshot In my opinion, the answer should be provided in 3-6 seconds! Typically, visitors’ attention span and patience level is quite short ![]()
Again, hoping Team Elfsight can fix this soon and/or provide an explanation.
Thank you!
Hello, @David_King and @AeroConsultants ! ![]()
First, welcome to our community, David! ![]()
I think it’s normal that the AI sometimes takes a bit longer to respond. Many AIs can be slower than usual at times. I’m not completely sure about the cause, but I hope the Elfsight team will be able to assist you well! ![]()
Update:
I queried ChatGPT using their latest language model and received the answers noted below.
Based on the information provided, it appears some of the issues highlighted by ChatGPT need to be reviewed and addressed by Team Elfsight (e.g., switch all users from the current GPT-4o-mini language model to GPT-5).
I hope this helps!
Exactly! ![]()
Hi @David_King, welcome to the Community ![]()
Hello to @AeroConsultants and @maxim too – thank you so much for sharing your thoughts!
First, I wanted to let you know that the speed of the Chatbot’s answer is usually 5 - 10 seconds, and it shouldn’t take much longer for it to search for an answer, surely. Two, ten minutes is really long, and I went ahead and investigated what might have happened at the time of your requests.
And indeed, there was a malfunction in our service at the time. We had trouble connecting to our data provider, and this was probably why the widgets took longer to answer you.
Now, the dev team figured out the issue and fixed it all up, so the Bots should behave now ![]()
Could you guys please check if the response time is ok on your end now too? I’d love to hear your feedback after the fix!
