Campaigns refuse to launch in an unsafe state

Campaigns now check themselves before they launch. If a meeting campaign is pointed at a calendar you do not actually own and have verified, or a link goal is missing a valid URL, the campaign will not go live in that state. Simultaneous edits from two tabs can no longer silently corrupt a campaign either; you get a clear conflict message instead.

What changed

A meeting campaign only makes sense if it can actually book meetings, which means it needs a calendar connection that is both yours and verified. Previously, a campaign could be set up and launched even when that connection was missing or incomplete, which meant it could run and try to schedule meetings against a calendar that was not actually ready to accept them. Now, the system requires a verified calendar you own before a meeting campaign is allowed to launch, catching the gap at setup instead of leaving it to surface later as a broken scheduling experience for a prospect.

The same kind of check now applies to link goals. If a campaign's goal depends on a link, that link needs to be a valid URL. A campaign with a broken or missing link goal will not launch, instead of going live and sending prospects toward a destination that does not work, which would waste every reply the campaign generates until someone noticed the link was bad.

The other change here addresses a quieter but riskier problem: what happens when two people, or two open tabs, edit the same campaign at the same time. Before, simultaneous edits could overwrite each other in ways that were not obvious, potentially corrupting the campaign's configuration without anyone noticing until something went wrong downstream, sometimes days later when a draft or a send behaved unexpectedly. Now, if two edits collide, you get a clear conflict message instead of a silent overwrite, so you know immediately that a collision happened and can decide how to reconcile it.

All three checks share the same underlying idea: a campaign should never be able to reach a state where it looks launched but cannot actually do what it claims to do, and it should never lose changes silently. Each of these gaps, a calendar that is not really connected, a link that does not really work, or an edit that quietly vanished, previously left a campaign looking fine on the surface while something underneath it was broken.

How to use it

When you set up a meeting campaign, connect and verify your calendar as part of that setup. If you try to launch before that connection is confirmed, the campaign will tell you what is missing rather than letting you launch into a broken state that only becomes obvious once a prospect tries to book time and cannot.

If your campaign's goal involves a link, such as a booking page or a landing page, make sure that URL is filled in and valid before you launch. The system will flag it if it is not, giving you a chance to fix it before any outreach goes out pointing prospects nowhere.

If you are working on a campaign with a teammate, or you have it open in two browser tabs yourself, and you both make changes around the same time, watch for the conflict message. It tells you that a collision happened, so you can reconcile the changes deliberately instead of one edit quietly disappearing without either of you knowing which version actually survived.

If you regularly manage campaigns alongside a teammate, it is worth agreeing on a simple habit: check with each other before making a significant change to a shared campaign, or at least glance at it right before you launch to confirm the state matches what you expect. The conflict message will catch a genuine collision, but a quick check before launch is still the fastest way to avoid one happening in the first place.

Why it matters

A meeting campaign that cannot actually book a meeting, or a link goal that points nowhere, is worse than no campaign at all: it spends your outreach and your prospects' attention on something that cannot deliver, and you may not find out until a prospect complains or simply goes quiet. Catching these problems before launch, rather than after prospects start replying, saves you from a bad first impression you cannot take back.

The conflict handling matters for a similar reason. A campaign quietly corrupted by an overwritten edit can behave unpredictably in ways that are hard to trace back to their cause, costing you time debugging a problem you did not know existed. Surfacing the conflict directly, instead of letting one edit silently win, keeps your campaign configuration something you can trust, and something you and a teammate can work on together without stepping on each other.

Together, these checks shift the cost of a mistake from after launch, where it is expensive and visible to prospects, to before launch, where it is cheap and only visible to you. That is a trade worth making every time, especially for a channel like cold email where a broken first touch rarely gets a second chance with the same prospect.

None of these checks require extra effort from you beyond the setup you were already doing: connecting a real calendar, filling in a real link, and being aware that a collision message means exactly what it says. The system does the rest, catching the specific failure modes that used to slip through unnoticed until a prospect ran into them directly.

Availability

These checks apply to meeting campaigns and link goal campaigns now, and the conflict message applies to concurrent campaign edits across your workspace, whether the collision comes from two teammates or two tabs of your own. They apply automatically to every campaign you launch from here forward, with nothing to opt into, and to existing campaigns the next time you make a change to their setup, so you do not need to manually re-check anything that is already running correctly today.