Thanks for the video. It definitely piqued my interest. I notified another project used both voice flow and flowise- what sorts of use cases would requires this as it looks like a significant overlap although voice flow has better tools for triggers/if else/etc?
email data type (shown at 8:00) is not available in my environment. I'm using Hungarian language for my chatbot, probably this is the cause. Is there any way around to validate user input email address?
@@VoiceflowThat’s right. I can send you a screenshot. I chose the sitemap option just to go along with the tutorial. Anyways keep posting tutorials with the new interface as I want to learn more.
@@getwiser3925 Sorry to hear that. It would be helpful to see a screenshot of the issue. Please send an email to support@voiceflow.com and we will create a ticket for your issue!
capturing name entity dosnt work for me for some reason, im setting up the email capture and name capture block in the exact same way. email works fine but name capture always gives me the reply "sorry i didnt quite get that, please try again." what could the issue be?
You could try adding utterances to your Capture step! In the settings button when you click on the capture step to set your entity, click "Add Utterances" and then start generating different sample phrases where someone might provide there name, with the entity name in its place. For example, an utterance may be, "My name is {First_Name}" or "Yeah, it's {First_Name}." This should help your agent capture names more accurately without just capturing the entire user reply!
The Event step was replaced with the Triggers step on June 10th -- you can read the changelog here: docs.voiceflow.com/changelog/introducing-the-triggers-step-elevate-your-workflow-designs
The "Else" No Match path (if the AI output is not 0) just links to the text block below it that loops back to the Capture Email step to prompt the user one more time!
The event section was deprecated earlier this year and replaced with Triggers! See more here: docs.voiceflow.com/changelog/introducing-the-triggers-step-elevate-your-workflow-designs
