4X Cheaper than Stack Ai (RelevanceAI Full tutorial & Template) Stack AI alternative

preview_player
Показать описание
🚀 Welcome to ALLMYTE🚀

Hey there! 👋 I’m Taha E.H, with ALLMYTE Global Development Ltd. We use this channel to document our progress and challenges in the AI and wider entrepreneurial world.

🤝 Consultation Services 🤝

Discover What We’re All About:

Connect with me:

Link to Airtable: (copy into your account)

Book a Date with ALLMYTE:

Subscribe!

Join Our Journey 🚀
ALLMYTE rose from the ashes of one of my previous endeavors, ecommerce.
A few years ago, we had one of the fastest growing stores in Canada, the story of how that ended will be told another time. The important aspect which has served me since, is the marketing and business knowledge which has benefitted me ever since. Hopefully through these videos, some may get the lesson without the scar.

A single spark has evolved into a fully fledged software development company amid the AI landscape.

Grab a seat!

🏷️ Tags 🏷️
#chatbots #voiceassistant #voiceflow #airtable #automation #businessautomation #appointmentbooking #bookingbot #voicetech #voiceai #conversationdesign #cx #cxdesign #voiceux #businessconsulting #smallbusiness #entrepreneur #workflowautomation #customautomation #make #integration #googlecalendar #youtubecreator #videodescription #howtomakeavideo #tutorialvideo #tutorial #casestudy #productivity #timemanagement #saas #workflow #liamottley #joshbrown #morningside
Рекомендации по теме
Комментарии
Автор

Would love more videos of using Relevance and other tutorials on it!

shaumsterman
Автор

4X cheaper than Stack AI? Impressive! SmythOS also offers incredible AI solutions with a no-code approach, making AI workflows accessible and efficient. #AI #SmythOS #Innovation

Sandheip
Автор

thank you for introducing relevance AI but I wonder why you use Airtable to parse your data. You might be better off to do an API request to e.g. Botpress > store the result in a temporary object/array > extract relevant data with an AI node. Than we would only store relevant customer Lead information near the end and "flush" all the conversation history. We should only keep the conversation in active memory for the active conversation. If you pass all the data to Airtable it will bottle-neck rather quickly. With your approach google-sheet is preferred since it has an unlimited amount of rows and its free.

awakenwithoutcoffee
Автор

You need to make the screen bigger - it's hardly visible - you've lost a sub!!

delstone
Автор

Did you find any other workaround the memory in Relevance?

henryklunaris