Reach candidates and contacts without leaving the pipeline
Build a recipient list, send a campaign, and watch it move from queued to delivered to opened — attributed to the job, candidate pool, or module it was sent for, right alongside the pipeline it feeds.
Three pieces, one workspace
A campaign is a recipient list plus a message, tracked all the way to delivery — sitting next to the pipeline it was sent for, not in a separate tool.
Recipient lists
Import addresses from a spreadsheet or add them one at a time. Every list is validated automatically before it's ready to send to.
Delivery tracking
Each recipient moves through a funnel — queued, sending, sent, delivered, opened, clicked — so you see what actually happened, not just what was scheduled.
Tied to your pipeline
Filter campaigns by the module they belong to — a job, a candidate pool, a hot list — so outreach stays attributed to what it was actually for.
Lists that clean themselves up
An uploaded list doesn't go straight to your send queue as-is — it's checked first, so a campaign isn't spent on addresses that were never going to deliver.
Import from Excel or CSV
Upload a spreadsheet to create a new list, or add rows to an existing one. A single contact can also be added by hand and is validated immediately.
Background address cleanup
Imported rows start out pending and are cleaned up in the background, ending as valid, risky, or invalid — with a progress bar while it runs.
Re-queue anytime
Send a list back through cleanup on demand, or remove a single recipient without touching the rest of the list.
Send through the provider you already trust
Campaigns go out through AWS SES, Mailgun, or a connected personal mailbox — whichever your tenant is configured to use.
Company-wide credit pool
Mass email and address cleanup are metered against a shared communications credit pool, with a configurable cost per unit.
Per-user allocation
Admins can allocate credits to individual users out of the company pool, and see who has spent what.
Send to a selection
Select recipients from a list — or from a campaign's own recipient table — and send a one-off promotional email to exactly that selection.
To be precise about it
Whether credits are required at all, and their cost per send or cleanup, is a tenant-level setting — ask your Jwalix admin, or us, for your workspace's configuration.
From queued to clicked, in one view
Campaign detail
Open a campaign to see delivery, open, and click rates, with a status funnel you can click through to filter its recipients directly.
Deep-linked from a module
Launch a campaign from a jobs list (or another module list) and it arrives pre-filtered to that module — no manual re-filtering after the fact.
Distributing a job posting to external job boards is a related but separate feature — see Ad Campaigns under → /product/recruitment-automation/.
Questions about Campaigns
Campaigns are outbound recruiting or outreach efforts, typically aimed at candidates or client contacts. Ad Campaigns specifically manage distributing a job posting to external job boards.
An imported address starts out pending and is checked in the background, ending as valid, risky, or invalid. You can re-queue a list for another pass at any time.
AWS SES, Mailgun, or a connected personal mailbox — set per tenant.
Mass email and address cleanup are metered against a shared communications credit pool with a configurable cost per unit — whether that's enabled, and at what cost, is a tenant-level setting.
Yes. Campaigns can be filtered by the module they belong to, and can be launched directly from a module's list view already scoped to it.
See a campaign go from queued to delivered
We'll import a sample list, send a campaign, and walk through the delivery funnel live on the call.