Let the team know what needs them.

Notification delivery runs after the domain action commits. If Slack cannot accept a message, the appointment remains valid and the delivery failure can be handled separately.

Transient failures use bounded retries. Terminal conditions such as an archived channel need a person to repair the connection. Retrying cannot restore a channel that no longer exists.

A concise notification helps staff find the relevant business action. Detailed call information belongs in Evarmont’s authenticated dashboard, not in a channel that may have a wider audience.

The destination comes from the connection. Caller-provided content cannot choose a different Slack channel for the message.

Connect through Slack OAuth and choose the destination channel on Slack’s consent screen. Evarmont shows that selection; changing the destination requires reconnecting through the provider flow.

Permission to create and use an incoming webhook for the selected channel. The stored bot credential supports installation health checks and revocation, not reading messages.

This is a one-way notification integration. It does not ingest Slack messages or events, implement slash commands, or offer an interactive Slack bot.

Disconnecting revokes the installation credential and stops further notifications through it. Messages already posted remain in Slack. Archived or unavailable channels require attention rather than endless retries.