This article covers the AI Agent chat, task execution, tool calls, and Atlas Brain behavior. ## **⚠️ Error 1: AI Agent shows no response after I send a message** **What's happening:** The agent connection may have dropped or your session needs a refresh. **Steps to try:** - Check your internet connection — the AI Agent requires a stable, persistent connection. - Refresh the page and try a simple test message ("Hello") to check if the agent is responsive. - Log out and back in to reset your session. - Check remaining AI Agent usage: **Top-right Corner Avatar → Billing → See Usage**. - Contact support if the agent is completely unresponsive across different browsers. ## **⚠️ Error 2: Agent starts a task but stops partway through** **What's happening:** The agent may be waiting for clarification, or a specific tool it needed was temporarily unavailable. **Steps to try:** - Scroll up in the chat — the agent may have asked a question or left a message explaining why it stopped. - Reply with "Continue" or answer any question the agent asked. - Rephrase the request more specifically — "Audit title tags on my homepage" works better than "Fix all SEO issues." - If the agent stopped silently, restate the task in a new message. - Contact support with the conversation transcript if the agent consistently stops at the same point. ## **⚠️ Error 3: Agent recommendations reference issues I already fixed** **What's happening:** The agent is using data from a previous OTTO crawl that predates your fixes. **Steps to try:** - Trigger an OTTO re-crawl: **Left Sidebar → OTTO SEO → Site Audit → Overview (Website Overview) → Recrawl Site.** - After the crawl completes, start a new AI Agent conversation — the agent loads fresh data at session start. - Tell the agent directly: "I've fixed [issue]. Please check the current crawl data." - Mark resolved tasks as complete in the OTTO task list so they don't resurface. - Confirm your fixes are live on the published URL, not just saved in drafts. ## **⚠️ Error 4: Agent says it performed an action but nothing changed** **What's happening:** Some actions are queued rather than executed immediately, or a required integration is missing. **Steps to try:** - Check the OTTO task list for any pending approvals generated by the agent. - Hard-refresh the relevant module (Content Assistant, OTTO, etc.) to see if changes are visible there. - Ask the agent: "Please confirm the exact action you took and where I can verify it." - Check that the required integration is active — some actions require a connected CMS or GSC account. - Contact support with the specific action the agent claimed to perform and where you expected to see it. ## **⚠️ Error 5: Agent responses are too generic and not specific to my site** **What's happening:** The agent needs more context — either from your prompt or from Brand Vault. **Steps to try:** - Be specific in every message — include your domain, target keyword, and specific goal. - Complete your Brand Vault fully: More Features → Brand Vault. - Ask data-driven questions: "Based on my current OTTO audit, what are my top 3 SEO priorities?" - Include your goals: "My goal is 20% more organic traffic in 6 months. Where should I focus?" - Test what context the agent has: "Describe my business as you understand it" — the answer reveals how much Brand Vault context is being used. ## **⚠️ Error 6: Agent isn't using my Brand Vault information** **What's happening:** Brand Vault may not be linked to the current project, or Brand Vault is incomplete. **Steps to try:** - Verify Brand Vault has content in every section: More Features → Brand Vault. - Link Brand Vault to your project: ****OTTO SEO** in the left sidebar → **All Sites** → open your project → **Brand Vault**.** - Start a new chat session — Brand Vault context loads at session start. - Explicitly reference it, even you can type the Vault name. - Contact support if the agent returns no Brand Vault context after completing all sections. ## **⚠️ Error 7: Agent can't access a tool it's trying to use** **What's happening:** The specific tool's underlying service (Keyword Research, Content Assistant, GSC) was temporarily unavailable. **Steps to try:** - Wait 5 minutes and ask the agent to try again. - Check if the relevant module works on its own in the dashboard. - Ask the agent: "Which tool failed? Can you try a different approach?" - Ask the agent to skip the failing step and continue with the rest of the task. - Contact support with the specific task and which step failed. ## **⚠️ Error 8: Complex tasks time out before completing** **What's happening:** Multi-step agent workflows that take more than a few minutes can exceed connection timeouts. **Steps to try:** - Break large tasks into smaller sequential requests across separate messages. - Check if the agent left partial results — often the first few steps completed before the timeout. - Use the agent's checkpointing: "Continue from where you left off" in a new message. - For long-running jobs, ask the agent to provide a status update every few steps. - Contact support if critical multi-step tasks consistently time out at the same step. The AI Agent is not a static tool—it’s a dynamic system that depends on context, data freshness, integrations, and task clarity. Most issues arise not from failure, but from **missing context, outdated data, or overly broad instructions**.