User Profile
peterswimm
MicrosoftJoined 4 years ago
User Widgets
Recent Discussions
Re: Multi-language support
There are two ways you can approach this. In Composer you can have a per language version of your bot's dialogs, but do all the application development in a developer's native language. https://docs.microsoft.com/en-us/composer/how-to-use-multiple-language This could look something like the developer designs the bot in her native language, and then provides the translation resources to a translation team who would port the design to the other languages, each with their own LG and LU content. This allows you to carefully construct bot flows that are relevant to a particular culture. Alternatively, you can also leverage our translation service and its bot sample for a bot that will translate from a users language to your bot's language on the fly: https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/csharp_dotnetcore/17.multilingual-bot This translation model can be monitored and trained based on customer usage: https://docs.microsoft.com/en-us/azure/cognitive-services/translator/custom-translator/how-to-train-model The full list of supported language from this service is here: https://docs.microsoft.com/en-us/azure/cognitive-services/translator/language-support2.7KViews1like2CommentsRe: Capture and analyze logging and telemetry
In our (bot framework) ecosystem, there are lots of ways to accomplish this, but we have not done much in helping customers build their own solutions. Starting this year we are beginning to invest in out of the box telemetry solutions, but the first wave of these will likely be around bot performance and measurement and built with Application Insights in mind, and then move into more sophisticated hosted dashboards like you would see in dynamics or pva https://dynamics.microsoft.com/en-us/ai/customer-insights/ https://docs.microsoft.com/en-us/power-virtual-agents/analytics-overview Again, please feel free to reach out to me directly, would love to hear more about what you are trying to buid,2.4KViews0likes0CommentsRe: Capture and analyze logging and telemetry
Absolutely, we plan to support multiple types of scenarios but will be working from the framework of app insights as to the method for data insights, and along the way people should be able to use those reference materials as a basis for alternative solutions. Would love to hear more about your requirements, please feel free to drop me a line: peterswimm@microsoft.com2.4KViews0likes0CommentsRe: Dialog Interface in Composer
Take a look at this section in the docs, and let us know If you still have questions: https://docs.microsoft.com/en-us/composer/concept-dialog#:~:text=Composer%20integrates%20all%20of%20these%20pieces%20into%20a,how%20the%20bot%20will%20react%20to%20the%20input.1.7KViews0likes1CommentRe: Any estimates on productivity increase from Bot Framework SDK to Bot Composer?
This is a good idea for an internal research topic, I will share it with the team. My experiential data is that the newest version is going to have big improvements to the time it takes to make new flows, update existing ones, and work with a diverse team of people on your bot project.1KViews1like0CommentsRe: Capacity Concerns, Load Testing, and Concurrent Call Limitations on ACS and Bot Framework
With regards to the Telephony channel specifically, At GA, we expect to have a fully scalable platform that can scale to a large enterprise-scale capacity. While in Public Preview, best to provide a bot ID to telephony-preview@microsoft.com alias so that the engineering team could ensure service scaling is happening correctly in real-time depending on the load1.9KViews2likes0CommentsRe: Capacity Concerns, Load Testing, and Concurrent Call Limitations on ACS and Bot Framework
Bot apps are generally just web applications, so the typical load expectations should transfer over, which the bottleneck will locally occur in your Cognitive services calls before the bot tops out. There is also community efforts for load testing such as https://github.com/damadei/BotServiceStressToolkit Note: Please let us know if you are planning any stress tests beforehand! This is something we are looking to invest in soon in terms of providing more guidance and best practices.1.9KViews1like1CommentRe: Recommended Starting Points
There is this https://www.microsoft.com/mea/chatbot-in-a-day/ We have this in our documentation: https://docs.microsoft.com/en-us/composer/concept-best-practices In the upcoming release of Composer, it will ship with a new guided onboarding flow that suggests some bot best practices as well.1.6KViews2likes1CommentRe: Accelerators - close functional gaps
There are a number of big updates coming to the Bot Framework to be released at Build. I would suggest taking a look at the Composer nightly for a preview of some of them, we are currently updating documentation to share with partners when they become GA.2KViews0likes1CommentRe: Capture and analyze logging and telemetry
We recommend using Application Insights to collect your bot channel insights from the bot side: https://docs.microsoft.com/en-us/azure/bot-service/bot-builder-telemetry-analytics-queries?view=azure-bot-service-4.0 You would need to do some work to combine the data you are seeing from ACS with the data generated by the bot (And refer to an ACS team member for more details on that aspect of your stack), but feel free to reach out to me directly and we can find out the best person to do that.2.4KViews1like0CommentsRe: Welcome to the Conversational AI with Bot Framework Composer and the Telephony Channel AMA!
Hello everyone! I am a PM on the MS Composer team, with a focus on analytics and bot success measurement, happy to answer any questions you may have on using the Bot Framework ecosystem.2.4KViews1like1Comment
Groups
Recent Blog Articles
No content to show