Email campaigns¶
Send a one-question NPS survey to your contacts by email. The score buttons live in the email — a recipient clicks a number from 0 to 10 and the answer is already recorded before the page they land on finishes loading.
A project → Campaigns → New campaign.
A campaign is a batch. It mails your chosen audience, tracks each address on its own, and its answers flow into the survey's results like any other response.
Building one¶
| Field | What it does |
|---|---|
| Name | Internal only — how you find this campaign later |
| Subject | The email subject line |
| Intro | Optional text above the score buttons |
| Survey | The NPS survey to ask. Only live NPS surveys are offered |
| Page | The hosted survey page the buttons link to |
| Send to | Which contacts (see below) |
The page matters more than it looks. A scored link opens a real hosted survey page, so the click records the score and gives the person somewhere to add a comment. A survey can have several pages; the campaign pins the exact one.
Who gets it¶
| Send to | Audience |
|---|---|
| All contacts with an email address | Everyone in the project you can reach |
| Everyone who has submitted feedback | Only people who came to you first |
| By previous NPS score range | e.g. re-ask only last quarter's detractors |
Contacts come from feedback people have already left you and from CSV imports.
Imported contacts need a consent attestation
People who submitted feedback themselves gave you their address for exactly this. Imported contacts did not — so when the audience includes any imported contact, you must tick "I confirm these recipients agreed to receive email from me." It is a timestamped, attributed record, not a re-opt-in email. If you later widen the audience to add imported contacts, the old tick no longer covers the new list and you attest again.
Send now, or schedule¶
From the campaign, Send now shows a confirmation with the real count before anything leaves:
412 people will be emailed. 480 matched · 41 no email · 19 suppressed · 8 unsubscribed
Or Schedule for a date and time — entered in your team's time zone (set on the team settings page), not UTC, so "Monday 9am" means your Monday 9am.
What is frozen when you send¶
At the moment a campaign starts, two things are pinned and cannot change under it:
- the survey version every recipient answers, and
- the page the links point at.
Publish an edit to the survey mid-campaign and the people already mailed still answer the questionnaire they were sent — so one campaign is always one aggregate, never two questionnaires averaged together. This is the same versioning rule the surveys follow, applied to the whole batch.
Deliverability, handled¶
Campaign mail is built to keep your sending reputation intact without you managing any of it.
- Separate sending identity. Campaigns go out from a dedicated
mail.withfeedback.comaddress, apart from transactional mail, so a bulk complaint spike can never throttle your password resets. - Suppression is re-checked at the last moment. A hard bounce or a spam complaint that arrives after you press send still stops that address — the check runs immediately before each individual email, not once up front.
- One-click unsubscribe. Every email carries the RFC 8058 header that lets Gmail and Apple Mail show a native unsubscribe button, plus a link in the footer. An unsubscribe is scoped to your team and never blocks transactional mail.
- Legal footer. Your project's legal entity name and postal address are included automatically — set them in the project's settings.
- The link carries a token, never an email address. A scored link cannot be edited to answer as someone else, and the address never appears in a URL or a server log. Links expire (90 days by default).
Pacing and pausing¶
Big sends are paced for you against three separate ceilings: your plan's daily email cap, a per-second send rate, and the mail provider's own account-wide 24-hour quota. When a campaign meets one of these, it does not fail — it pauses and resumes on its own once the window reopens (the daily cap, for instance, resets at your team-local midnight). A paused campaign stays "sending"; you do not need to touch it.
See Limits and quotas for the daily cap behaviour.
Cancelling¶
Cancel a sending campaign and it stops at the next email — anything already sent stays sent, nothing further goes out. There is no way to un-send what has left, which is the honest state of email everywhere.
Privacy¶
Erasing a contact clears their address and name from the campaign's records but keeps the counts, so a person's right to be forgotten never silently rewrites your history. Bounce and complaint handling is tied to the exact message sent, so an event is attributed to the right recipient even when two teams happen to email the same person. See Privacy.