Project status

Your project's home answers two questions that look similar and are not: what is still left to set up, and what has broken. Each has its own surface, and knowing which one is talking to you saves a lot of guessing.

The two surfaces

Get your project ready is the setup checklist. It lists the things you haven't done yet — import your audience, set up a channel, verify your business, add funds, send your first campaign — and it steps aside when nothing is pending.

Needs attention is the alerts panel. It lists what has broken, or is about to: a card that expired, a connector that stopped bringing contacts in, a campaign scheduled for tomorrow that your balance won't cover. Each one comes with a date when there is a deadline.

Why a brand-new project has no alerts

The rule that decides which surface a thing belongs to is worth knowing, because it explains most of what you'll see: not having something is always the checklist.

For an alert to appear, the thing has to exist and be broken. There is no expired card without a card, no disconnected connector without a connector, no underfunded campaign without a campaign. So a project that has just finished signing up sees a full checklist and no red at all — we won't tell you your balance is low right next to the step asking you to add funds.

What you may see on day one is something informative, such as a sender registration waiting on an operator. That's work in progress, not a problem.

Nothing is saved — everything is recalculated

There is no inbox of notifications here, and nothing to mark as read. Every time you open your project, both surfaces are recalculated from your data at that moment.

Two consequences, and they're the ones that generate most of the questions:

• An alert disappears only when the problem is genuinely fixed. The expired card goes when you add another one; the half-finished connection goes when the data source is created. Nobody has to remember to clear anything, and nothing lingers pointing at a problem you already solved.
• No step is ever done forever. There is no "setup complete" flag, so a step you had completed comes back if its condition stops holding — you spend your balance, the only sender you had gets rejected, a new regulator appears. That's the point, not a glitch: what you see is true now.

Hiding things: what's yours and what's your team's

You can get some of these out of your way, and it's worth knowing what that actually does — because skipping a step and hiding an alert behave differently on purpose.

	Where it's saved	Who else is affected
Skip a checklist step	On the project	Your whole team stops seeing it
Hide an alert	In your browser	Nobody — not your teammates, not your other computer

An alert you hide is hidden from you, on that browser. Your colleagues still see it, it comes back if you switch machines, and — this is the part that matters — your assistant still sees it. Ask it whether everything is fine and it will tell you about the very thing you hid.

That difference is deliberate. A shared dismissal would hide a live failure from everyone in your organization, which is exactly what an alert must never do. A skipped step is the opposite: it's a decision about how your team wants to set the project up, so it belongs to the project.

Not every alert can be hidden, and the ones that can behave in one of two ways:

• Some can't be hidden at all — an overdue invoice, an account whose API is blocked. Hiding those would only delay the surprise.
• Some hide until something changes. Hide a half-finished Shopify connection and it stays hidden; leave a different one half-finished tomorrow and that one appears, because it's a different fact.
• Some come back after a few days, even if nothing has changed. That's what we do with an expired card: it's a problem that quietly gets worse while looking exactly the same, and hiding it forever would be hiding a breakdown in progress.

What Needs attention watches

Four families. What matters isn't the list itself but knowing that each entry has a precise condition behind it — so if something didn't warn you, there's a reason.

Money. An expired card, or one about to expire. A low balance — measured against your organization's threshold, and only once money has actually gone into the account. A failed subscription charge, an invoice due or overdue, and auto-recharge switched off on a project that has automations running. See Balance.

Data. An integration you authorized and never finished connecting, a connector whose access has dropped, and one that hasn't brought anything in for seven days — only if it ever synced, because one that never did is unfinished setup, not a fault. See Managing data sources.

Sending. A scheduled campaign your available balance won't cover, with its send time as the deadline; a campaign that went unpaid during its send; and an account whose API calls are being rejected.

Compliance. A sender registration a carrier or regulator turned down, one that's still under review, and a regulator's deadline — "on the 15th you stop being able to send to Spain", which is not the same as "you haven't registered Spain yet". See Spain.

Two things that appear in both places

There are exactly two situations where the checklist and the alerts talk about the same country at the same time. Both are deliberate, and in both cases the two sentences say genuinely different things.

A regulator's deadline. The checklist recommends registering a country from the moment the regulation exists. The alert only appears in the 30 days before the date, and only for countries you can send to today. During those four weeks the checklist is telling you there's a gap to close, and the alert is telling you what happens on a specific date to something you can still do right now.

A rejected registration. A country whose registration was turned down shows up as an alert and as a country still to register, because a rejected registration isn't coverage. After thirty days it stops being news and stays only on the checklist. It doesn't vanish — it moves.

Where each thing is actually fixed

This page explains the two surfaces. The fixing lives with the topic: