Campaigns: group outreach by initiative, and see what’s working
Every sequence now belongs to a Campaign, the business initiative it serves: “Q4 fintech outbound”, “Invites for our October event”, “Churned customers win-back”. Campaigns live at Outreach → Campaigns.
Why this matters — Sequences used to be grouped only by the automation that created them, and everything built in chat went into one shared conversation bucket, including follow-up work on an automation’s results. There was no way to pull the sequences for one initiative together, so a specific push (inviting 100 people to your event, a small campaign to one group of accounts) got mixed in with everything else and its performance was invisible.
Swan understands Campaigns — Sequences from any automation and from chat can go into the same Campaign, and one automation can feed several. Swan knows which initiative every sequence belongs to, so you can ask “How is the October event campaign doing?”, “Which campaign gets the best reply rate?”, or “Look at what got replies in the win-back campaign and use it in the next one”, and it answers from that Campaign’s sequences. It also files new outreach under the right Campaign as it builds it.
In the app — The Campaigns list shows each Campaign’s owner, sequences awaiting approval, reply rate, and last activity, with All campaigns / Mine only and a search across campaigns and contacts. Each Campaign has an Enrolled tab (its numbers and sequences) and an Awaiting approval tab (review drafts one by one, with J/K or the arrow keys). Outreach Analytics filters by Campaign and switches its performance table between By Campaign and By Sender.
Where sequences go — Swan picks the Campaign when it builds a sequence: the Campaign you name, then the automation’s Default campaign (set on its tools card; unset reads “Swan decides”), then your personal default Campaign (for example “Dana’s sequences”). Ask Swan to create, rename, or delete Campaigns, change your default, or move sequences between Campaigns. Existing sequences were filed automatically on September 24, 2026. The org-wide Sequences list now redirects to Campaigns, and old sequence links still open the sequence inside its Campaign. A view of all your sequences in one place is coming back shortly.
Inboxes: pick any email and any LinkedIn account for a sequence
Each connected account is now its own inbox, one email account or one LinkedIn account. A sequence picks one email inbox and one LinkedIn inbox, from anyone on the team.
Why this matters — Swan used to pair each LinkedIn account with one of your email accounts into a single sender, and a sequence could only use that fixed pair. With two email addresses, only one of them could send alongside your LinkedIn, and you couldn’t combine your email with a teammate’s LinkedIn. Now you mix and match: email from your second inbox, connection request and message from your CEO’s LinkedIn, in the same sequence. Swan writes each channel in its owner’s voice.
Per-inbox settings — Every inbox has its own daily sending limit (up to 150 emails, 40 LinkedIn messages, or 80 with Sales Navigator), writing instructions, default CC/BCC, and a switch for whether sequences can use it. Change them by asking Swan in chat; it asks for your approval before changing anything. Connection-request limits stay fixed.
Team inbox list — The Inboxes page lists every connected inbox on the team. Owners can disconnect their own inboxes and admins can disconnect anyone’s, including inboxes that are already disconnected, so dead accounts can finally be removed.
See who approved what
Every sequence now records its review decision: “Approved by Dana · 2h ago”, “Rejected by you”, or “Automatically sent”. It shows in the sequence drawer, on the sequence card in chat, and on Desk chips.
Reject instead of Archive — Reject replaces Archive in the review form, the chat approval bar, and the bulk toolbar. Rejected sequences stay in a read-only history under the Rejected filter instead of disappearing.
Automations can approve by rule — Scheduled and triggered automations can approve or reject drafts waiting for review when their instructions say so, for example “approve drafts for accounts already in an open deal”. These decisions show as automatic, with no reviewer named.
Big runs on the Desk — Desk cards and task details load a run’s sequences 20 at a time, with load-more, so large batches stay quick to review.
Improvements
LinkedIn messages don’t hold up sending while they wait — A LinkedIn message waiting for a connection to be accepted no longer takes one of the day’s sending slots. Rejected, expired, or withdrawn invitations close the LinkedIn steps, and email steps continue.
Longer connection notes — Connection request notes can be up to 300 characters, up from 200. Notes send only from inboxes with Sales Navigator.
Know when the first message goes out — After building a sequence, Swan now has the org’s sending window and tells you when the first message can go out.
Fixes
LinkedIn messages outside sending hours — A LinkedIn message sent right after a connection was accepted could go out outside your sending hours. It now waits for the sending window.
LinkedIn replies not stopping a sequence — A LinkedIn reply from a prospect with duplicate contact records sometimes didn’t stop their sequence. Replies now find the right sequence.