Invite named people to a survey and track who answered. Open Surveys, your survey, Distribution. The survey must be published.
Waves
A wave is one round of invitations with its own recipients, reminders and results. Run the same survey again next quarter as a new wave: it is stored separately from the first, even for the same person, and you can analyse one wave on its own with the wave filter in Analysis.
- Create wave. Choose a name, an optional subject and message, and the reminder rules.
- Add recipients. Paste addresses, one per line with an optional name after a comma (and, for a survey with several languages, a language code after a second comma), or upload a CSV file (up to 5,000 rows). Duplicates and invalid lines are counted and skipped.
- Start wave. The first invitations are queued. Large lists go out in batches under the "emails per run" cap.
- Close wave when the round is over. Nothing more is sent and the personal links stop counting.
Each recipient gets a personal link. One answer completes that invitation for good; the link cannot be used to answer twice, and it should not be forwarded.
Repeat automatically
A recurrence starts a new wave for you on a schedule, so a quarterly check-in does not need to be set up by hand every time. Open Distribution, Repeat automatically, Add a recurrence.
- Repeat weekly, monthly, quarterly, or every N days (7 or more), "every N" weeks, months or quarters. Pick a timezone: the first send is read in that timezone and every later round keeps the same local time of day, also across daylight saving changes. A monthly rule that starts on the 31st sends on the last day of shorter months.
- Stop after an end date, after a number of waves, or never. You can pause, resume, edit or delete a recurrence at any time. Resuming does not send rounds that passed while it was paused. Deleting runs in the background and keeps the waves it already created.
- Skip while an earlier wave is open (on by default) skips a round when the previous wave has not closed yet, so people are not asked twice at once. Each wave closes after the number of days you set (14 by default).
- Who is invited. Recipients are taken from the previous wave (or the wave number you choose). You can invite everyone, only people who answered, or only people who did not. People who opted out or whose address bounced are never emailed, and you can leave out anyone who answered in the last N days.
- Reminders follow the same rules as any wave: a first reminder, a gap, a maximum, and only to people who have not answered.
- A round that cannot go out is skipped and the reason is shown on the recurrence: the survey was not running, nobody was left to invite, there was no earlier wave to take recipients from, or the round was more than a day late (for example after an outage). Late rounds are never sent out of schedule.
Saving a recurrence sends nothing by itself. Rounds are created automatically only once automatic waves are switched on for your workspace; until then the page says so.
Reminders
Turn on Remind people who have not answered and set when the first reminder goes out, the gap between reminders and the maximum number of reminders. Reminders go only to recipients who have not completed their invitation. Someone who answers, opts out or bounces gets no more. A closed wave sends nothing.
Opt-out
Every invitation and reminder has a one-click unsubscribe from survey invitations, in the email footer and in the mail program's own unsubscribe button. The page opens in the language of the invitation. Opting out applies to every wave of every survey for that address and to nothing else: security and billing mail is not affected.
An opted-out or undeliverable address is checked before the first send and again on every retry. If you import one, it is recorded with that status and never emailed. The recipient list shows each status: invited, reminded, completed, opted out or bounced. Addresses are shown in full only to members who may edit the survey.
Language
The email is written in English. Your own subject and message are sent exactly as you wrote them.
The survey itself can open in another language. If your survey has several languages, choose one for a whole wave or recurrence (Survey opens in), or give individual recipients their own language code in the import (email,name,fr). The personal link then opens the survey in that language; people can still switch language on the page. A code the survey does not offer is ignored and the survey opens in its default language.
Invite on an event
For in-app surveys, create an event wave and start it. When the event fires for a person, they are invited to the open event wave, unless the same person was already invited within the "do not re-invite within" window, the workspace limit for survey emails is reached, or they opted out. The result says which of these applied.
API and agents
With surveys:read and surveys:write. Sending is always queued.
GET/POST /surveys/{survey}/distribution/waves,GET/PATCH .../waves/{number},POST .../launch,.../closeand.../send(queue the invitations and due reminders now).GET/POST .../waves/{number}/invitationslists recipients and imports addresses (emailstext, orrecipientswithemailandname).POST .../distribution/eventinvites one person for an event.GET/POST .../distribution/schedules,GET/PATCH/DELETE .../schedules/{id}manage recurrences (PATCHwithstatuspauses or resumes; delete is queued). Waves and recipients accept an optionallang.- Agent tools:
list_survey_waves,create_survey_wave,update_survey_wave,launch_survey_wave,close_survey_wave,send_survey_wave,import_survey_invitations,list_survey_invitations,trigger_survey_event_invitation,list_survey_wave_schedules,create_survey_wave_schedule,update_survey_wave_schedule,delete_survey_wave_schedule.
