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

# Customer-meeting GEO scenarios

> Anonymized customer and partner meeting patterns mapped to HaloX workflows and reporting outputs.

<Frame>
  <img src="https://mintcdn.com/afterworklab/lupD4-jE5SvWCVgz/images/concepts/page-thumbnails/en-guides-customer-meeting-scenarios.png?fit=max&auto=format&n=lupD4-jE5SvWCVgz&q=85&s=be66a623eb58a035ce2bc572c21d14ca" alt="HaloX Guides page thumbnail summarizing Customer-meeting GEO scenarios in five cards" width="1600" height="900" data-path="images/concepts/page-thumbnails/en-guides-customer-meeting-scenarios.png" />
</Frame>

Customers rarely ask only “What is GEO?” In real sales and onboarding conversations, they ask how AI search affects their brand, channels and reporting work. This guide turns those recurring conversations into anonymized public scenarios.

## What should you prepare before starting?

* Make sure your HaloX workspace and target site are ready.
* Keep GSC/GA4 access and any existing SEO or meeting notes nearby.
* Decide where the output will live: internal note, client report, or weekly operating document.

## How do you verify the result?

| Check              | Healthy state                                               | Next action                                             |
| ------------------ | ----------------------------------------------------------- | ------------------------------------------------------- |
| Workflow completed | The requested audit or reporting task is finished           | Reflect the result in Strategy Map and the right report |
| Priority selected  | The next keyword, page, or content opportunity is clear     | Assign an owner and due date                            |
| Evidence recorded  | The metrics and reasoning can be reused in the next meeting | Track the same signals next week                        |

## What commonly blocks teams?

| Problem                                       | Cause                                                        | Fix                                                      |
| --------------------------------------------- | ------------------------------------------------------------ | -------------------------------------------------------- |
| Scores are visible but next steps are unclear | Metrics were not translated into execution units             | Start from Strategy Map GAP types and priority clusters. |
| It is hard to explain to customers            | Technical signals were not converted into business language  | Add cause, impact, and next action to every report item. |
| Results do not change immediately             | AI answer surfaces need time to recrawl and reassess sources | Track the same prompt set and metrics weekly.            |

## Recurring questions from meetings

| Customer situation               | What they ask                                                                                       | How to explain HaloX                                                                                          | Connected features                               |
| -------------------------------- | --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ |
| Financial or platform business   | “Can we appear in non-brand conversion questions, brand search and non-brand conversion questions?” | Separate brand-defense questions from non-brand conversion questions, then monitor source and citation paths. | Site Audit, Prompt Analysis, Strategy Map        |
| Enterprise communications team   | “Can GEO become an operating and verification system?”                                              | Score owned media, define recurring strategic prompt sets and report evidence for executives.                 | GEO Dashboard, Citation Tracking, Weekly Reports |
| PR or agency team                | “How do we package GEO/AIO for clients?”                                                            | Sell one-page diagnosis<br />2–4 week sprints<br />monthly operations<br />and shared execution.              | Dashboard, Export, Agency guide                  |
| B2B SaaS team                    | “If SEO dropped, should we start with GEO?”                                                         | Recover search foundations first. Then rebuild topic clusters and expand into AI citation monitoring.         | Site Audit, Keyword Clusters, Content Factory    |
| Local or multi-location business | “How do we monitor local questions and branch URLs?”                                                | Select priority branches and URLs before building local prompt sets.                                          | Local GEO guide, Strategy Map, Weekly Reports    |

## 1. Financial/platform: brand plus non-brand conversion questions

For regulated or platform businesses, brand visibility and conversion questions are different jobs.

| Operating axis      | What to do                                                                                     | Where in HaloX                       |
| ------------------- | ---------------------------------------------------------------------------------------------- | ------------------------------------ |
| Brand defense       | Check whether AI answers describe the brand and official services accurately.                  | AVI, citation rate, top AI questions |
| Non-brand expansion | Track “how to,” “best,” “comparison,” and “before signing up” questions.                       | Prompt Analysis, Strategy Map        |
| Trust foundation    | Find weak third-party pages<br />bot-access issues<br />schema gaps<br />or thin explanations. | Site Audit, Web Health               |
| Global/English      | Separate Korean and English assets because source pools can differ by model and locale.        | Content Factory, Citation Tracking   |

> “Showing up for brand search is not the same as being selected in pre-purchase questions. HaloX separates those question sets and checks which sources AI systems use as evidence.”

## 2. Enterprise communications: an operating system, not a lecture

Enterprise teams often need governance and reporting more than a one-off GEO explanation.

| Output                  | What it includes                                                                                | HaloX role                        |
| ----------------------- | ----------------------------------------------------------------------------------------------- | --------------------------------- |
| Current-state diagnosis | Newsroom<br />official site<br />fact sheet<br />English assets<br />and AI-citation readiness. | Site Audit, GEO Dashboard         |
| Comparison axes         | Competitors<br />affiliates<br />owned media<br />YouTube<br />and issue topics.                | Citation Tracking, Share of Voice |
| Strategic prompt set    | Brand<br />leadership<br />issues<br />business<br />global<br />and product questions.         | Prompt Analysis                   |
| Execution backlog       | FAQ<br />fact sheet<br />entity hub<br />English PR templates<br />schema fixes.                | Content Factory, Export           |
| Executive reporting     | Explain why a weakness exists and what changes next month.                                      | Weekly Reports                    |

## 3. PR/agency: package diagnosis into monthly execution

Agencies usually do not need to sell a development project. GEO works better as a differentiated diagnosis and operating package.

| Package            | Client value                                                                | Deliverables                                          |
| ------------------ | --------------------------------------------------------------------------- | ----------------------------------------------------- |
| One-page diagnosis | Makes current risks and opportunities obvious.                              | KPI summary, three weaknesses, ten priority questions |
| 2–4 week sprint    | Turns question clusters into content and channel actions.                   | Prompt set, priority content list, sample rewrite     |
| Monthly operations | Tracks citation rate, competitor mentions, and channel changes.             | Weekly/monthly report, export package                 |
| Shared execution   | Agency executes PR/content while HaloX provides diagnosis and verification. | Role split, execution calendar                        |

## 4. B2B SaaS: recover SEO before expanding GEO

For SaaS teams, the first action is sometimes not a new GEO campaign. It is repairing the search and content structure that AI systems depend on.

<Steps>
  <Step title="1. Find the dropped category keyword">
    Check rankings, titles, meta descriptions and internal links.
  </Step>

  <Step title="2. Rebuild topic clusters">
    Connect definition pages, comparison pages, how-to guides and FAQ pages instead of publishing one-off posts.
  </Step>

  <Step title="3. Expand into adjacent questions">
    After the core topic recovers, move into adjacent problem, alternative and automation questions.
  </Step>

  <Step title="4. Separate mention, source, and citation">
    A brand mention is not the same as being used as evidence or cited with a link.
  </Step>
</Steps>

## 5. Local/multi-location: fix scope before measurement

Local GEO starts with scope: choose the branch, URL and location question set before measuring.

| Question group       | Example                                                  | Content response                                    |
| -------------------- | -------------------------------------------------------- | --------------------------------------------------- |
| Local recommendation | “Best clinic in Gangnam,” “English academy in Seongsu”   | Location landing page, branch FAQ, review structure |
| Before visiting      | “Is parking available?”, “Is English support available?” | Branch fact sheet, hours, access information        |
| Service comparison   | “How to choose this treatment/service?”                  | Comparison table, cautions, selection criteria      |
| International users  | “Korean clinic for foreigners”                           | English guide, global FAQ, channel-specific sources |

## Turning meeting language into public docs

| Internal meeting language                | Public documentation language                                                                                               |
| ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| Specific customer name, domain, or score | Anonymized vertical scenario                                                                                                |
| Prompt                                   | Strategic prompt set / core questions AI receives                                                                           |
| Cluster                                  | Topic or keyword group                                                                                                      |
| Mention/source/citation                  | Name appears / used as evidence candidate / cited as a link or source                                                       |
| Prove revenue attribution                | Start with leading indicators: AI exposure<br />citation rate<br />question share<br />site visits<br />and issue reduction |

## Read next

* [Fan-out search patterns](/en/guides/fan-out-search-patterns)
* [Agency GEO operations](/en/guides/agency-geo-operations)
* [B2B SaaS GEO operations](/en/guides/b2b-saas-geo)
* [Local GEO operations](/en/guides/local-geo-operations)
* [PR and brand AI citations](/en/guides/pr-brand-ai-citations)

## Proposal language by scenario

Customer meeting scenarios should end with decision language: current risk, priority prompt set, next content asset and next-week metric.

| Proposal section    | What to include                                                                      | Related doc                                     |
| ------------------- | ------------------------------------------------------------------------------------ | ----------------------------------------------- |
| Current state       | Weak areas across AVI<br />citation rate<br />source visibility<br />and web health  | [Reading scores](/en/guides/reading-scores)     |
| Priority prompt set | Branded<br />non-branded<br />comparison<br />local<br />and buying-review questions | [Prompt analysis](/en/features/prompt-analysis) |
| Execution asset     | FAQ<br />comparison table<br />entity hub<br />newsroom or blog improvements         | [Content Factory](/en/features/content-factory) |
| Verification        | Weekly movement across the same prompts and citation URLs                            | [Reports](/en/guides/reports)                   |

### How to anonymize cases

Do not publish customer names, real URLs or meeting transcripts. Convert each case into an industry context, question type, HaloX screen and next action.