Slack, Teams and Google Chat

What differs between Slack, Microsoft Teams and Google Chat: how the bot receives events, how a form is drawn, and what identifies a thread.

Slack

We would suggest Socket Mode where possible. The bot then needs only outgoing connections, so the bot can run inside a private network beside the agent server, with nothing exposed to the internet. This matters when the agent server is not reachable from outside the company.
Please verify Slack’s request signature on every event.
Answers are best posted in a thread, so that a conversation in Search2o matches a thread in Slack.
The connect flow uses an ordinary link button. Slack has no masked input, so never collect a password or a token in a Slack form.

Teams bots are registered in Azure and receive events over HTTPS. The bot needs a public endpoint, or a tunnel into the company network.
Adaptive Cards suit the connect button, and the input form when an agent asks a question.
Teams identifies a conversation and a reply chain. Both are needed to key the record of which thread belongs to which Search2o conversation.

A Google Chat app receives events over HTTPS or through Pub/Sub. Pub/Sub suits a bot inside a private network, for the same reason as Socket Mode in Slack.
Card messages suit the connect button and the input forms.
Google Chat identifies a space and a thread, and the record is best keyed on both.