trial_ended last month and nothing emails them”, not just “send more email”.
Checks run for workspaces with more than 1,000 active subscribers that sent at
least one email (campaign, sequence or transactional) in the last 14 days. A
workspace that stops sending is skipped until it sends again.
What it checks
The rules decide what is a problem. The AI step ranks findings, writes a
short summary for your business and sharpens each recommendation. It can leave
a finding out (an event it traces to an active sequence, a draft not worth
sending) but never adds one, so it never reports something the data does not
show. Campaign drafts need its judgment, so they only appear in checks where
the AI step ran.
How “nothing reacts to it” is decided
An event counts as handled when something ends up contacting the person, directly or down a chain. The check follows each event through:- sync rules that tag the contact (
saas.payment_failedaddspast-due); - sequences that start on that tag, or on a segment the tag or the event puts the contact in (a segment counts when that tag or event alone is enough to enter it);
- the tags and lists those sequences add, and the sequences that start on them, up to three sequences deep.
Revenue behind a finding
When a payment integration syncs revenue to your contacts (theirmrr
attribute), an event finding also says how much the people behind it pay you
each month, for example “1,000 a month or more makes a finding high priority, and among
findings of the same priority the one with more revenue behind it comes first.
The amount is in evidence.monthlyRevenue (USD) in the API.
If the sequence that would catch the event is paused or a draft, the finding
offers Turn it on and says how the event reaches it, for example “It
starts when this event adds the past-due tag.” The AI step then
double-checks the rest against your sequences, their triggers and what they
do, and leaves out an event it can trace to a specific active sequence. That
verdict is kept while the sequence stays active, so a check without the AI
step does not bring the finding back.
Where you see it
- Dashboard. The Account Health card sits at the top of your dashboard: Swirl’s summary, the most important finding and its fix button. See all opens every open finding, most severe first. Findings about a sequence, campaign or domain link to the screen where you fix them. Run now checks immediately; progress shows on the card and the list updates when it finishes.
- Email. After each scheduled check that finds something, the findings reach everyone who has the check on (see In your weekly report). The standalone email starts with your sending stats for the period against the one before: emails sent, open, click and bounce rates. Every link opens the full list on your dashboard, scrolled to the finding it is about.
- API, CLI and MCP. See Get Account Health,
sequenzy account-health, and theget_account_healthMCP tool.
Drafted fixes
With Draft fixes on (the default), Swirl may lay out up to two draft sequences per check, for example a sequence triggered by an event nothing reacts to. A draft has the trigger, the timing and one titled email step per message, with a short brief for each. A check on its own never writes the emails: write or attach each one, then turn the sequence on yourself. A sequence with an empty email step cannot be turned on. The agent never drafts the same fix twice, even if you delete the draft. When you click Build this sequence yourself, the emails are written too, the same as a sequence from a template. Review them, then turn it on.Fixing findings in one click
Every finding comes with buttons that do the fix, not just describe it:
Anything that changes live sending asks you to confirm first. When a button
fixes the finding, it is marked fixed and Swirl, the account health snail,
celebrates. The same actions are listed in the API response, so agents can
run them too.
You can also triage from the menu on each finding:
- Mark as fixed clears a finding. If the next check still finds it, it comes back.
- Snooze hides it for a week or a month.
- Dismiss hides it for good.
In your weekly report
Checks run early Monday (05:00 UTC), a few hours before the Monday weekly report. Swirl’s summary and the most important fixes, each with its button, then appear as an Account health section inside that report, so you get one email instead of two. If you do not get the weekly report (it is off for you, the workspace was not in it, or the week was too quiet), the findings arrive as their own email a few hours later. Either way you get each check once, and only when something needs fixing. Who gets it is each person’s own choice, in Settings → Notifications under Account health check: on by default for the workspace owner, opt-in for everyone else. Turning it off stops both the report section and the separate email. With the CLI:sequenzy notifications set --account-health off.
Settings
Checks run every Monday at 05:00 UTC, a few hours before the weekly report. The AI cost is on us, so there is no budget to manage. Owners and admins open Settings from the … menu on the card:- Weekly check: turn scheduled checks on or off. Run now works either way, at most once every 10 minutes. After a check that found something to fix, it waits a day: work through the findings first.
- Draft fixes: let Swirl lay out inactive sequences for the gaps it finds. You write the emails and turn them on.