Recurring pulse series

A pulse series turns a single poll into a repeating one. You pick a cadence, and InviziPoll keeps track of when the next wave is due, carrying your questions and settings forward each time; recurring series are a paid feature; an active trial or a paid plan.

#Creating a series

Start from a poll you have already published. On its poll page choose Make this recurring, name the series, and pick a cadence. That poll becomes wave 1, and its questions, branching rules, duration, retention, recipient bounds, access settings, folder, and Slack announcement channel become the series blueprint, which every later wave inherits.

Choose a cadence:

Month-end is handled the way you would expect: a monthly series starting on 31 January comes due on 28 February (or the 29th in a leap year), not on 3 March, and it does not skip a month.

#When a wave comes due

On the due date, the workspace owner gets an email with a link straight into the wizard, pre-filled from the blueprint. The dashboard's Upcoming rail shows the same thing: due and upcoming waves, each one click from a pre-filled wizard. Review, adjust anything that needs adjusting, and send.

Wave numbers are assigned by the server when a wave is created, so two people opening the link at the same time produce wave 4 and wave 5, never two wave 4s and never a lost one.

If a series goes unattended, it does not fire a backlog. A weekly series ignored for two months sends one reminder for the next future date, not eight overdue ones.

You can pause a series at any time and resume it later; pausing stops the reminders without discarding the blueprint.

#Why you launch each wave

Each poll has its own encryption keypair, generated in a browser. Our servers don't generate poll keys, and we've designed them not to.

So a scheduler that silently created and sent waves on your behalf would require exactly the capability we have designed the system not to have. Instead, the server tracks the schedule and sends you a link; your browser mints the keys when you open it.

The practical effect is that a wave goes out when a human opens the email. If you want a pulse to land on Monday morning, expect to spend thirty seconds on it.

#Reading the trend

Every series has its own page, reached from any of its waves. It lists the waves and, once at least two waves have unlocked, draws each question's movement wave over wave. An NPS question, or a scale set to exactly 0 to 10, also gets an eNPS card: the latest wave's score and how far it moved since the previous readable wave.

A wave whose results haven't unlocked yet is drawn as a gap in the line, never as a zero. See when results unlock. From the same page you can pause and resume the series, delete it, and see the actions that were published for each wave.

Trends are computed in your browser from decrypted results, so they are visible only to someone who holds the poll keys.

#Retention and trend history

Waves use the retention period you chose, exactly like any other poll. A series doesn't quietly extend the life of anyone's response data to make a longer trend line; respondents are told when their responses are deleted, and a series does not change that promise.

Trend history across waves comes instead from a per-wave aggregate snapshot: counts, distributions, and scale statistics only, never a written answer. Your browser writes it the first time it decrypts a wave's unlocked results, encrypted to that wave's own poll key, so the server stores it without being able to read it. Purge never touches it, so your trend line survives after the underlying responses are deleted on schedule.

See also Duplicating polls and poll list management. Each page covers the adjacent settings and workflow steps.

#Related

• You said, we did: publishing actions after a poll
• Creating your first poll
• Viewing results
• Billing, trial, and tier limits