integrationsPage.detail.h1

Put guest and ops alerts where your team already looks.

The update arrives in Slack, not in another dashboard.

Your team is already in Slack all day. Connect it and ProhostAI posts the things that need a human — a cleaning that did not happen, a guest asking something the AI would rather not answer alone, a booking worth knowing about — into the channel that owns it.

integrationsPage.detail.overview

Every operations tool eventually asks your team to check one more place. That works for the person who lives in it and fails for everyone else, which is how a maintenance flag sits unread for two days while five people are active in Slack the whole time.

Connecting Slack inverts that. ProhostAI brings the exception to where your team already is: a message in the channel that owns it, with enough context to act on without opening anything. The AI keeps handling the routine work; Slack is where it raises a hand.

It also works as an input. Because the connection is two-way, someone can ask ProhostAI a question from Slack — which property is empty this weekend, whether the Thursday clean was confirmed — and get an answer in the thread, without leaving the conversation they were already having.

integrationsPage.detail.capabilities

Once Slack is connected, ProhostAI works with it in plain language. There is no separate alerts screen to configure — you say what should reach the team, and where.

Read

  • Follow a channelRead recent messages in a channel so the AI has the context a thread has already built up.
  • Answer from the threadSomeone asks in Slack and the AI replies with what it knows about the property, the stay or the task. “Which places are empty this weekend?”

Create & update

  • Post where it belongsSend an update into a specific channel — cleaning issues to the ops channel, booking news to the team one. “Post the check-outs for tomorrow in #ops each evening.”
  • Escalate for a humanFlag the conversations the AI should not close on its own, so somebody sees them while it still matters.
  • Reply in a threadKeep an exchange in the thread it started in rather than splitting it across two tools.

integrationsPage.detail.howToConnect

Slack connects through OAuth against your workspace, so ProhostAI never sees anyone’s password and a workspace admin can revoke it at any time.

  1. 1Open ProhostAI and go to Settings → Connections.
  2. 2Search for Slack and select Connect.
  3. 3Pick the Slack workspace and approve the permissions on Slack’s authorization screen.
  4. 4Invite ProhostAI to the channels it should post in, then ask it to send a test message.

integrationsPage.detail.goodToKnow

ProhostAI can only see and post in the channels it has been invited to. Adding it to a channel is what grants access, and removing it takes that access away again.

Private channels need an explicit invite, the same as any other Slack member.

Connecting Slack does not move your guest inbox into Slack. Guest conversations stay in ProhostAI, where the AI has the full history; Slack is for what your team needs to see.

A workspace admin can revoke the connection at any time from Slack’s app management settings.

integrationsPage.detail.faqTitle

Yes, connecting Slack is included with ProhostAI. You need your own Slack workspace, on any Slack plan including the free tier.

Only the ones it has been invited to. Adding ProhostAI to a channel is what grants access, including for private channels, and removing it revokes that access immediately.

Guest conversations live in ProhostAI, where the AI has the full stay history and can reply on the right channel. Slack is where the team gets alerts, asks the AI questions and picks up anything escalated for a human.

Yes. You tell ProhostAI what should reach the team and in which channel — cleaning problems in one, booking updates in another — rather than receiving one undifferentiated feed.

No. It reads messages in the channels it has been invited to, which is what lets it answer a question in context. It has no access to channels it is not a member of, or to anyone’s direct messages.

Open Settings → Connections in ProhostAI and disconnect Slack, or have a workspace admin remove ProhostAI from the app management section of your Slack settings.

Bring the exceptions to your team