> ## Documentation Index > Fetch the complete documentation index at: https://docs.resolve.ai/llms.txt > Use this file to discover all available pages before exploring further. # Resolve Overview **Guided Tour · Part 1 of 5** Resolve Overview → [Connect an Integration](/connect-an-integration) → [Team Knowledge](/D5xH-team-knowledge) → [Auto Investigations](/auto-investigations) → [Tuning Accuracy](/tuning-accuracy) Welcome to Resolve. This is the first stop in the Guided Tour: a quick look at the **main ways to interact with Resolve** so you know where everything lives before you start onboarding your own systems. New to the product? Read [About ResolveAI](/about-resolve-ai) for the big picture first. The main ways to work with Resolve: 1. [Run alert investigations](#1-run-alert-investigations) 2. [Chat with Resolve about production](#2-chat-with-resolve-about-production) 3. [Add Resolve to ongoing incidents](#3-add-resolve-to-ongoing-incidents) 4. [Monitor deployments and other production tasks](#4-monitor-deployments-and-other-production-tasks) 5. [Interact with the Resolve MCP server and REST API](#5-interact-with-the-resolve-mcp-server-and-rest-api) *** ## 1. Run alert investigations Open **Investigations** from the sidebar. You'll see two tabs at the top: * **Investigations** — completed and in-progress root-cause analyses. * **Alerts** — alerts flowing in from your monitoring tools. From here you can kick off an investigation manually, or set alerts to [auto-investigate](/auto-investigations) as they arrive. You can filter by **team** to narrow the list. Open any investigation to see how Resolve works: * **A team of dynamic agents** collaborate on the investigation. The team scales up and down during the investigation as needed. * **Theories** show the hypotheses the agents explored, which they converged on, and which they ruled out. * **The evidence trail** captures every query and data point the agents used. * **The report** (on the right) summarizes the investigation — typically with sections such as *What happened*, *Root cause*, *Key evidence*, and *Recommendations*, though the exact structure adapts to the investigation. Hover any claim to see its **citations**, and open a citation in a new tab to dig into the underlying metrics or logs. You can **highlight text and ask follow-up questions**, **@-mention a teammate** to pull them in, and use the **Steer** control on the left to redirect an investigation that went down the wrong path. To learn how Resolve decides how deep to go, see [Alert Investigations](/alert-investigation-modes). Resolve can also take action on its findings — see [Mitigation Actions](/mitigation-actions). For the full feature set, see [Features](/features). ## 2. Chat with Resolve about production Chat is the fastest way to ask ad-hoc questions. Ask things like *"What services are running?"* or *"Show me error logs from the payment service in the last hour"* and Resolve answers in plain English, drawing on the full context of your production systems — no query language required. A chat is a lightweight conversation. When a question needs deeper analysis, type **`/rca`** or click **Deep Investigation** in the chat window to escalate it into a full, multi-agent **deep investigation**. See [Alert Investigation Modes](/alert-investigation-modes) for how deep investigations work. You can also chat wherever your team already works. Connect the [App for Slack](/app-for-slack) or [App for MS Teams](/app-for-ms-teams-beta) and treat Resolve like a teammate — ask *"Is there a bad deploy right now? I'm seeing errors in the front end"* right in a channel and get a grounded, evidence-backed answer. See [Workplace Collaboration Tools](/workplace-collaboration-tools-for-team-knowledge) for how chat ties into team knowledge. ## 3. Add Resolve to ongoing incidents When an incident is underway, bring Resolve into the channel where your team is already working. Resolve treats designated [incident channels](/incident-channels) as live investigations — it captures context from the conversation, links, and logs, then runs an autonomous investigation in the background and keeps it updated as the incident unfolds. * **@-mention Resolve** to have it check logs, dashboards, deployments, or PRs with full incident context. * **Catch-up summaries** privately bring new responders up to speed as they join (Slack). * **Postmortem drafts** assemble a timeline, findings, impact, and supporting links when the incident winds down. Set this up with the [App for Slack](/app-for-slack) or [App for MS Teams](/app-for-ms-teams-beta), then see [Incident Investigations](/incident-channels) for the full workflow. ## 4. Monitor deployments and other production tasks Resolve can also work on autopilot. [Tasks](/tasks) let you tell Resolve what to do, when to run, and where to report — using the same investigation abilities it brings to a live incident, but unattended. * **On a schedule** — hourly deploy checks, daily alert digests, weekly reports (interval or cron, in your time zone). * **On events** — watch a Slack or MS Teams channel and act when a matching message appears (e.g. *"watch #deploys for rollbacks and DM me if things trend poorly"*). * **On demand** — one-off checks that run now or at a due time. You create tasks in plain language from a chat, a Slack or MS Teams thread, or the Resolve UI, and each task reports back to a channel, a DM, or its own task page. See [Tasks](/tasks) for the full picture. ## 5. Interact with the Resolve MCP server and REST API For programmatic and agent-to-agent workflows, Resolve exposes a [Resolve MCP Server](/resolve-mcp-server) and a [Resolve REST API](/resolve-rest-api): * Install an [AI Assistant Plugin](/ai-assistant-plugins) to drive Resolve from **Claude Code**, **Codex**, or **Cursor** — pull production context, join investigations, and turn findings into pull requests without leaving your editor. * Connect any MCP client directly, or call the [REST API](/resolve-rest-api) to trigger and query investigations from scripts and dashboards. See the [Developers](/developers) section for everything you can build on top of Resolve. *** ## What's next Now that you know the different ways to interact with Resolve, the next step is connecting Resolve to *your* systems so it can investigate real production data. **Next:** [Part 2 — Connect an Integration](/connect-an-integration)