Hello! Well, Flowise is super powerful and offers extensive features, some of which are lacking in Stack AI. For instance, Open AI Assistants are easy to use in Flowise, but a significant drawback is the absence of infrastructures. This requires reliance on other tools for hosting the software, adding disk space, etc. If you use the assistant built in FlowiseAI and plan to run it at scale, meaning you want to handle a large volume of traffic, it can become expensive quickly due to subscription fees for the web server, disks, etc. On the other hand, Stack AI comes with a pricing of $199/month. The advantage is that you won't need to pay for any other tools; you don't even need a separate subscription since Stack AI takes care of server downtimes and manages everything in the background to ensure a smooth running process.
Hey men, amazing video! I'm building ine real state bot rn that shoul work like this: the user puts in his preferences about a property (like: 3 bathrooms) and then the bot search for a matching property. After that the bot should send the price, a description, the link to the site and one image of the property. The only thing that the bot is not beeing able to do is to import the correct url for the image. I'm using the URL's+search kb, is that rigth? Do you have any idea on what may be wrong?
Hey Amir, i was wondering how realistic is the token amount stack ai provides? because even with the starter plan which gives you 10,000 runs/month .. isn't it unrealistic since 1 run = 1 response in the chatbot.. and knowing that we build complex bots like lead gen bots for real estate, would mean that 1 conversation could eat up 20 + runs. Is the starter plan enough in your case or you use other plans for your clients?
Hello and thanks for your question. that is accurate to say some models/projects consume more runs that the others. for my client with a few hundred conversations a month 10,000 runs is certainly enough.
@@ChatbotWhizAmir yeah but stack ai says that 1 run = 1 response.. not a conversation. Even a basic bot will produce at least like 5-10 runs for 1 client + you have to pay for API key tokens. Our potential clients organic traffic is 5k a month. Just wondering if we could manage that number. I love the fact that Stack Ai is not as linear as Voiceflow and better in many ways but the pricing is quite astronomic (especially the tokens)... or maybe I'm getting it all wrong :D. Hope to get some clarity on this or maybe you can recommend a better solution. Our main problem is that voiceflow doesn't quite work with a large amount of xml links. We tried adding a pdf with 10k+ links, but Voiceflow doesn't seem to know what's inside those links :/
chatbot with flowise or
chatbot with stack ai
(pros and cons)
PS : pricing remains main point . What u think Amir ?
Hello!
Well, Flowise is super powerful and offers extensive features, some of which are lacking in Stack AI. For instance, Open AI Assistants are easy to use in Flowise, but a significant drawback is the absence of infrastructures. This requires reliance on other tools for hosting the software, adding disk space, etc.
If you use the assistant built in FlowiseAI and plan to run it at scale, meaning you want to handle a large volume of traffic, it can become expensive quickly due to subscription fees for the web server, disks, etc.
On the other hand, Stack AI comes with a pricing of $199/month. The advantage is that you won't need to pay for any other tools; you don't even need a separate subscription since Stack AI takes care of server downtimes and manages everything in the background to ensure a smooth running process.
@@ChatbotWhizAmirloved your response , thank you
Hey men, amazing video! I'm building ine real state bot rn that shoul work like this: the user puts in his preferences about a property (like: 3 bathrooms) and then the bot search for a matching property. After that the bot should send the price, a description, the link to the site and one image of the property. The only thing that the bot is not beeing able to do is to import the correct url for the image.
I'm using the URL's+search kb, is that rigth? Do you have any idea on what may be wrong?
Inaccurate data retrieval right? try using the new RAG feature in stack AI, that should eliminate such issues
Hey Amir, i was wondering how realistic is the token amount stack ai provides? because even with the starter plan which gives you 10,000 runs/month .. isn't it unrealistic since 1 run = 1 response in the chatbot.. and knowing that we build complex bots like lead gen bots for real estate, would mean that 1 conversation could eat up 20 + runs. Is the starter plan enough in your case or you use other plans for your clients?
Hello and thanks for your question. that is accurate to say some models/projects consume more runs that the others. for my client with a few hundred conversations a month 10,000 runs is certainly enough.
@@ChatbotWhizAmir yeah but stack ai says that 1 run = 1 response.. not a conversation. Even a basic bot will produce at least like 5-10 runs for 1 client + you have to pay for API key tokens. Our potential clients organic traffic is 5k a month. Just wondering if we could manage that number. I love the fact that Stack Ai is not as linear as Voiceflow and better in many ways but the pricing is quite astronomic (especially the tokens)... or maybe I'm getting it all wrong :D. Hope to get some clarity on this or maybe you can recommend a better solution. Our main problem is that voiceflow doesn't quite work with a large amount of xml links. We tried adding a pdf with 10k+ links, but Voiceflow doesn't seem to know what's inside those links :/
Is there way or an application that I can use to integrate Stack AI voice assistant with Telegram?
I hope this is resolved by now. sorry for being ridiculously late here
Hi like your content can you show a real estate chatbot?
Thank you, That's a great idea! I will make one.