Campaign builder stays in the workspace you picked

Picking a workspace should mean you stay in it, all the way through building a campaign.

What changed

In some flows, building a campaign could redirect you out of the workspace you had selected and into a different one partway through the process. This was disorienting: you would start building a campaign in one workspace and, without changing anything yourself, find yourself working in another. If you manage more than one workspace, whether for different clients, different brands, or different teams, this kind of unexpected switch is more than a minor annoyance, since it puts you at risk of configuring a campaign against the wrong workspace entirely without noticing right away.

This is now fixed. The campaign builder keeps you in the workspace you selected from start to finish, with no unexpected redirects. Whichever workspace you were in when you started building a campaign is the workspace you remain in through every step, from initial setup through final launch.

Workspaces in FirstSales exist to keep separate operations cleanly separated: separate senders, separate contact lists, separate billing in many setups, and separate reporting. That separation only works if the tools you use inside a workspace actually respect its boundary the whole way through. A builder that could silently hop to a different workspace partway through a build was quietly breaking that boundary, even if it did not happen on every single build.

The underlying cause was in how the builder tracked which workspace context should apply at each step of setup. In some sequences of actions, that tracked context could shift to a different workspace without any deliberate action from you to cause the switch. The fix makes the workspace context something that is fixed once you begin building a campaign, rather than something that could be recalculated and changed midway through.

How to use it

Nothing changes in how you use the campaign builder. Select your workspace, start building your campaign, and it will stay scoped to that workspace throughout setup, from audience selection through sequence design and launch. You do not need to double-check your workspace selection at each step anymore; it stays fixed once you begin.

If you regularly switch between workspaces, this makes it safer to jump straight into building a campaign right after switching, since the workspace context you land in is the one that will stick for the entire build process. There is no longer a need to build a habit of re-verifying which workspace you are in partway through setup as a precaution against an unexpected switch.

If you manage FirstSales on behalf of multiple clients or brands, each typically set up as its own workspace, this fix is particularly relevant to your day-to-day workflow. Switching into a client's workspace, building a campaign for them, switching to a different client's workspace, and building another campaign is a common pattern, and it depends entirely on each build staying scoped to the workspace you were in when you started it. If you had previously built a habit of double-checking your workspace indicator at every step of the builder as a safeguard, you should be able to drop that extra check now, since the underlying redirect issue is resolved.

If you have an existing campaign that you suspect might have been built partly against the wrong workspace before this fix, it is worth reviewing that campaign's sender list, contact sources, and settings to confirm everything lines up with the workspace it currently lives in. If anything looks inconsistent, support can help you sort out where a specific setting or contact list actually belongs.

Why it matters

An unexpected workspace switch mid-build risks you configuring a campaign in the wrong place, whether that means the wrong sender identities, the wrong contact lists, or the wrong billing context. For anyone managing multiple workspaces, that is a real risk, not just a cosmetic inconvenience: a campaign built partly against the wrong workspace could end up drawing from the wrong sender pool or attaching to the wrong billing account, and untangling that after the fact is far more work than avoiding it in the first place.

Keeping the builder anchored to your chosen workspace removes that risk and keeps campaign setup predictable. You can trust that the workspace you started in is the workspace your finished campaign actually belongs to, without needing to verify that assumption at every step along the way.

This matters most in the moments when you are moving quickly, building several campaigns back to back across different workspaces in a single session. That is exactly the situation where an unnoticed redirect would have been easiest to miss, since you are already switching context often and a workspace change partway through one build could blend in with the switches you were making intentionally. Removing that failure mode means the speed of working across multiple workspaces no longer comes with a hidden accuracy cost.

Workspace boundaries exist for a reason: they keep separate operations, separate clients, and separate teams from bleeding into each other. A tool that respects that boundary consistently, without exception, however small the exception seemed, is what lets you actually rely on workspaces as a real organizational structure instead of a label that mostly holds up but occasionally slips.

This is one of those fixes where the correct behavior is unremarkable by design. You should not have to think about whether the campaign builder is staying in the right place; it simply should, every time, for every build. Getting that unremarkable behavior right is what lets the more visible parts of building a campaign, choosing your audience, writing your sequence, setting your goal, get your full attention instead of being shared with a quiet worry about whether the workspace underneath you might have shifted.

If you build campaigns across several workspaces regularly, it is worth treating this as one less thing to check off your mental list before hitting launch. The workspace context is settled the moment you start the build, and it stays settled through every screen after that, freeing up attention for the parts of setup that actually need your judgment.

Availability

This fix applies to campaign building across all workspaces.