Certification Checklist

March 14, 2018 · View on GitHub

This document captures the certification checklist used by Microsoft and Skype to validate Skype bots submitted for certification.

NumberRequirementNotes
100Bot Profile Information
101Bot Name and Publisher NameYour bot needs to have a clear and descriptive Bot Name and Publisher Name. Do not suffix ‘Bot’ to your bot name unless it is unavoidable and use spacing. E.g.: FooBot should ideally be Foo, or if unavoidable, Foo Bot.
102Privacy Policy and Terms of Use documents published online and referenced by the botYour bot must have links to a valid Privacy Policy and Terms of Use.
103Bot avatar image with non-black and non-white background colorYour bot must have an avatar image. You must not use the standard bot framework avatar. You must not infringe any copyrighted images.
104Bot description explains the purpose of the botYour bot must have a clear and comprehensive description to help users understand its purpose.
200Bot Functionality
201Automatically display a Welcome messageWhen a user adds the bot as a contact, the bot must automatically display a welcome message. This increases user engagement and guides the user to success.
202Display a Help screen when receiving unknown commandsWhenever a user sends any message / command to the bot that the bot doesn’t understand, the bot must respond with a help message, providing usage guidance.
203Bot functionality works correctlyYour bot must function correctly. Bots with obvious broken functionality will be rejected and / or removed from the directory.
204Bot must be fastThe bot must respond to user commands without extensive delays.
205Bot must be mobile-friendlyThe bot must be designed in a way that enables users to be able to interact with it on a mobile device. For example, the bot should not send excessively long individual messages (instead it can send a sequence of several messages). To ensure the bot is mobile friendly, please test on a mobile device (Android or iOS) with the latest versions of Skype.
300Compliance
301Your Bot Submission must PASS Azure Online Service TermsSee Azure Online Service Terms
302Your Bot Submission must PASS Microsoft Channel Publication TermsSee Microsoft Channel Publication Terms