The Bot Builder SDK enables you to build bots that support different types of interactions with users. You can design conversations in your bot to be freeform. Your bot can also have more guided interactions where it provides the user choices or actions. The conversation can use simple text or more complex rich cards that contain text, images, and action buttons. You can add natural language interactions and questions and answers, which let your users interact with your bots in a natural way.
The Bot Builder includes a set of command line tools to streamline end-to-end conversation centric development experience, and an emulator for debugging your bot locally or in the cloud.
Bot Builder SDK v4 is the latest SDK for building bot applications. It is in Preview state. Production bots should continue to be developed using the v3 SDK - csharp, node.
It is easy to build your first Bot. You can create a bot with Azure Bot Service. Click here if you need a trial Azure subscription.
You can create a bot with Bot Builder SDK using your favorite language:
Visit azure.com for the primary Azure Bot Service documentation page to learn about building bots using Bot Builder. There is additional documentation on the SDK, oriented towards contributors. The SDK currently supports four programing language:
Bot builder SDK v4 (preview) includes samples for all supported languages:
If you have questions about Bot Builder SDK v3 or v4 Preview or using Azure Bot Service, we encourage you to reach out to the community and Azure Bot Service dev team for help.
- For questions which fit the Stack Overflow format ("how does this work?"), we monitor the both Azure-bot-service and bot framework tags (search both)
- You can also tweet/follow @msbotframework
While we do our best to help out on a timely basis, we don't have any promise around the above resources. If you need an SLA on support from us, it's recommended you invest in an Azure Support plan.
We track functional issues and features asks for and Bot Builder and Azure Bot Service in a variety of locations. If you have found an issue or have a feature request, please submit an issue to the below repositories.
| Item | Description | Link |
|---|---|---|
| SDK v3 (.NET and JS) | core bot runtime, abstractions, prompts, dialogs, FormFlow, etc. | File an issue |
| SDK v4 .net | core bot runtime for .NET, connectors, middleware, dialogs, prompts, LUIS and QnA | File an issue |
| SDK v4 JavaScript | core bot runtime for JavaScript, connectors, middleware, dialogs, prompts, LUIS and QnA | File an issue |
| SDK v4 Python | core bot runtime for Python, connectors, middleware, dialogs, prompts, LUIS and QnA | File an issue |
| SDK v4 Java | core bot runtime for Java, connectors, middleware, dialogs, prompts, LUIS and QnA | File an issue |
| Documentation | Docs for Bot Builder and Azure Bot Service | File an issue |
| CLI tools | MSBot, chatdown, ludown, LUIS, LUISGen, QnA Maker, dispatch | File an issue |
| Emulator | view transcripts, connect to services, debug your bot | File an issue |
- SDK v3 (.NET and node)
- SDK v4 - .NET
- SDK v4 - JavaScript
- SDK v4 - Python
- SDK v4 - Java
- Bot Builder tools
- Bot Builder Emulator
Your bot can provide a great conversational experience without using any Azure Cognitive Services. You can increase your customers' delight with adding a more natural interaction using one or multiple Azure Cognitive Services. The following are common services integrated to bots:
- LUIS
- QnA Maker
- Speech
- Personality Chat - Handles Small-Talk/Chitchat for any bot, in line with a distinct personality.
- all Azure Cognitive Services
Production bots should continue to be developed using the v3 SDK.
Review the documentation to get started with the Bot Builder SDK!
Get started quickly with our samples:
- Bot Builder samples GitHub repo
- More samples are available within the SDK C#, Node.js
Join the conversation on Gitter.
See all the support options here.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.