> ## 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. # Pulse > Know what changed. 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. ## Quick questions One question, one answer. Paste it as it is. ### How visible are we in AI answers right now? *Quick question* Brand Strength, visibility, share of voice and sentiment in plain words, and your rank. ```text wrap theme={null} Using Oppin, how visible are we in AI answers right now? ``` ### What changed this week? *Quick question* The three biggest moves (yours and competitors') vs last week, or "nothing material". ```text wrap theme={null} Using Oppin, what changed this week? ``` ### Which AI assistant likes us most, and which least? *Quick question* Engines ranked by Brand Strength, thin-data engines flagged. ```text wrap theme={null} Using Oppin, which AI assistant likes us most, and which least? ``` ### Where in the world are we strongest and weakest? *Quick question* Countries ranked, and who leads where you trail. ```text wrap theme={null} Using Oppin, where in the world are we strongest and weakest? ``` ## Workflows A few steps and one useful result. ### Weekly pulse *Workflow · Answer* Know in two minutes what moved this week and whether it matters. ```text wrap theme={null} Using Oppin, give me this week's AI visibility pulse. Compare with last week, name the three biggest changes with numbers, and finish with the two things worth doing this week. If nothing moved much, just say so. ``` * **You get:** Under 400 words: where you stand, three movements with before and after, two actions. * **Why it helps:** Replaces the Monday dashboard tour, and says "quiet week" instead of inventing a story. * **Shortcut:** the [`oppin_weekly_pulse`](https://docs.oppin.ai/mcp/commands#weekly-pulse) command runs the same analysis. * **Take it further:** Notion + Slack; see [Weekly brief to Notion, summary to Slack](https://docs.oppin.ai/mcp/use-cases/reporting.md#weekly-brief-to-notion-summary-to-slack). ### Campaign or launch impact *Workflow · Insight chart* Find out whether a campaign, launch or PR push changed what AI says. ```text wrap theme={null} Using Oppin, did our [campaign] move AI answers? It ran from [start date] to [end date] and targeted [topic]. Chart our daily visibility across the campaign and the same number of days before it, with the campaign period shaded and competitors drawn faintly behind us. Then show which questions and sources carried any change, and tell me how confident we can be. ``` * **You get:** A trend chart where the campaign's effect (or the lack of one) shows at a glance, a before and after table, the questions and new sources behind the change, and a verdict with a confidence note. * **Why it helps:** Answers "did the coverage land in AI?", and refuses to credit the campaign when competitors moved the same way. * **Shortcut:** the [`oppin_campaign_impact`](https://docs.oppin.ai/mcp/commands#campaign-impact) command with output `page` runs the same analysis. ### Portfolio check *Workflow · Answer · For agencies* See which client needs attention without opening each one. ```text wrap theme={null} Using Oppin, check every brand we manage. Which ones had an unusual week: visibility down more than 15%, a competitor up more than 10 points, or a big sentiment swing? Skip the ones that look normal. ``` * **You get:** Only the flagged brands, with what changed and by how much. "All normal" otherwise. * **Why it helps:** One call covers every client; attention goes where it's needed. * **Take it further:** Slack, daily; see [Client updates, one channel each](https://docs.oppin.ai/mcp/use-cases/reporting.md#client-updates-one-channel-each). ### Weekly metrics log *Workflow · Structured data (sheet rows) + Slack when something moved* Add this week's numbers to your tracking sheet, and flag big moves in Slack. ```text wrap theme={null} Using Oppin, add this week's numbers to our AI visibility tracking sheet: Brand Strength, visibility, share of voice, sentiment and rank, one row per brand. If anything moved more than 5 points, post it to #marketing. ``` * **Why it helps:** A running history in the tool the team already charts from. For a full data feed, Oppin's export and API are the better path. * **Needs:** Google Sheets, Slack, connected in your assistant. ### Competitor surge alert *Workflow · Slack message (only when it fires)* A morning Slack alert that fires only when a competitor surges. ```text wrap theme={null} Using Oppin, every morning check whether any competitor gained more than 5 points of share of voice over the last 7 days. If one did, post to #marketing: who, on which assistants, and which of our questions they now win. If nobody did, post nothing. ``` * **Why it helps:** An alert people keep reading because it rarely fires. * **Needs:** Scheduled tasks, Slack, connected in your assistant. ### Sentiment drop alert *Workflow · Slack message (only when it fires)* A morning Slack alert when your sentiment drops, with the answers behind it. ```text wrap theme={null} Using Oppin, every morning compare our sentiment over the last 7 days with the 7 days before. If it dropped more than 5 points, post to #marketing: the drop, the assistant with the worst change, and the three most negative answers with the pages behind them. ``` * **Why it helps:** Catches the negative page while it's still one page. * **Needs:** Scheduled tasks, Slack, connected in your assistant. ## Agent tasks Longer tasks: the assistant investigates and reasons before it writes anything up. ### Visibility drop investigation *Agent · Insight chart + report* Find when a drop started, where it hit, and what changed. ```text wrap theme={null} Using Oppin, investigate the recent drop in our AI visibility. Find when it started and compare the affected period with the one before. Work out whether it's broad or concentrated: which questions, assistants, countries and topics moved, which competitors gained, whether the sources AI reads changed, and whether tone shifted. Write it up like an incident report: what happened, evidence, possible explanations ranked by how well the data supports them, and what to check next. Don't claim a cause the data doesn't show. Chart the daily trend across both periods with the break marked, plus small charts per assistant and per topic showing where it fell. ``` * **You get:** An incident-style report led by the annotated trend, with evidence and next checks. * **Why it helps:** Shows Oppin as an investigation tool, not just a report. * **Shortcut:** the [`oppin_investigate_drop`](https://docs.oppin.ai/mcp/commands#investigate-drop) command with output `page` runs the same analysis. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.