The ReachLLM Agent

The ReachLLM agent is the built-in assistant for brand visibility work. It behaves less like a chatbox and more like an AEO copilot: it plans multi-step work, searches the live web with sources, runs tasks in parallel when it can, and remembers reusable workflows as skills.

The Agent checks the workspace's current execution-credit balance before each response. Monthly credits and non-expiring top-up credits are combined. If you add credits or upgrade after a response was stopped, the old response remains in the conversation as history, but the warning clears as soon as the live balance can cover that response.

What it can do

The agent can:

Explain visibility, traffic, and GEO results.
Answer questions about your own account: which plan you are on, how many execution credits you have used and have left (including non-expiring top-up credits), your tracked prompt, GEO audit page, and project limits, and which AI models are tracked for you. These come from your live billing record, so they match what Account > Billing shows.
Read connected AI crawler traffic, including crawler totals, top bots, top pages, daily trends, and recent visits for the active brand.
Compare two visibility runs and tell you exactly which prompts gained or lost a mention for a specific AI platform (for example, "which prompts dropped for Perplexity between June 24 and the latest run"), and separate a real lost mention from a platform that simply was not queried that run.
Turn Brand Visibility answers into inline charts for visibility score, share of voice, average rank, mentions, citation rate, trends, and competitor comparisons. Use the metric buttons to change the chart and View data to inspect the values in a table.
Run or inspect audits.
Platform admins can update Brand Visibility model preferences in Account settings or ask the Agent to switch models directly. ChatGPT choices use GPT-5.6 Sol Medium, High, Extra High, or Pro. Gemini choices use Gemini 3.7 Flash, Gemini 3.6 Flash, or Gemini 3.1 Pro. Retired model names are not accepted.
Generate prompts, content, schema, and llms.txt.
Search the live web for current information and cite its sources.
Read connected context from supported integrations.
Read existing website content and publish or prepare changes through WordPress, GitHub, Webflow, or Shopify when connected.
Preserve platform-specific edit details from connected CMS reads, including GitHub paths and SHAs, Shopify asset IDs, and Webflow editable node IDs for targeted component updates.

Generated proposals, contracts, and surveys

The agent can create a GEO proposal as a downloadable PDF and HTML report, create a service agreement in Google Docs, and create a live onboarding survey when the required integration is connected.

Follow-up feedback in the same conversation updates the saved deliverable instead of starting over:

Proposal edits reuse the active proposal and regenerate its PDF and HTML downloads. The edit is scoped to that proposal only, so it does not change the master template, another customer's report, or a future proposal.
Contract edits update the same Google Doc and keep its existing link.
Survey edits update the same live form and keep its existing share link.

You can ask for another change in a later message because the conversation remembers which proposal, contract, or survey is active. Proposal changes also create version history, so you can ask the agent to list or restore an earlier version.

Working in the chat

Attach files (CSV, PDF, text, images) with the plus button. Attached files show as chips on your message; click a chip to preview the content or download the original file. Images are included in the current multimodal Agent turn, while documents are retrieved through the file pipeline.

Working with the agent inside Content Studio

Content Studio uses the same ReachLLM Agent with structured document context. Select a passage and press Command-I (or Control-I) to open the side panel with the selected block, text range, surrounding sections, document ID, and current revision attached. The selection appears as a quoted attachment in the composer and remains visible on the sent message.

The agent can read the draft alongside your approved brand facts, writing style, competitor set, website content, connected search data, and AI visibility research. When a request changes the document, the agent creates a reviewable proposal instead of replacing the article. Accept applies the proposal to the current shared document and records a version. Reject keeps the document unchanged. If the selected text or revision changed while the agent worked, ReachLLM marks the proposal stale and asks the agent to retry against the latest draft.

The embedded Agent uses the same files, voice input, competitor mentions, saved skills, slash commands, Plan mode, connected tools, thinking activity, sources, charts, and follow-up actions as the main Agent page. Each document has one shared Agent conversation, so teammates can watch and continue the same live session while unrelated chats remain separate.

Running a saved skill uses the same composer path as a typed request. The skill keeps the active Plan setting and selected tools, then uses the current document and selected passage as context.

When Plan mode needs approval, the Agent explains the plan first and shows Proceed with the plan or Adjust something below that explanation. Approving a plan does not bypass the document proposal and review controls.

Content Studio also gives the agent dedicated tools to:

list and read Content Studio documents
create a reviewable suggestion against a specific revision
start basic or deep review
read and resolve review findings
find internal links from real website, audit, and Content Studio page context
request a brand-aligned image
move an approved revision through publishing
send an approved, revision-pinned website document to the Website workspace

Comment threads show profile photos, replies, mentions, and who resolved the discussion. The release panel also shows who approved and published the current revision. Review, link, research, and asset tasks can run while teammates continue editing because they create durable findings and proposals instead of locking the document.

Paste long text freely. Anything over a screenful becomes a "Pasted text" attachment chip instead of flooding the composer, and long pasted messages stay collapsed in the thread with a Show more toggle.
Type / to open the command menu: run a web search, turn on Plan mode, or run one of your saved skills.
Type @ to mention your brand or a competitor. This works on the first screen and mid-conversation, in both the Agent page and the floating assistant.
Every answer ends with follow-up suggestions you can click to continue the thread.
The chat follows new text while you are at the bottom. If you scroll up to read, it stops jumping and shows a button to return to the latest.
The same chat is available on the Agent page and in the floating assistant on every other page.

Conversation history

Conversation history is saved separately for each brand. Switching brands shows that brand's chats, and returning to a brand restores its most recent conversation. Scheduled agent runs also create conversations in the same history so you can open the prompt and result later.

If history cannot be reached, the sidebar shows a connection message instead of incorrectly saying that no conversations exist. Refresh the app to retry the connection.

Live progress

While the agent works, it shows plain-English steps such as "Reviewing your brand knowledge," "Comparing visibility reports," or "Preparing your visibility chart" instead of a generic thinking label or raw tool names. Completed steps get a check and read in the past tense; the current step shows the ReachLLM mark. After the answer is ready, the activity summary explains what was completed and how long it took. Click the summary to review the recorded activity details.

Inline Brand Visibility charts

Ask for a trend, a competitor comparison, or a filtered view of your Brand Visibility data. When chart-ready data is available, the answer includes a ReachLLM visualization directly below the explanation. The same chart works on the full Agent page, in the floating assistant, and in a shared chat.

The chart uses the stored Brand Visibility reports behind the answer. It does not estimate missing values. Filters such as lookback period, prompt selection, provider, or prompt type stay attached to the visualization, and the Open link takes you to the full Brand Visibility workspace for deeper analysis.

Competitor comparisons and agent-created visibility reports use the competitors marked Direct in Knowledge Base by default. Share of Voice, rank, comparison tables, and report summaries use that same group so the values match the Brand Visibility workspace. Choose All tracked in Brand Visibility when you deliberately want the broader discovered-company view. Sentiment does not use the page comparison switch. Its Head-to-Head card always compares the brand with one Direct competitor.

In Sources & Opportunities, open Gap Analysis and choose Plan a fix on a missed prompt to send its competitors, AI platforms, and evidence to the Agent. The Agent reviews the gap and proposes the highest-impact content or authority work before making changes.

When the agent explains or reports a Brand Visibility metric, it should include the metric name, exact value, report date or date range, active filters, comparison group, denominator, and calculation basis. A change between two rates should be labeled in percentage points. The agent should not compare competitor sentiment with the brand's sentiment because those values are not produced by the same evaluation method.

Try requests such as:

"Show my share of voice over the last 90 days."
"Compare our visibility with our top three competitors."
"Chart our citation rate for these product prompts."
"How did mentions change between the previous report and the latest one?"

Web search and sources

When you ask about something current (recent news, prices, competitor or industry updates), or when you share a link, the agent searches the live web and grounds its answer in what it finds. The sources appear as clickable chips under the answer, each with the site's icon and a link you can open. You can also force a search from the / menu with /websearch.

Plan mode

For multi-step work the agent lays out a short plan first, shown as a checklist that ticks off as it goes. It decides on its own when a request needs a plan. You can also turn on Plan mode explicitly (the Plan button, or /plan) to have it propose a plan and wait for your approval before doing anything.

For large requests whose parts are independent (for example: audit the site, pull visibility, and compare competitors), the agent runs those parts in parallel so the whole thing finishes faster.

Skills

A skill is a saved, reusable workflow. Ask the agent to "save this as a skill" (give it a name), or save one after it builds a workflow you like. Your skills then appear in the / menu, and you can run one anytime by picking it there or asking for it by name. The agent runs the saved steps and reports the result. Skills are separate from memory: memory is facts the agent recalls about your brand; skills are workflows it executes on demand. You can also ask it to list or delete your skills.

Speed

Quick messages like a greeting get a fast, lightweight reply. Real tasks get the full pipeline with your brand context and reasoning. You do not choose a model; the agent picks the right one automatically.

Grounding

The agent grounds every answer in your full brand knowledge base (brand details, competitors, structured profile, saved facts, and E-E-A-T signals) and your connected integrations when available.

Best uses

Ask the agent for a concrete outcome, such as:

"What should we fix first?"
"Generate schema for this page."
"Create an article for this prompt."
"Search the web for the latest on Generative Engine Optimization and cite sources."
"Save this as a skill called Weekly Visibility Check."
"Open a GitHub PR for this llms.txt update."
"Read my Shopify homepage content before rewriting it."