🎯 Why Describing Your Issue Matters
When you reach out for support, the more clearly you describe your problem, the faster our team can identify the root cause and provide a solution. Vague or incomplete descriptions — even when escalated to a human teammate — can lead to delays, repeated back-and-forth, and conversations that end without resolution.
This article walks you through how to identify and communicate your technical issue effectively before or during a support conversation.
🧩 Common Reasons a Problem Goes Unresolved
- The issue was not described beyond a general feeling that something is wrong.
- Only a term or concept was asked about (for example, asking what a CMS is) without connecting it to the actual problem being experienced.
- The conversation moved to agent escalation before the core issue was identified.
- No specific feature, page, or action was mentioned.
If any of these sound familiar, the steps below will help you reframe your request so it leads to a real resolution.
🔍 How to Identify Your Underlying Issue
Before contacting support or requesting a human teammate, take a moment to answer these questions:
- What were you trying to do? For example: publishing content, connecting a CMS, running an automation, or reviewing a report.
- What happened instead? Describe the unexpected result — an error message, missing data, a button that did not respond, or a feature that behaved differently than expected.
- Where in the platform did it happen? Note the specific section. For example, OTTO SEO is accessed from the left sidebar under OTTO SEO → All Sites (SEO Automation) at the URL /seo-automation-v3.
- When did it start? Was this the first time you tried this action, or did it work before?
- What have you already tried? Refreshing the page, reconnecting an integration, retrying a step — include anything you attempted.
💬 What to Say When You Request an Agent
When you open the chat widget and type human teammate, it helps our team enormously if you lead with a brief summary of your issue. Use this simple format:
- I was trying to: [describe the action]
- What happened: [describe the unexpected result or error]
- Where: [name the feature or section, e.g. OTTO SEO, Site Auditor, Link Builder]
- What I already tried: [any steps you already took]
Example: "I was trying to publish an AI-generated article from the OTTO SEO section, but the publish button is greyed out and nothing happens when I click it. I refreshed the page and retried, but the issue persists."
This level of detail allows our teammate to jump straight into troubleshooting rather than spending time gathering basic information.
📖 A Note on Definitions vs. Technical Problems
Our support team is here to solve problems inside the Search Atlas platform. If you ask about a general concept — such as what a CMS (Content Management System) is — that is a helpful starting point, but it is not the same as reporting a technical issue.
A CMS is any platform used to create, manage, and publish digital content, such as WordPress, Webflow, or Shopify. Search Atlas integrates with CMS platforms to streamline content publishing directly from the platform.
If you were asking about a CMS because you are having trouble connecting one to Search Atlas, or because a CMS-related step in a workflow is not working, that is the technical issue worth describing. Sharing that context ensures the conversation moves toward a real fix.
✅ Quick Checklist Before Escalating
- I can name the feature or section where the issue occurred.
- I can describe what I was trying to do and what happened instead.
- I have noted any error messages or unexpected behavior I observed.
- I have tried at least one basic troubleshooting step (e.g. refresh, retry, re-login).
- I am ready to share my account details if asked.
Running through this checklist before or during a chat conversation significantly increases the chance of resolving your issue in a single interaction.
🙋 Still Need Help?
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.