All Docs
a blue background with lines and dots

AI Discovery

Prompt Monitoring

Define the buyer questions you want to track, run them across three AI engine labels, and see how often your brand appears in the responses.

2 min read

Prompt Monitoring is part of the authenticated Revenue Proven workspace. Shawn’s prompt/result history is seeded and unscheduled. Add and Re-run invoke real configured model calls. The page is documented against the current production interface rather than a mockup or an obsolete navigation path.

What this guide covers

Prompt Monitoring manages the buyer questions used to measure how AI engines mention the workspace brand and competitors. The controls and values shown depend on the signed-in workspace, its connected providers, plan entitlements, member role, and any data already synchronized or seeded for demonstration.

Use this article to understand the page’s purpose, where its data comes from, and the safest next action. Revenue Proven separates read-only analysis from explicit mutations so that opening a page never implies that an external write has occurred.

Current product workflow

Prompt Monitoring manages the buyer questions used to measure how AI engines mention the workspace brand and competitors. This screenshot was captured from the current production route while signed in to the populated Shawn Brown demo workspace.

Prompt Monitoring table showing tracked prompts, brands, competitors, active status, and last run time
Prompt Monitoring table showing tracked prompts, brands, competitors, active status, and last run time. Captured from /dashboard/ai-discovery/prompts.

Add a prompt within the plan limit, pause or activate monitoring, and use Re-run only when a fresh model execution is intended. Interface labels and availability follow the current plan, role, connection, and workspace context.

Shawn’s prompt rows and last-run history are seeded with no future schedule. Add and Re-run are real model actions. Confirm the active workspace and understand whether a control reads data, changes local configuration, or calls an external system before using it.

Data, access, and permissions

Shawn’s prompt rows and last-run history are seeded with no future schedule. Add and Re-run are real model actions. Real synchronized values can change after a scheduled sync, while seeded demo rows are deterministic examples and must not be presented as customer benchmarks.

Feature availability is enforced on the server. A button may be hidden or disabled when the workspace lacks the required plan, add-on, OAuth scope, account role, owner permission, or rollout flag. Team membership never bypasses owner-only write guards.

Operational guidance

Before changing anything, verify the active workspace, selected account, date range, provider filters, and saved configuration. If a screen looks incomplete, allow asynchronous charts and grids to finish loading and check Workspace > Connections for sync health.

Use read-only preview, filter, export, and drill-down controls freely. Treat controls labelled Save, Submit, Apply, Resume, Sync, Send, Publish, Delete, Reconnect, or Regenerate as state-changing actions and confirm their effect before continuing.