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

# Reporting

> Share it with your team and clients. Prompts to paste into Claude or any assistant connected to Oppin.

Paste a prompt into an assistant connected to Oppin ([how to connect](https://docs.oppin.ai/mcp/overview.md)) and replace the parts in \[brackets] with your own. In Oppin, the **MCP** tab of the **Data & MCP** page has the same prompts with your brand and a competitor already filled in.

## Workflows

A few steps and one useful result.

### Leadership update

*Workflow · Answer · For leadership*

A plain-English update a CEO or CMO reads in one minute.

```text wrap theme={null}
Using Oppin, write a 150-word update for our CMO on how AI assistants talked about us this month compared with last month. No jargon. Include where we rank, the biggest improvement, the biggest concern, one competitor move, and one question leadership should think about.
```

* **You get:** One paragraph and three bullets. Rounded numbers, every metric explained in plain words the first time.
* **Why it helps:** Leadership gets the story without learning what share of voice means.
* **Take it further:** Slack DM or email draft.

### Monthly or client report

*Workflow · Deliverable (PDF) · For agencies · For leadership*

A report ready to send, for your own team or a client.

```text wrap theme={null}
Using Oppin, write this month's AI visibility report for [brand], ready to send to [the client / our team]. Plain language, no internal jargon. Sections: summary, how visible we are, competitors, how AI describes us, the sites AI relies on, what changed on key questions, Oppin's recommendations, next steps. Flag anything based on thin data. Make it a PDF with [our logo and colors]: a one-page summary, then the charts.
```

* **You get:** A PDF report with month-on-month numbers and a chart per section, ready to forward.
* **Why it helps:** The draft writes itself from live data; the team adds judgment.
* **Shortcut:** the [`oppin_client_report`](https://docs.oppin.ai/mcp/commands#client-report) command with output `pdf` runs the same analysis.
* **Take it further:** Google Docs or Notion, or a branded HTML page; see [Shareable dashboard page](https://docs.oppin.ai/mcp/use-cases/reporting.md#shareable-dashboard-page).

### Weekly brief to Notion, summary to Slack

*Workflow · Notion page + Slack message*

Your weekly brief saved to Notion, with the headline posted to Slack.

```text wrap theme={null}
Using Oppin, write our weekly AI visibility brief. Save the full brief to Notion as "[date] Weekly AI Brief", then post a three-line summary and the link to #marketing.
```

* **Why it helps:** Slack gets the headline, Notion keeps the history, nobody opens a dashboard.
* **Needs:** Notion, Slack, connected in your assistant.

### Pre-call brief from the calendar

*Workflow · Slack DM or Gmail draft · For sales*

A five-bullet AI visibility brief before each external meeting.

```text wrap theme={null}
Using Oppin and my calendar, every morning look at today's external meetings. For any company we track in Oppin, send me a five-bullet AI visibility brief in Slack before the meeting.
```

* **Why it helps:** The brief shows up without anyone asking for it.
* **Needs:** Google Calendar, Slack or Gmail, connected in your assistant.

### AI visibility next to AI traffic

*Workflow · Insight chart (two stacked charts) · For leadership*

See whether AI visibility and AI referral traffic move together.

```text wrap theme={null}
Using Oppin and [GA4 / Amplitude], put our weekly AI visibility next to sessions and conversions from AI assistants over the last 3 months. Tell me whether they move together, and be clear that this is correlation, not proof. Chart them as two small charts stacked on the same weeks, not one chart with two axes.
```

* **Why it helps:** The first step toward the board-level question, stated honestly.
* **Needs:** GA4 or Amplitude, connected in your assistant.

### Client updates, one channel each

*Workflow · Slack messages + an internal summary · For agencies*

A weekly update in each client's Slack channel, plus one internal summary.

```text wrap theme={null}
Using Oppin, for each brand we manage, post a five-line weekly update to its client Slack channel: visibility, change vs last week, sentiment, one competitor move, one thing worth flagging. Then put all of them in one internal summary for our team.
```

* **Why it helps:** Weekly client comms without a Monday of copy-paste.
* **Needs:** Slack, connected in your assistant.

### Shareable dashboard page

*Workflow · Interactive page · For agencies*

A self-contained page with your map, heatmap and headline numbers, no login needed.

```text wrap theme={null}
Using Oppin, build a self-contained HTML page with a world map of our visibility by country, a topic heatmap against our competitors, and this month's headline numbers. Use [brand colours]. It should open without a login.
```

* **Why it helps:** A link for a meeting or a client, no tool access needed. Numbers are a snapshot, not live.

## Agent tasks

Longer tasks: the assistant investigates and reasons before it writes anything up.

### AI brand audit

*Agent · Deliverable (PDF) · For leadership*

How AI discovers, describes and recommends you, in one document.

```text wrap theme={null}
Using Oppin, run a complete AI brand audit for [brand] over the last 3 months. Cover how AI discovers us (the questions and fan-out queries where we show up or don't), how it describes us (words, tone, differences between assistants), how it recommends us against competitors (overall, by question, by topic, by country), and what it relies on (the sources, our own site's role, the gaps). Start with a half-page executive summary: our strongest points, weakest areas, recurring perception themes, and the three most important opportunities, using Oppin's own recommendations where they fit. Then give the evidence for each. Don't make recommendations the data can't support, and flag anything based on thin data. Deliver it as a PDF with a one-page scorecard up front and one chart per section.
```

* **You get:** A PDF: a one-page scorecard, then the evidence section by section with a chart each. The document to hand a new CMO or client.
* **Why it helps:** A consultant's week of work, grounded in the brand's own answers.
* **Shortcut:** the [`oppin_brand_audit`](https://docs.oppin.ai/mcp/commands#brand-audit) command with output `pdf` runs the same analysis.

### Weekly analyst with memory

*Agent · Notion page + Slack message*

A weekly brief that follows up on what it flagged the week before.

```text wrap theme={null}
Act as our weekly AI visibility analyst, using Oppin. First read last week's brief in Notion, especially its "watch next week" list. Then review this week's data against last week. Report only meaningful changes and investigate the biggest ones (questions, competitors, sources, tone). Write: what changed, why it matters, what happened to last week's watch items, what marketing should consider, and what to watch next week. Save it to Notion as this week's brief and post a short summary with the link to #marketing.
```

* **You get:** A brief that follows up on itself week after week.
* **Why it helps:** The assistant remembers what it flagged, so issues get closed, not repeated.
* **Needs:** Notion, Slack, connected in your assistant.

### Quarterly review: did our work move anything?

*Agent · Deliverable (slides) · For leadership · For agencies*

Which completed recommendations moved anything this quarter.

```text wrap theme={null}
Using Oppin, prepare our quarterly AI visibility review. List the recommendations we marked completed this quarter. For each, check what happened afterwards on the questions, sources and assistants it was meant to affect, and compare with how competitors moved. Say which appear to have helped, which show no change yet, and where it's too early or too thin to tell. End with next quarter's priorities. Make it a slide deck: one slide per completed action and what happened after it.
```

* **You get:** A QBR deck that ties actions to outcomes, with honest confidence levels.
* **Why it helps:** Closes the loop from ask, to action, to result. It relies on statuses being kept current, which recommendation triage and the recommendation board take care of.
* **Take it further:** see [Recommendation triage](https://docs.oppin.ai/mcp/use-cases/tracking.md#recommendation-triage) and [Recommendation board, both ways](https://docs.oppin.ai/mcp/use-cases/tracking.md#recommendation-board-both-ways).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.