I have created a custom cortana skill using bot frame work.My channel name or invocation phrase is "S********O".When I tried to invoke Cortana skill in Windows Phone, it doesn't invoke the skill. Instead, it keeps directing me to Bing results.
I invoke skill using Ask Keyword Ask "S********O" and it redirects to bing search. Its is working fine in Andriod. Is anyone have idea about this.
There are a few reasons why you get directed to Bing instead of a skill.
The account you are using on the device is not the same one used for development (self publish / default settings)
Your region and/or language settings are not US / en-US in the App
The account you are using is an AAD joined account, not Microsoft account
You've discovered a bug
Related
I created an Azure bot with cognitive services, and enabled the direct speech client and skype channels.
I can talk to the bot using the Direct Speech Client application, but I would like to talk to it from my phone, via Skype. I mean place a call to it not text.
I know MS is deprecating the Skype and all its associated components but they are still available.
When I place a call to the bot i hear a MS Azure message saying "You cannot talk to this bot yet but we are working on it" Is there a way I can get it to work ?
I cannot find the documentation on Github either.
As said in the error message, they are working on it, so currently it is not available
I am trying to develop an agent using DialogFlow. When doing this, it is possible to debug the agent via the link https://console.dialogflow.com/api-client/#/assistant_preview .This (sort of) works as far as it allows me to interact with my agent etc. On the DialogFlow integrations page I can create a "Web Demo". Typing in exactly the same interactions with the web demo when trying to perform user sign in fails, where as on the simulator it works.
This may be similar to Dialogflow Agent works in Google simulator, failed in console and web link
Surely both methods of interaction should work the same way otherwise this is impossible to test with any level of confidence.
User sign-in is an Assistant feature that Dialogflow supports, but it is not a Dialogflow feature.
The Web Demo is just that - a demo. You can use the Dialogflow Detect Intent API and provide your own authentication system through that if that's what you're trying to do.
If you're looking to test just the Dialogflow interaction, you can test that using the simulator on the right hand side of the page.
Is it possible to use Alexa Voice Profile in my custom skill?
Alexa has ability to identify user by voice (but user need to create alexa voice profile (AVP) ) once AVP is created can I use it in my custom skills? I could not find any useful information/documentation/samples about it
It is available but only as developer preview, for exclusive companies/users. More info: link. When it will be a available, they will probably announce it in their blog: link.
So short answer would be: they are working on it, but it is publicly not available.
Just purchased a Google Home and created an app using API.ai, which works fine in the 'Actions on Google' simulator. I don't plan to publish this app (it's very specific to me - it just calls a webhook on my webserver with a couple of entities taken from the command)...but I'd ideally like to use commands (intents) without having to confirm each time that I want to use my app.
I realise I can set my intents as 'triggers', but Google Assistant still asks if I'd like to use [my app name] and I have to confirm. Is there any way to automatically make it use my app if my voice command matches a trigger?
Im trying to make a custom bot in MS Teams.
My Admin has not yet enabled "Sideloading", but I have the option to "Create a Custom Bot", yet I cannot find any information between the differences of these 2 options?
Has the "Custom Bot" replaced sideloading? In which case, how can i connect my bot to my team? Its hosted on azure, but it kept saying "Sorry, there was a problem encountered with your request", when I had it set up using the Custom Bot.
The bot works perfectly, using both the emulator and the bot framework.
A custom bot is not a Bot Framework bot - it's really designed as a simple way to send information from Teams to an external application (Slack calls them "Outgoing Webhooks"). It's not designed for real bot conversations in the Bot Framework sense. The feature (and its limitations) are documented in detail here.
You can't use bots in a team without sideloading - that's what sideloading is for. When you sideload an app that contains a bot - more info here - it registers additional information needed for a bot to work in a team, as well as a record of the consent for that bot to operate in a team.