Slack

The Slack connection lets a ThunderPhone agent use selected workspace actions during a phone conversation. An attached agent can list or read channels, search messages, and, when posting permission is enabled, post a message. The practical use is a controlled bridge between a caller and the team already coordinating work in Slack.

This is a live conversational tool connection, not an automatic feed of every call. The agent invokes Slack tools when the conversation and its prompt call for them. For call-event notifications to your own system, use a webhook separately.

What the Slack connection does

Slack is a native app connection under Connections → Apps. An administrator or owner authorizes the account, then controls the operations available through that connection. You may connect multiple accounts when different agents need different workspaces or access boundaries.

Viewing channels and recent messages, and searching messages, are read-style permissions. Posting messages is off by default until you enable it. If posting remains disabled, ThunderPhone does not offer the posting tool to the agent during calls. After reviewing permissions, attach the connection to the relevant agent in the builder; merely connecting the workspace does not change agent behavior.

Prompt instructions should name the situations where Slack is appropriate, define what may be included in a post, and require confirmation before sending information that could be sensitive or difficult to correct.

Typical call flows

Urgent escalation. In an urgent-call routing flow, the agent gathers the approved minimum details and can post them to a designated channel if the posting operation is enabled. Posting an update does not transfer the call or guarantee that a person has seen it, so the prompt should use a separate human handoff path when immediate response is required.

Support context. During support intake and triage, the agent can search accessible messages for internal context when that is an approved source for the answer. If results are incomplete, conflicting, or unrelated to the caller's exact case, it should avoid treating them as authoritative and escalate instead.

Team follow-up. Near the end of a call, the agent can post a concise, confirmed request to a channel. The message should distinguish caller-provided facts from the agent's summary and include only the data the receiving team needs.

Setup outline

Open Connections → Apps in ThunderPhone and choose Slack.
Complete the authorization flow for the intended workspace. Connecting and managing app connections requires an administrator or owner role in the ThunderPhone organization.
Open the connection and review its permission toggles. Leave posting disabled if the agent only needs to find channels or search messages.
Open the agent in the builder and attach the Slack connection under Connected apps.
Update the prompt with the permitted channels or use cases, the facts allowed in a post, confirmation requirements, and the fallback when Slack is unavailable.
Test channel lookup, message search, a permitted post, a denied post, no search results, and a tool error before deploying the configuration.

Operating limits

Slack access does not replace human handoff. A message can create visibility, but it does not establish that a person accepted responsibility or responded within the call. Keep transfers or other staffed escalation routes for cases that require immediate action.

The safest design gives the agent only the operations its call flow needs. Read access and write access serve different purposes; enable each deliberately, and test what the agent does when the requested channel or information cannot be found. The underlying action pattern is described in function calling.