How prompt runs become chatlogs

A prompt run is not just a score

A prompt run is the full answer event. It is not only a mention count or a percentage in the dashboard.

CLEA keeps the answer because the wording, sources, competitors, and answer type all matter. A score can tell you that something changed. The chatlog helps explain why.

The full answer is kept

The full answer shows how AI framed the question. It can show a strong recommendation, a weak mention, a missing brand, or a risky claim.

Read the answer before deciding what the metric means.

Saved answer

The full answer matters because wording, sources, and competitors explain the metric.

Sources stay attached

Sources should stay connected to the run. They show which pages or domains shaped the answer.

This matters because a source can explain a competitor mention better than the final answer alone.

Mentions are reviewable later

Mentions can be reviewed later because they are stored with the run.

This lets CLEA compare movement over time instead of treating each answer as an isolated event.

1

Prompt runs

CLEA asks the tracked buyer-style question.

2

Answer is saved

The full chatlog becomes reviewable evidence.

3

Metrics update

Mentions, competitors, and sources feed Analytics.

4

CLEA can inspect

Later chats and workflows can use the saved run.

Chatlogs become the workspace memory

Chatlogs give the workspace memory. They let CLEA look back at what was asked, what was answered, and what changed across runs.

This is what makes the workspace different from manually saving screenshots.

CLEA can inspect old answers

You can ask CLEA to compare older answers with newer answers.

This is useful when a competitor starts appearing more often, when your brand drops out, or when a source pattern changes.

Agents can summarize patterns

Agent prompts can summarize chatlog patterns after scheduled runs.

For example, a weekly agent can review chatlogs and create one suggestion card if a real action appears.

prompt.txtCopy prompt
Compare the latest chatlog with the previous run.
Explain what changed and whether it deserves one suggestion card.

Chatlogs feed analytics

Analytics uses chatlogs to show patterns. The dashboard can summarize mention outcomes, source reads, competitor appearances, and prompt-level gaps.

The analytics are only as useful as the prompt set behind them.

Mention outcomes

Mention outcomes show whether your brand appeared, how often it appeared, and in which prompt contexts.

Source reads

Source reads show which pages or domains influenced answers.

They help explain why certain companies appear and which content types AI systems may trust.

Source read

A read source can explain why the answer trusted a competitor, claim, or page type.

Competitor appearances

Competitor appearances show who wins attention in the same prompt set.

Repeated appearances are stronger evidence than one-off mentions.

Chatlogs feed suggestions

Suggestion cards can be created from chatlog patterns. A card might recommend prompt cleanup, source review, competitor tracking, or a content update.

workflow.txtCopy prompt
Goal: review new prompt chatlogs.
Inputs: latest runs, mention outcomes, sources, competitors.
Steps: find material changes, ignore one-off noise, choose one action.
Output: one suggestion card only if the evidence is clear.

Trust check before using a run

Before using a run as evidence, check whether the prompt was clear and whether the answer matches the question.

If the prompt was weak, keep the chatlog but fix the prompt before using it as a recurring measurement.

Next step

Main website