> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hihobbes.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Why did a Hobbes Slack alert not arrive?

> Separate Slack delivery from the conversation and event your team expects to trigger a notification.

Last reviewed 2026-11-10

Hobbes Slack alerts notify your team about selected conversation activity. A connected Slack workspace does not mean that every conversation sends an alert to every channel.

## Check what you expected

1. Identify the organization, agent, conversation, and approximate time of the expected alert.
2. Check the intended Slack workspace and channel. A support request may use a different destination from a sales notification.
3. Confirm the event you expected, such as live activity or a completed conversation summary.
4. Ask the connection owner to compare the conversation with the selected notification criteria and run the appropriate test.

For example, a fictional sales team receives a test message but no alert from an internal practice conversation. The team checks whether its notification rules include that kind of session before reconnecting Slack.

## Separate delivery from eligibility

| Observation | What to investigate |
| - | - |
| The test message does not arrive | The connection, app access, or selected destination. |
| The test arrives but a session alert does not | The agent, selected event, session eligibility, and completion state. |
| A sales alert arrives but a support alert does not | The destination and criteria for the support workflow. |

A completed summary depends on the conversation completing and its analysis becoming available. A page visit alone does not establish a qualified lead or completed conversation.

After the connection owner makes a correction, run a new matching conversation and verify the result in the intended channel. Share the session reference and observed result through your approved support channel if the problem remains.

## Summary

First check the destination, then check whether the conversation matches the expected event. Verify recovery with a new test rather than an old session.

## Related docs

* Understand notification capabilities. [Integration capabilities](https://docs.hihobbes.com/guides/integration-capabilities.md)
* Check the supporting session. [Conversation intelligence](https://docs.hihobbes.com/guides/conversation-intelligence.md)
* Diagnose CRM delivery separately. [Missing CRM activity](https://docs.hihobbes.com/guides/troubleshoot-crm-sync.md)
* Sign in for notification settings and tests. [Troubleshoot Slack alerts](https://docs.hihobbes.com/customer-hub/troubleshoot-slack-alerts.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.