Amazing tutorial, thank you!! Maybe a dumb question but can I asign a phone number to the flow that you made for example and have and interaction with the bot using that IA intent playing in prompt the answer of the model bot?
In the tutorial - Phone number is attached to the Amazon Connect Flow (ProductFlow) - which in turn uses Lex Bot. I guess you are asking - if we can we assign Phone Number directly to the Lex Bot (or an Intent)? As of today - I don't see a way to attach a Phone Number directly to a Lex Bot.
@@ArchitectureBytesWell actually what I wanted to see is if there is some way to ask about the products just like you did in the example but through a call. Carching the customer inputs and reproducing the bot responses until you get the goodbyeIntent but all of this in a phone call
The QnA Intent (ProductIntent) is a built-in Gen AI intent, it can answer questions automatically from the Knowledge Base using a foundation model (LLM)
@@ArchitectureBytes @ 5:17 in the video, you have the option to click into the fulfillment area and designate what you want to happen as a next step in the Success Response and others. For example, you can Wait for Users Input or go to Intent, or go to Slot within and Intent, to name a few options. I'm curious about what you've selected because I have the same intent created. Is your next step truly set on nothing? If it's set on Wait for Users Input, I found it interesting that when the user said Thanks, it clicked over to the good bye intent. That's all great and designed well. I'm just curious how you get the QnA intent to break out of AI mode and get back to pre-made intents. Thanks
Ok I understand your question now. For the ProductIntent (QnA Intent) I have not set any specific options in Fulfillment or Closing Response, and there is no Initial Response or Slot options available here. My understanding is that, each user prompt is evaluated independently every-time to determine the most appropriate intent to handle it. However there are scenarios where conversation can get "stuck" - particularly if the intent's fulfillment requires multiple steps or slots to be filled. In such cases, the chatbot may expect the user to provide specific information to complete the current intent before moving on to another one. And if the default behavior is not the best, you can guide the conversation in desired direction by providing 'Next step in Conversation'
@@vikkiechristian Please check the Connect Contact Flow 9:52 - if it has been setup correctly. If it is the same contact flow you are using for both Web Calling (via communications widget) and Phone Call - I would have expected same disconnect behavior for both (over phone and web call). Again check if web call is working fine for you.
Amazing tutorial, thank you!!
Maybe a dumb question but can I asign a phone number to the flow that you made for example and have and interaction with the bot using that IA intent playing in prompt the answer of the model bot?
In the tutorial - Phone number is attached to the Amazon Connect Flow (ProductFlow) - which in turn uses Lex Bot.
I guess you are asking - if we can we assign Phone Number directly to the Lex Bot (or an Intent)? As of today - I don't see a way to attach a Phone Number directly to a Lex Bot.
@@ArchitectureBytesWell actually what I wanted to see is if there is some way to ask about the products just like you did in the example but through a call. Carching the customer inputs and reproducing the bot responses until you get the goodbyeIntent but all of this in a phone call
@@juanpa9590 Yes of course - pls see the demo at 14:55 - Customer Support via Phone Call!
In the QnA Intent, you didn't have a next step? I didn't see one in closing response and the fulfillment box was closed. Thanks for clarifying.
The QnA Intent (ProductIntent) is a built-in Gen AI intent, it can answer questions automatically from the Knowledge Base using a foundation model (LLM)
@@ArchitectureBytes @ 5:17 in the video, you have the option to click into the fulfillment area and designate what you want to happen as a next step in the Success Response and others. For example, you can Wait for Users Input or go to Intent, or go to Slot within and Intent, to name a few options. I'm curious about what you've selected because I have the same intent created. Is your next step truly set on nothing? If it's set on Wait for Users Input, I found it interesting that when the user said Thanks, it clicked over to the good bye intent. That's all great and designed well. I'm just curious how you get the QnA intent to break out of AI mode and get back to pre-made intents. Thanks
Ok I understand your question now.
For the ProductIntent (QnA Intent) I have not set any specific options in Fulfillment or Closing Response, and there is no Initial Response or Slot options available here.
My understanding is that, each user prompt is evaluated independently every-time to determine the most appropriate intent to handle it.
However there are scenarios where conversation can get "stuck" - particularly if the intent's fulfillment requires multiple steps or slots to be filled. In such cases, the chatbot may expect the user to provide specific information to complete the current intent before moving on to another one.
And if the default behavior is not the best, you can guide the conversation in desired direction by providing 'Next step in Conversation'
Very Good
Very nice work..
Great video. We’re building a similar solution and would like your insights in a consulting capacity. How can I reach you?
Hi, why does it terminate the call after saying "I'm here to help you with product"? Did I do something wrong? Pls help
Does it happen when you call over Phone 14:55 or Web Call 15:33? Or both?
@@ArchitectureBytes over phone call
@@vikkiechristian Please check the Connect Contact Flow 9:52 - if it has been setup correctly.
If it is the same contact flow you are using for both Web Calling (via communications widget) and Phone Call - I would have expected same disconnect behavior for both (over phone and web call).
Again check if web call is working fine for you.