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

# New chat

> Start focused analysis quickly, pick the right agent, and turn prompts into actions

<Frame>
  <img src="https://mintcdn.com/atomicai/2EwXzkqhhawPmJOp/images/automation/new-chat/app-new-chat.png?fit=max&auto=format&n=2EwXzkqhhawPmJOp&q=85&s=8a2d216a56fb6d249376f8acf9243400" alt="New chat composer with agent and chat selectors" width="1440" height="1000" data-path="images/automation/new-chat/app-new-chat.png" />
</Frame>

Use New chat when you need a fast answer and a clear next step. This page helps you go from question to action in minutes.

## Questions this page should answer

1. Which agent should handle this request?
2. What prompt format gets an actionable answer?
3. How do you keep context clean across different tasks?

## Before you start

* Pick one clear goal for this chat.
* Know what output you need: diagnosis, action plan, or draft copy.
* Choose whether this should stay ad-hoc or become a workflow later.

## What this page gives you

* A central prompt composer for one-off requests.
* An agent selector to match task type with the right specialist.
* A chat-context selector to continue an old thread or start clean.
* Quick prompt starters for common marketing tasks.

## How the composer is organized

* Main input box: write the task in plain language.
* Agent selector: pick the specialist that should answer.
* Chat selector: choose `New chat` when you want clean context.
* Quick starter chips: launch common requests quickly.

Start with a new chat for analysis work, then continue the thread only if the follow-up is part of the same task.

## Choose the right agent before sending

<Frame>
  <img src="https://mintcdn.com/atomicai/2EwXzkqhhawPmJOp/images/automation/new-chat/app-new-chat-agent-selection.png?fit=max&auto=format&n=2EwXzkqhhawPmJOp&q=85&s=36a8b7639acb97f5a2766e08fe706c47" alt="New chat with General agent dropdown open" width="1536" height="1024" data-path="images/automation/new-chat/app-new-chat-agent-selection.png" />
</Frame>

Agent choice changes output quality more than prompt wording.

* `General agent`: broad planning and mixed questions.
* `SEO performance analyst`: traffic and ranking diagnosis.
* `Technical SEO auditor`: crawl, index, and issue-focused tasks.
* `Content strategist` or `Content editor`: content planning and rewriting.
* `Workflow automation specialist`: requests that should be turned into repeatable flows.

<div className="atomic-info-callout">
  <p>
    <strong>Important:</strong> If output quality is weak, switch the agent
    first before rewriting the prompt.
  </p>
</div>

If the result feels too generic, switch agent first, then retry the same prompt.

## Prompt format that works for marketers

Use this structure:

1. Goal
2. Context
3. Constraints
4. Output format

Example:

```text theme={null}
Goal: Find my top 5 pages losing organic traffic in the last 28 days.
Context: B2B SaaS, focus on non-branded traffic.
Constraints: Prioritize quick wins we can ship this sprint.
Output: Table with page, issue diagnosis, and next action.
```

## When to keep chatting vs start fresh

Start a fresh chat when:

* You switch from SEO analysis to content writing.
* You change site, market, or campaign context.
* You want a clean answer without prior assumptions.

Stay in the same chat when:

* You are refining the same output.
* You are asking follow-up implementation questions.
* You are validating tradeoffs for the same problem.

## Quick execution checklist

1. Pick agent.
2. Write prompt with clear output format.
3. Review answer for direct actions.
4. Convert useful repeated tasks into workflows.

## Keep in mind

* Better inputs produce better outputs.
* One task per prompt keeps answers focused.
* New chat is best for speed; workflows are best for consistency.

## Where to go next

* [Agents](/automation/agents/overview): create and manage specialists
* [Workflows](/automation/workflows/overview): automate repeatable tasks
* [Schedule](/automation/schedule/overview): run audits and workflows on a cadence