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

# Conversations

> Start and continue Sawmills Agent conversations to investigate telemetry issues, ask follow-up questions, and keep related context in one thread.

## Overview

Conversations are the main way to work with Sawmills Agent. A conversation keeps your question, follow-up messages, files, and results together so you can continue the same investigation over time.

## What You Can Do in a Conversation

Use a conversation to:

* ask a new question
* continue a previous investigation
* attach files or other supporting context
* request a summary or next step
* keep related work in a single history

## Conversation Flow

A typical conversation looks like this:

1. Start with a question or problem statement.
2. Review the response from Sawmills Agent.
3. Add follow-up questions to narrow the answer or request a summary.
4. Continue the same conversation until you reach a useful outcome.

In some cases, Sawmills Agent may ask a follow-up question before returning a final answer.

## Attachments

Conversations can include file attachments. Use attachments when the investigation depends on content that is easier to share as a file than as a message.

Examples include:

* logs or samples
* screenshots
* supporting documents

When you attach a file, continue the same conversation so the follow-up questions stay connected to that context.

## Conversation Titles

Conversations can have titles to make them easier to find later. Titles are useful when you return to an investigation or share it with a teammate.

## When to Start a New Conversation

Start a new conversation when:

* the topic has changed significantly
* you are switching to a different service or incident
* the previous context is no longer useful

If the topic is still related, continue the same conversation instead of starting over.

## Best Practices

* start with a clear question
* include the service, timeframe, or environment early
* keep related follow-up questions together
* ask for a short summary when you are ready to share results