Work Command Center
Use Command Center to make review decisions in the right order, with enough context to know whether a recommendation is safe, urgent, or optional.
Updated 2026-03-27
Quick Answer
Command Center is where you review Prism's highest-priority work in a risk-first order and decide what to approve, reject, or leave alone.
When To Use This
Use this guide when you are processing recommendations, training reviewers, or trying to understand which recommendation states and phases actually matter.
Prerequisites
You need a connected account, a selected marketplace, and Contributor or Admin permissions for approve or reject actions.
Audience
Operators
Estimated Time
12 minutes
Page Type
Workflow
On this page
Use Command Center to make review decisions in the right order, with enough context to know whether a recommendation is safe, urgent, or optional.
Fast Path
Start in Triage, clear the highest-risk lanes first, review one recommendation at a time in the workbench, and verify outcomes in Activity Log rather than assuming approval means completion.
How To Use This
Process work in sequence: Triage, Defend, Attack, Optimize, then Maintain. That order exists to reduce the chance that you scale or polish a problem before stabilizing it.
When you open a recommendation, answer three questions before you approve it:
- Do I understand the evidence behind the recommendation?
- Does the proposed change match the account's current goal?
- Would I still be comfortable with this change if I had to explain it to a teammate tomorrow?
If the answer to any of those is no, slow down. Use the evidence panels, explain-on-demand details, or skip the item until the reasoning is clear.
What To Watch For
Approval is not the same as final success. A recommendation can move from pending_approval to queued, then end as applied, rejected, closed, expired, or superseded. That means the real "did it work?" check often happens after you leave Command Center.
Filtered views can also fool you. A phase can look finished while global work still exists. Before you declare a queue clear, compare filtered counts with the unfiltered backlog.
Common Problems
If a lane looks empty but you know work should exist, clear campaign and type filters first.
If a recommendation appears in an unexpected lane, check the intent. Budget increases belong in growth-oriented work. Budget cuts belong in optimization. Bid changes can land in defensive or scaling contexts depending on why they were generated.
24 Guided Actions
Use this section as a lane-by-lane reference when you need to know what a guided action means, what triggers it, how often it runs, and what acceptance actually does.
Cadence groups:
Monitoringmeans Explorer runs weekly, Starter runs daily, and Growth, Pro, and Enterprise run hourly.Optimizationmeans Explorer runs weekly and Starter plus higher paid tiers run daily.Strategicmeans paid tiers run weekly.
Cadence below is tier-based. Onboarding and full runs can execute all groups regardless of tier.
| Phase | Guided action | What triggers it | Cadence | What you get when accepted |
|---|---|---|---|---|
| Triage | Critical Alerts | Severe risk signals like ACOS spikes, budget exhaustion, or urgent guardrail breaches | Monitoring (tier-based) | Immediate protective fix is queued so you can prevent revenue loss quickly |
| Triage | Legacy Protection | Mature or legacy campaigns that should not be changed aggressively | Strategic (weekly paid tiers) | Campaign is put into protected mode so risky optimization recommendations are no longer generated for it |
| Defend | Downbids | High-spend keywords or targets with poor efficiency | Optimization (weekly Explorer, daily Starter+) | Bids are lowered to reduce waste and protect margin |
| Defend | Negative Keywords | Search terms spending with weak or zero conversion | Optimization (weekly Explorer, daily Starter+) | Blocking negatives are added so low-quality traffic stops triggering ads |
| Defend | Product Page Shield | Competitor pressure on your product detail pages | Strategic (weekly paid tiers) | Defensive targeting is created to help hold your PDP traffic |
| Attack | Upbids | Proven winners that are under-scaled | Optimization (weekly Explorer, daily Starter+) | Bids are increased to capture more profitable volume |
| Attack | Harvest | Converting search terms found in broader or discovery traffic | Split cadence: weekly strategic harvest, plus daily optimization harvest-from-auto on Starter+ | High-performing terms are promoted into tighter targeting and cleaned up at source |
| Attack | ASIN Harvest | Strong product-level opportunities against specific ASINs | Strategic (weekly paid tiers) | New product targets are created to capture those opportunities directly |
| Attack | Category Discovery | Early signs of conversion in untapped categories | Strategic (weekly paid tiers) | New category-level targeting is launched to test expansion areas |
| Attack | Category Scaling | Existing categories already showing good return | Strategic (weekly paid tiers) | Category targeting is expanded to scale proven pockets of demand |
| Attack | Scale Budgets | Profitable campaigns hitting budget ceilings | Mixed: monitoring can surface urgent budget exhaustion, optimization handles regular budget adjustments | Daily budgets are increased so winning campaigns do not cap early |
| Attack | Anchor Keywords | Keywords with outsized contribution to revenue efficiency | Monitoring (tier-based) | Priority anchor terms are identified for focused investment |
| Attack | Focus Campaigns | Anchor terms that need tighter control and isolation | Strategic (weekly paid tiers) | Focused campaign structures are created for better control of bids and placements |
| Attack | Auto Campaign Creation | Gaps in discovery coverage | Strategic (weekly paid tiers) | New discovery campaigns are launched to find additional winners |
| Optimize | Dayparting | Clear time-of-day or day-of-week performance differences | Strategic (weekly paid tiers) | Schedules are applied so spend shifts toward high-performing windows |
| Optimize | Placement Optimization | Imbalance across top-of-search, product page, or rest-of-search performance | Strategic (weekly paid tiers) | Placement multipliers are adjusted to improve return by placement |
| Optimize | Variation Optimization | Meaningful performance gaps between creative or ad variations | Strategic (weekly paid tiers) | Underperforming variations are reduced so delivery concentrates on stronger creatives |
| Optimize | Cut Budgets | Campaigns consistently underperforming versus target | Optimization (weekly Explorer, daily Starter+) | Budgets are reduced to limit waste and reallocate spend |
| Optimize | Budget Rules | Repeating budget patterns that can be automated | Strategic (weekly paid tiers) | Budget automation rules are created for hands-off control |
| Maintain | Naming | Campaign naming drift from your standards | Monitoring (tier-based) | Names are standardized to improve reporting and team clarity |
| Maintain | Ad Group Naming | Ad-group naming drift from your standards | Monitoring (tier-based) | Ad-group names are standardized for cleaner structure and analysis |
| Maintain | Allocation | Portfolio mix drifting from intended discovery or scale balance | Strategic (weekly paid tiers) | Clear allocation guidance is recorded so spend mix is corrected intentionally |
| Maintain | Structure | Structural issues that reduce control or quality | Strategic (weekly paid tiers) | Structural improvements are applied to keep the account clean and manageable |
| Maintain | Health Alerts | Non-urgent warnings or info signals, for example cannibalization or hygiene findings | Monitoring (tier-based) | Preventive fixes are queued before issues become critical |
Recommendation categories not exposed as standalone lanes
- Product Split recommendations run through guardrail and product-split flows, not as a dedicated lane.
- Campaign Classification recommendations update campaign role metadata, not as a dedicated lane.
FAQ
What should I approve first?
Approve the items that protect the account from waste or instability before you approve the items that try to scale it.
When should I leave Command Center and edit directly?
Leave Command Center when you already know the exact entity and exact change you need to make, and you do not need recommendation-level evidence to decide.
Next Steps
Use Activity Log to verify outcomes, or read Turn On Auto-Apply when you are ready to automate the decisions you repeatedly trust.
Lane Reference
| Phase | What it is for |
|---|---|
| Triage | Immediate risk reduction and account protection |
| Defend | Waste control and efficiency protection |
| Attack | Scaling proven winners |
| Optimize | Improving return and allocation |
| Maintain | Hygiene, structure, and recurring upkeep |
Read next
Related product and trust pages
Sources
Last reviewed by Prism team
