You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
one limitation of mailadm's teams bot implementation which might also be relevant for the proper teams bot one day - you can't really start a conversation with another address and have it in a collective chat right now. The collective chats only get created when there is an incoming message.
So maybe interesting would be a bot command which you could execute in the admin group for example, something like:
/message [email protected]
Hi Bob,
long time no see. You still owe our family quite some amount of money.
You don't want one of our "cousins" to drop by, do you?
Make up your mind what type of person you are, the type that stands for their debts or the type that...
doesn't.
The bot would then send the message (minus the first line), create a new group with all the people in the admin group and the receiver as title (so that responses of the receiver end up here), and forward the sent message there as the conversation starter.
The text was updated successfully, but these errors were encountered:
Right now the bot doesn't support being in groups other than the admin group and collective group chats. If we support that one day, we could handle the case that more than one recipient is added in the first line. Until then I would raise an error if more than one argument is given.
one limitation of mailadm's teams bot implementation which might also be relevant for the proper teams bot one day - you can't really start a conversation with another address and have it in a collective chat right now. The collective chats only get created when there is an incoming message.
So maybe interesting would be a bot command which you could execute in the admin group for example, something like:
The bot would then send the message (minus the first line), create a new group with all the people in the admin group and the receiver as title (so that responses of the receiver end up here), and forward the sent message there as the conversation starter.
The text was updated successfully, but these errors were encountered: