Bot Builder is comprised of SDK and tools that enable you to build and connect intelligent bots that interact naturally wherever your users are talking, from text/sms to Skype, Slack, Office 365 mail and other popular services. You can build bots that converse free-form or your bot can also have more guided interactions where it provides the user choices or possible 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.
Bot Builder provides the most comprehensive experience for building conversation applications and includes the following SDKs and tools:
- Bot Builder V4 SDK
- Bot Framework Emulator (local debugging and visualization of conversations)
- Bot Builder CLI tools (streamlined development, provisioning, and deployment)
- Bot Framework webchat (embeddable and customizable open source web chat control)
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:
A rich set of samples are available at the BotBuilder-Samples repository.
Questions and Help
If you have questions about Bot Builder SDK 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.
Issues and feature requests
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.
|SDK v4 .net||core bot runtime for .NET, 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|
|CLI tools||MSBot, chatdown, ludown, LUIS, LUISGen, QnA Maker, dispatch||File an issue|
|Emulator||Test and debug bots running locally or remote.||File an issue|
|Webchat||Embeddable web chat control for the Microsoft Bot Framework||File an issue|
|SDK v3 (.NET and JS)||core bot runtime, abstractions, prompts, dialogs, FormFlow, etc.||File an issue|
Join the conversation on Gitter.
See all the support options here.
Adding intelligence to your bot
With the power of Azure Cognitive Services, your bots can interact with your customers in more human ways. The following are common services that bots utilize:
- Bot Builder V3 SDK
- Has been migrated to the BotBuilder-V3 repository.
- Bot Framework Emulator
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA. This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact email@example.com with any additional questions or comments.
Reporting Security Issues
Security issues and bugs should be reported privately, via email, to the Microsoft Security Response Center (MSRC) at firstname.lastname@example.org. You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Further information, including the MSRC PGP key, can be found in the Security TechCenter.
Copyright (c) Microsoft Corporation. All rights reserved.
Licensed under the MIT License.