Every day, Qwairy analyzes your monitoring data (prompts, answers, sources, competitors, site diagnostics, search demand) and turns it into concrete, prioritized actions. Each action carries a quantified justification, the signals behind it, a step-by-step execution guide, and a measured outcome once you complete it. The recommendations are generated deterministically from your data. The same data always produces the same actions, with a traceable explanation for every priority. You’ll find the Action Center in the Cockpit section, alongside your overview and alerts.

​

How it works

The Action Center has three surfaces, as tabs:

​

1. Suggestions

Fresh engine output lands in a triage inbox. For each suggestion you decide: Accept moves it into your action plan, Decline removes it (it will not be suggested again). Nothing enters your plan without your decision.

​

2. Action plan

Your accepted queue, available as a focus list (the top 25 by priority, with a collapsible backlog) or as a kanban board (To Do, In Progress, Done, Declined). Only actions you have accepted appear here; fresh suggestions stay in the Suggestions tab until you accept them. Each action moves through a simple lifecycle: Start working, Mark done, Decline, Reopen. When you open the Action Center, it lands on the Action plan if you already have accepted work, or on Suggestions if your plan is still empty.

​

3. Strategy

Three levers that tune how your queue is ordered:

• Time horizon: quick wins first, balanced, or long term
• Engine focus: actions targeting a focused AI engine get a priority boost
• Capacity and budget: monthly content capacity and backlink budget used to size outreach recommendations

Strategy settings re-order your queue. They never create or delete actions.

​

How actions are prioritized

Every action is scored from the raw signals the detectors extract, then surfaced as a force tier plus a single legible priority score: Connecting Google Search Console enriches the demand scoring with real impressions and positions for your pages and queries.

​

Action families

Actions come from detector families, each watching a different part of your monitoring data: Each action is also classified by scope: on-site (work your team ships on your own site), off-site (outreach, PR, external platforms) or setup. Filters let you slice the queue by family, tier and scope.

​

Inside an action

Opening an action shows everything behind the recommendation:

• Why it matters: the quantified justification (citations, competitive pressure, demand, severity)
• Signals: the raw numbers behind the priority (citations, fan-out occurrences, impressions, affected pages, domain rating)
• Context: live evidence such as per-engine presence on the linked prompt, competitors cited on it, brand presence on the cited source, and competitors present in answers citing that source
• How to execute: a step-by-step guide, tailored to your brand context when available, plus a ready-to-use artifact for some actions (a FAQ schema stub, an outreach email draft or a community engagement plan)
• History: the full lifecycle timeline (detected, rescored, accepted, started, completed, reactivated). A rescore names the dominant signal that moved the priority, for example “2 → 4 competitors now cited here”
• Ask AI: hands the action to the Qwairy assistant, which loads its full context and helps you build a concrete execution plan from your brand data

​

Measured outcomes

Completing an action is not the end of the story. For action families with dense, automatically refreshed data, the engine freezes a baseline metric when the action is created and re-measures it after you complete the action, for 90 days: Outcomes are displayed honestly: a first read appears 7 days after completion, deltas are only shown above a minimum sample size and a minimum movement, and the wording is always “observed since completion” rather than attribution. AI answers typically reflect changes after 4 to 12 weeks.

​

Staying current

The engine re-syncs daily. Existing actions are re-scored as new data arrives (a priority change appears in the action’s History), actions whose underlying signal disappears are auto-resolved, and they reactivate with their previous status if the signal comes back. Your triage decisions always survive: declined actions never come back, and completed work is never deleted.

​

Access from the API and MCP

The Action Center is also available programmatically:

• API: List Actions returns the prioritized queue with filters and pagination
• The get_actions MCP tool exposes the queue to AI assistants connected to Qwairy

Both surfaces are available on paid plans. The REST API and MCP server require Growth or above.