Fixing unexpected changes from the dashboard or in chat
How you review an AI diagnosis of an unexpected change and approve a fix, through the dashboard or a conversation.
Once the AI has diagnosed an unexpected change and proposed a fix (see How Reqursor fixes unexpected changes with AI), you have two equally valid ways to review it and decide: the dashboard, or a conversation. The underlying decision is the same either way; these are just two doors into it.
From the dashboard
An alert about an unexpected change appears directly in the affected store's health panel, with the AI's diagnosis and its recommendation shown alongside it. From there you can:
- Confirm with one click if the recommendation looks right, or
- Open the detail view to review exactly what changed, and adjust or reject the proposal before deciding.
From a conversation
The same information is available by simply asking:
| You say | The AI does |
|---|---|
| "Why is Store X showing unexpected changes?" | Explains what changed and why it matters. |
| "Fix it" | Proposes the specific fix; you confirm before anything happens. |
| "Show me what changed" | Presents the difference in plain language, not technical details. |
| "Go back instead" | Proposes reverting to a prior version that was working; you confirm first. |
Same gate, either way
Whichever door you use, nothing runs without your confirmation: the same preview-and-confirm gate as anywhere else on the platform.
Why this matters for your agency
- No context switching required. Stay in the dashboard while reviewing multiple stores, or ask a quick question in chat without opening anything.
- Dashboard for browsing, chat for specifics. Use whichever fits the moment: reviewing several stores at once, or asking about one thing.
- The explanation is always plain language. Whether you click into a detail view or just ask, you get a clear answer, not technical jargon.
Where to go next
How Reqursor fixes unexpected changes with AI
Where the diagnosis and proposal you're reviewing actually come from.
Undo: what it restores, and what it doesn't
What "go back instead" actually does to your store.
Understanding unexpected changes
How unexpected changes are found in the first place, and across your stores.
How store health is checked
How the healthy, degraded, unexpected change, failing, and unknown statuses are actually determined for each store.
Undo: what it restores, and what it doesn't
Undoing a change takes a store's design, settings, and technical setup back to an earlier version, but never its orders, products, or media.