# Use Last9 AI in Slack > Connect Last9 to Slack and investigate production issues with your team in an incident thread. Source: https://last9.io/docs/ai/slack/ Mention `@Last9` in Slack to ask about your services, alerts, logs, and traces. The assistant replies in a thread, where you can ask follow-up questions and share evidence with your team. ```text @Last9 Investigate HTTP 5xx errors for checkout-api in production over the last 30 minutes. Confirm the service and data source, identify affected routes, and include supporting evidence links. ``` Replace the example service with your own. For a historical incident, give explicit start and end times with a time zone. ## Prerequisites - Check that AI access is enabled for your Last9 organization. An organization admin can open [**AI Settings**](https://app.last9.io/ai-settings) and check **Enable Last9 AI**. - Confirm that the relevant telemetry is available in Last9. - Check that you have permission to install or approve apps in your Slack workspace. - Use a Last9 account with the same email address as your Slack account. Last9 uses your Slack email to identify your account. ## Setup 1. [Sign in to Last9](https://app.last9.io) and open [**Slack App**](https://app.last9.io/slack-app). 2. Click **Connect Slack Workspace**. Allow pop-ups for Last9 if your browser blocks the authorization window. 3. Select the intended Slack workspace, review the requested permissions, and authorize the app. 4. Invite the app to the channel where you want to investigate: ```text /invite @Last9 ``` 5. Mention `@Last9` with a question that includes the service and time window. Check that the response refers to the intended service and environment. The Slack App page shows the workspace connection status. Use **Re-authorize Slack** if you need to renew the app's authorization. :::note Start the setup from the Slack App page in Last9 so the authorization request includes your organization and account details. ::: ## Investigate in a thread Mention `@Last9` in each follow-up, and keep questions for the same incident in the same thread: ```text @Last9 Which requests failed in the incident window? Show a representative request or trace ID and distinguish total counts from sampled logs. ``` ```text @Last9 Check the related traces and logs for the selected request. What is confirmed, which causes are still possible, and what evidence is missing? ``` ```text @Last9 Recheck the last 15 minutes before writing the incident summary. State the exact query window and verify successful requests as well as the error rate. ``` Open the evidence links in Last9 to inspect the query, filters, and time window. For the complete workflow, see [Investigate an incident with AI](/docs/ai/investigate-an-incident/). For team participation, account requirements, and sharing AI Assistant conversations, see [Collaboration mode](/docs/ai/collaboration-mode/). ## Use an alert as the starting point The Last9 Slack app also supports alert notification channels. Configure delivery with [Slack notification integration](/docs/slack-integration/), then mention `@Last9` in the alert's thread and ask it to investigate the alert window. ```text @Last9 Investigate the alert. Use the service and time window in the alert, check supporting telemetry, and list confirmed findings and remaining questions. ``` Installing the app and asking a question does not configure recurring checks. Use [alert rules](/docs/alert-rules/) to define the conditions you want Last9 to monitor. ## Review proposed actions If an investigation proposes a configuration change and presents an approval request, inspect the operation and arguments before approving it. A proposed action or a written recommendation is not evidence that a change has been executed. In the incident summary, state which actions your team performed, which the assistant completed, and which are still proposed. ## Channel access and shared information Invite the app to each channel where you want to use it, including private channels. Anyone with access to the channel can read the answers and evidence posted in a thread, so choose the channel before asking about production telemetry. See [AI data handling](/docs/ai/#privacy-and-security) for what an investigation can include, and contact [support@last9.io](mailto:support@last9.io) for organization-specific requirements. --- ## Troubleshooting | Problem | What to check | | --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | The authorization window does not open | Allow pop-ups for Last9, then click **Connect Slack Workspace** again. | | Slack setup does not complete | Confirm the selected workspace and your permission to install apps. Restart from the [Slack App](https://app.last9.io/slack-app) page in Last9. | | `@Last9` does not reply | Check the workspace connection, invite the app to the channel, and mention it explicitly. Ask an admin to check AI access. | | Last9 does not recognize your account | Confirm that your Slack email matches your Last9 account email. Ask your organization admin to add your account if needed. | | The answer refers to the wrong service | Provide the exact service, environment, and data source, then ask the assistant to confirm them before querying again. | | The answer is incomplete | Ask which queries failed, returned samples, or found no data. Check the time window and follow the evidence links. | | An old answer no longer reflects the incident | Ask for a fresh query window and a new recovery check in the thread. | Please get in touch with us on [Discord](https://discord.com/invite/Q3p2EEucx9) or [Email](mailto:support@last9.io) if you have any questions.