The same short conversation, on a schedule.
Follow-up runs the study you already trust again — on a schedule you set, or after every delivery. Nothing changes about the conversation itself: the same questions, the same voice agent, and the same quality gate deciding what counts — only the schedule is new, and a trend line where there used to be one snapshot.
What a wave is
One instrument, fired again on a fixed cadence
A Follow-up wave is not a new survey — it is the same pulse survey, pinned to the same version, sent out again on a schedule you set instead of once. Follow-up is the short and frequent end of that: every day, several times a day, or fired after every delivery. Repeat a full study monthly and what you are running is waves of Survey & Feedback — the same dashboard, a slower rhythm. Monthly is as slow as a schedule goes; for anything slower you start the next wave yourself, one click, whenever it is due.
Every day
A steady read on a workforce, a ward or a route — close enough that a bad week shows up while you can still do something about it.
Several times a day
As close to real time as this gets, for a shift, a queue or a process you are actively trying to move.
After every delivery
Fired once a job, a stay or an order closes, so the question always lands right after the moment it is about.
Why it beats a one-off
A trend line, not a snapshot
A single study tells you where things stand today and nothing about which way they are moving. Because Follow-up pins every wave to the same survey version, the same questions are asked the same way each time — so a rise or a fall in the numbers is a real change in the answer, not a change in the instrument.
Every wave is comparable, by construction
The version is frozen the moment the first wave goes out. A later wave cannot quietly ask a slightly different question and still call itself the same trend.
Catches drift while it is still small
A problem building slowly across three waves is visible on a trend line long before it would show up as one bad reporting period.
Benchmarked against your own past, not an industry footnote
The comparison that matters most to most buyers is not "how do we compare to the market" — it is "are we getting better or worse than we were".
What you actually control
The switches you set once, before the first wave goes out
Follow-up is a schedule on the campaign you already built, not a separate system with its own rules. Three things decide how it behaves: how often it repeats, when it is allowed to reach people, and when it stops.
Frequency
Once, hourly, daily, weekly or monthly — set on the campaign and unchanged once waves have gone out, so a report always describes one consistent rhythm.
Quiet hours
A daily calling window, plus weekdays and specific dates you mark as off-limits — read in the campaign’s own timezone, never the browser’s, because a call is disruptive by where the phone rings, not where a dashboard happens to be open.
A stop rule
A wave closes on its own once it reaches the number of responses it was set up to collect, and pauses itself if the share of usable answers falls below a floor you set — it does not wait for someone to notice and turn it off by hand.
How it reports
Every wave lands beside the one before it
Each wave gets its own methodology block — sample source, field dates, contacted, valid and rejected counts — and the results view lines waves up against each other, so a topic’s volume and sentiment shift wave over wave is visible at a glance rather than something you build yourself in a spreadsheet.
Findings are directional only unless quota controls were applied and met — the same rule that governs one wave governs every wave in the sequence.
Consent is taken fresh every wave, never carried over from the last one, and a receipt is kept for each. Personal details are encrypted and never appear in a report. DPDP-aligned, and held in India.
Tell us the cadence you want to start with — we can always change it before the next wave goes out.