I'm planning some kind of Google Hangouts bot/integration which is not following premises from code samples at:
https://developers.google.com/hangouts/chat/concepts/
This won't be a "reply-bot" for incoming messages, it will start conversation-chats or rooms proactively to get people in contact.
From my application, I expect to make questions to users like:
"Hello!
John Doe has requested access to your server.
Do you allow him to get access?
(Allowed responses: yes/no)"
So, they guy might reply: "yes"
And all the devops mechanism will be triggered.
Similar use-case for many people (chat room for i.e. the unix team):
(Here no response is expected, just to start room chat)
"Critical incident at our main router detected
All of you where identified as responsible to solve this issue."
I would really appreciate any suggestion or whatever on how to approach this.
Best regards to everyone! :)
Hangout Chat bots are currently not allowed to proactively contact people. They will need a person to add them first before being able to make interactions.
Related
I developed a welcome bot using the Microsoft Bot Framework. I want to add it to Teams. In teams I want the bot to send welcome messages to only certain members belonging to a particular team or group. Please provide me advice or steps how to do it.
You can only send a welcome message to a specific user if that user first contacted your bot. This is done purposefully to minimize the possibility of spam bots being created. Once a user has contacted your bot you can capture the user's Id and, coupled with the conversationId, you can send future (proactive) messages.
Is it possible to add a bot to a personal conversation with other people?
What I would like to provide is the ability to have #bot commands work in a personal conversation with other users.
Today my bot can:
Respond to messages in a team room when called with #bot
Send direct messages and have conversations 1-on-1 with the user.
However I see no way to provide #bot functions in a 1-on-1 chat between two people.
I can add other people to those 1-on-1 chats, but not bots.
We are working on this feature right now - it's not yet possible, but we hope to release it in the next few months.
My company has a policy of only sending passwords via encrypted email. However, that takes a little more effort then just asking and sending a quick message during a thread. Is there a way for Teams to reject a message containing a word, in this case password, and give a rejection message?
Thanks
This isn't a programming related question, so this isn't the place to ask it. I'll answer it anyway though.
We call this "Data Loss Prevention" (DLP) and it's available in some versions of Office 365. We have not yet added it for Teams but it's definitely on the roadmap. Please use "share an idea" via the Feedback (lightbulb) icon at the lower left of Teams and add your vote.
I am making an event organisation platform. Whenever user creates an event, the candidate gets an email notification as well as sms notification asking whether the suggested time fits or not. The problem is that since it is event organisation, there may be more than one occurance of candidate's mobile phone. So I need to have some unique information to identify to which event candidate is responding to.
I have tried identify using Message SID, but then I realised that Message SID is different on reply message.
So my question would be: is there any way to authenticate to which message candidate is replying to?
Hi Twilio developer evangelist here.
Because every message is idempotent, you wouldn't be able to track them just via the call sid. however, there's way to get around that such as passing a code that goes with each message which you can then read, or using cookies.
I think you are probably going to be more successful using cookies, and luckily enough there is an article on twilio's website that describes just how to do that. And because I noticed you're using PHP, I'm pointing you directly to the PHP article on tracking SMS conversations.
Hope this helps you
I am trying out different things with Twilio, but open for other solutions with Nexmo, Tropo or Plivo.
Here's a situation, I am sending an SMS texts from a server to bunch of clients. I can get a status back: like queued, sending, sent, or failed. Here's what Twilio says about SMS sent status:
"Sent" indicates that your message was successfully sent into the SMS
network for delivery. However Twilio does not receive confirmation from
the destination carrier that the message was received, and this is not
a guarantee that the message has reached the intended device.
(https://www.twilio.com/help/faq/sms/what-do-the-sms-statuses-mean)
So, my question is: does Plivo, Tropo or Nexmo (or any other service that I missed) do anything like that? I mean, knowing that an SMS was received either by client directly, or client's carrier would be really important.
PS. I'm not even sure if it is possible
Any help or suggestions would be appreciated.
It's certainly possible with Nexmo - as the other answer and comment state, it's not possible with Twilio & Tropo. Plivo's docs look like their delivery receipts are similar to Nexmo's.
Nexmo sends a delivery receipt if it's supported by the carrier. In the US it's not, but internationally it is supported often. In those cases Nexmo will give your app a callback with a delivery receipt. You can also use the message ID to query for the message status.
This screencast shows checking the DLR from the dashboard, which is really just a UI on top of the API.
Kevin makes the point that this could be difficult if the message is bounced through multiple providers - one of Nexmo's focuses is getting as direct a connection as possible.
[Disclaimer: I do occasional developer evangelism for Nexmo.]
I'm a Tropo customer, and I've asked the same question, and so far, the answer's similar to what Kevin Burke gave for Twilio. It's hard to do, so there's no confirmation at this time. They do give some debugging information in the logs which is helpful with that first-hop negotiation, at least, even if it's hard to retrieve/parse easily. They are working on it, and have been very active adding new features.