Microsoft Bot Framework for Skype do not works for other users - frameworks

I've made Bot for Skype with Microsoft Bot Framework
The bot was registered on MS site (now in the review status).
It answered on my messages in the Skype.
when I share it to other users the Skype shows for them:
Messaging unavailable.
Could somebody give me some direction how to found where is problem?

This may depend on how many other users.
Initially Skype will have your bot in a pending state which limits your bot to 100 users. You can go to the Skype bot portal and request that your bot be elevated from that initial status.
If however nobody can get to your bot I would consider:
Do they have the latest skype client with support for bots?
Maybe there's something going on with the bot framework.
If you think the latter, you can send us your bot id at bf-reports#microsoft.com and we can investigate.
--jim

Related

Hangouts Chat bot to post timed message

I can see from this, that a bot can send a message in chat, and if supplied a thread ID that does not exist, will start a new thread and post there. I am wondering if there is a way, given the current REST API or any other compatible with Hangouts, to send a message to a room at a given time of day, rather than when the bot is called or interacted with.
I am working in NodeJS, deploying my project in the GCP.
My apologies for the ambiguity of my question, I am trying to wrap my mind around the GCP environment.
In the bots documentation there are described the three ways in which a bot can send a message to a room. Those are:
Every time the bot is mentioned.
When the bot enters a room for the first time.
When the bot is taken out of the room.
Unfortunately, none of them is a daily message at a given time. If you still have questions, please ask them freely.
We have a working bot (NodeJS based) which sends messages freely. Just use this endpoint https://developers.google.com/hangouts/chat/reference/rest/v1/spaces.messages/create .
Your bot must be invited to the particular space/room for this. You can create threads as well with new and subsequent messages.
We also have bots written in Google Apps Script and there it is also possible.

Facebook Messenger Platform business limitations?

I'm excited about the potential of chatbots automating small business receptions, but there are a few unknowns which I can't seem to find answers for. Even after reading the FB developer website:
https://developers.facebook.com/docs/messenger-platform
If I had a business with many receptionists / admin staff that currently respond to customer requests via text and phone. Can they view the chatbot conversations and potentially (manually) take-over the conversation if the chatbot cannot understand the question? Following that, can the automation be turned-off and the customer just has a standard chat conversation with the multiple receptionists (as a group chat)?
Can they view the chatbot conversations and potentially (manually) take-over the conversation if the chatbot cannot understand the question?
Yes
Following that, can the automation be turned-off and the customer just has a standard chat conversation with the multiple receptionists (as a group chat)?
Yes.
The way I do this is I have the bot turned on for everybody by default, and there's an option within the bot to disable it and contact a human. That will disable the bot and send a message to a staff member who will know they need to respond.
Additionally, I have it so that staff members can disable the bot with no notification to the user, so if a user is known to not want to use chat bot functionality, a staff member can disable it manually and speak with them through messenger as the page as normal.
Commands like disabling the bot, I handle through messenger between a staff member and the chatbot, and it simply checks if your id is part of the staff before doing anything, if you're attempting to perform an administrative action such as disabling the bot for someone.
The implementation of this isn't super simple, but it's not super complicated either.
EDIT: I don't think there's anything built into Facebook that does this, and I expect them to eventually add it, but as for now, you have to handle it in your code in a way similar to how I explained here.

Integrate Facebook messenger into CRM without bot?

we have built a very simple bot that simply passes any message onto our own application. (we want to answer questions asked from our customers to be handled straight from our CRM application for customer service purpose)
Now, the bot is declined with message:
Thank you for your submission. We tested the messenger experience on your associated page and received either no response from your messenger bot or received a human response. Please resubmit with the new, improved version of your bot.
Which raises the question for me: is it even allowed to do human assistance via the messenger API? Or is it bot only? I have read through all the platform policies, use case examples, etc.
So, how do I create the simplest integration? (send message straight through to one of our customer service users?)
Making a bot is easy if you use Wit.ai which is an NLP and speech API. It can integrate with the messenger/graph API. Basically, you send text to wit.ai and it returns the intent. For example: you send "get me a large pizza" to Wit and it returns something like (intent = pizza, size=large, time = now) You could also try api.ai but in my opinion, it is not as good yet.

Options for chat API in V2?

We have an education National Program called "Dale Aceptar"[1], where using a ChatBot creator we teach high school kids basic programing concepts like variables and regular expressions.
One of the key part of it is the kids connecting their chatbot to Facebook chat and let it chat with their friends get feedback.
Also with this software the National university of Cordoba won the "Google Roots in Science and Engineering (RISE) Awards"
I'm part of the team who build the software # Lvklabs.com [2]. Can you please point me some options to have access to the FB chat api after migration to V2 is complete?
Thanks
PDA
[1]http://www.daleaceptar.gob.ar/
[2]http://www.lvklabs.com/#/theproducts
https://developers.facebook.com/docs/chat/
The service and API this document covers has been deprecated with the release of Platform API v2.0. Once version 1.0 is deprecated, chat.facebook.com will no longer be available.
There are no plans to replace the Chat API. But even with the Chat API, i would see 2 problems:
User profiles can only be created for real users. A chat bot is not a real user.
The messages must bei user generated, bot messages would not be allowed.
Not sure if that would be good enough for you, but you could also create a Facebook Page for the bot and use the conversations endpoint: https://developers.facebook.com/docs/graph-api/reference/v2.2/page/conversations
You canĀ“t initiate a conversation, but you can reply: https://developers.facebook.com/docs/graph-api/reference/v2.2/conversation/messages

Facebook Chat limitations

My company develop a product for customer support on Facebook and we want to give the representatives a way to contact the customer via Facebook Chat.
I have read the Chat API documentations and it is not clear whether users MUST be friends on Facebook in order to chat or is it just enough they both installed a Facebook app? more limitations?
any insight will be appreciated.
Thanks in advance for you answers,
Yaniv Hakim
Facebook provides an XMPP port to the outside world while internally it implements MQTT. As per XMPP specs, messaging works between two entities without they being in each other roster list (friend/contact list). However, Facebook seems to have this limitation as part of their own business requirement. I think even GoogleTalk disallows this if two federated entities try to send message to each other without being on the roster list.
In short, yes you can just send the message. You don't need a presence authorization from someone in order to send messages to them (in XMPP world). HOWEVER, some services has a policy of requiring this, despite the fact that this is not mandated by the XMPP specifications.