# voice.md

## Communication Style

### Overall Tone and Personality
BotSee's voice is **authoritative, expert, and practical**. We position ourselves as a knowledgeable guide and a data-driven problem-solver for professionals navigating the complexities of AI visibility. The tone is direct, precise, and efficient, prioritizing clarity and actionable insights over casual or overly friendly conversation. We are confident in our expertise and the robust solutions we provide.

### Key Stylistic Elements and Patterns
*   **Direct and Concise:** Sentences are typically straightforward, avoiding fluff or unnecessary jargon. We get straight to the point.
*   **Solution-Oriented:** Content consistently identifies a problem or challenge and immediately presents BotSee as the definitive solution.
*   **Structured and Logical:** We frequently use bullet points, numbered lists, and clear headings to break down complex information, processes, or comparisons into easily digestible formats.
*   **Emphasis on Data and Measurement:** Key terms like "structured measurement," "repeatable," "comparable runs," "rigorous," and "data" are prominent, reinforcing our analytical and evidence-based approach.
*   **Educational and Instructive:** Much of our content takes a "how-to," "what is," or "guide" format, empowering our audience with knowledge.

### Vocabulary Preferences and Word Choices
Our vocabulary is highly **technical and industry-specific**, reflecting our target audience of AI agents, developers, marketers, and strategists. We use terms accurately and consistently.

*   **Preferred Terms:** AI visibility, Generative Engine Optimization (GEO), REST API, LLM monitoring, brand mentions, brand citations, share of voice, queries, prompts, agents, structured data, workflows, automation, test harness, actionable recommendations, diagnostic workflow, evidence gap, positioning work.
*   **Avoid:** Overly informal slang, vague descriptors, or corporate buzzwords that lack specific meaning.

## Content Patterns

### Common Themes and Topics
*   **AI Visibility & GEO:** The core concept of tracking brand presence in AI-generated answers.
*   **Comparative Analysis:** Highlighting how BotSee differs from traditional SEO tools or other AI visibility platforms.
*   **Problem/Solution:** Addressing pain points like "Why is my brand not showing in ChatGPT?" and offering BotSee as the fix.
*   **Practical Workflows:** Step-by-step guides for monitoring, reporting, and optimizing AI visibility.
*   **Automation & Integration:** Emphasizing BotSee's role as infrastructure for agents and its API capabilities.

### Structural Approaches to Content
*   **Problem-Solution Framework:** Clearly state a challenge, then introduce BotSee as the effective solution.
*   **"How-To" Guides:** Detailed, practical instructions for specific tasks (e.g., "How to Track AI Visibility by Country and Language").
*   **Comparative Structures:** Using side-by-side comparisons (e.g., "BotSee vs Semrush") often with bulleted lists highlighting differences and advantages.
*   **Numbered Steps/Workflows:** For outlining processes or recommendations (e.g., "How it works," "Observe, Diagnose, Prioritize").
*   **Demonstrative Examples:** Showing input and output for agent interactions with BotSee to illustrate functionality.

### Call-to-Action Styles and Patterns
Our CTAs are **direct, functional, and explicit**. They guide the user to the next logical step in their journey.

*   **Examples:** "Get Started," "Log in," "Explore the field guides," "install-plugin," "Analyze your site," "Compare against competitors," "Get recommendations."
*   **Pattern:** Often embedded within the flow of content, especially in workflow demonstrations, rather than solely at the end of a page.

## Audience Interaction

### How the Brand Addresses its Audience
We address our audience indirectly, often referring to "teams," "agencies," "clients," or "your agent." The language implies a professional audience seeking a robust, data-driven tool for strategic decision-making. We respect their intelligence and expertise, speaking to them as peers in the technical domain.

### Level of Formality and Relationship Style
The relationship is **expert-to-professional**. We maintain a professional, yet approachable, level of formality. We are not stiff or overly academic, but we avoid overly casual language. Our goal is to educate, empower, and provide valuable tools and insights, fostering a relationship built on trust and utility.

### Engagement and Conversation Patterns
Engagement is driven by demonstrating utility and efficiency. We engage by:
*   Clearly articulating common challenges in AI visibility.
*   Providing concrete, actionable advice and solutions.
*   Illustrating how BotSee integrates into existing workflows.
*   Using examples that resonate with the audience's professional needs.
We are not conversational in a chatty sense, but rather in a direct, instructional, and demonstrative manner.

## Guidelines & Examples

### Do's and Don'ts for Brand Communication

**Do:**
*   Be precise and unambiguous in your language.
*   Focus on the practical benefits and actionable insights BotSee provides.
*   Use technical terms accurately and consistently.
*   Structure content for clarity and scannability (headings, lists).
*   Emphasize data, measurement, and repeatability.
*   Highlight BotSee's role as infrastructure and an API-first solution.

**Don't:**
*   Use vague or overly generalized statements.
*   Adopt an overly casual or informal tone that undermines expertise.
*   Over-promise or make unsubstantiated claims.
*   Use jargon incorrectly or unnecessarily.
*   Create content that feels like a static dashboard without actionable next steps.

### Example Phrases and Expressions that are "On-Brand"
*   "See what AI answers say. Then decide what to do."
*   "Go beyond one-off prompt checks with repeatable, structured measurement your agent can compare over time."
*   "Your agent can ask the questions. BotSee gives it the test harness."
*   "A practical reference for the answer economy."
*   "Prioritized recommendations grounded in keyword gaps, missed sources, and competitor evidence."
*   "BotSee is infrastructure for your agent runtime, not another chat surface."

### Content Types and Formats the Brand Uses
*   **Blog Posts:** Educational guides, "how-to" articles, comparative analyses, problem/solution deep dives.
*   **Marketing Copy:** Product descriptions, feature highlights, value propositions, use case scenarios.
*   **API Documentation:** Technical specifications, integration guides, code examples.
*   **Workflow Demonstrations:** Step-by-step examples of BotSee in action (e.g., agent interaction examples).