> For the complete documentation index, see [llms.txt](https://docs.zigpoll.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zigpoll.com/polls/nudge-non-responders.md).

# Nudge Non-Responders

Automatically send a one-time reminder to people who were sent or presented a survey but didn't respond

**Nudge Non-Responders** automatically sends one reminder to anyone who was sent or shown a survey but didn't respond. Most people who see a survey never answer it, so a reminder recovers responses you would otherwise lose, with no manual follow-up.

The reminder is **one-time** and **self-cancelling**. If the person responds before it goes out, it is skipped. Nobody who has already answered ever receives a nudge.

{% hint style="info" %}
This setting is configured per survey. Turn it on for each survey you want to nudge.
{% endhint %}

### Enabling it

1. Open your survey and go to **Settings → Workflows → Reminders**.
2. Turn on the **Nudge Non-Responders** toggle.
3. Set how long to wait before sending the reminder, in **hours** or **days**. The default is **1 day** after the survey is sent, which is when most people who are going to answer already have.
4. (Optional) Customize the reminder subject (email) or reminder message (SMS) — see [Customizing the reminder](#customizing-the-reminder) below.
5. Click **Save Changes**.

That's it. Eligible non-responders are followed up automatically on the schedule you set.

### How the reminder is delivered

The reminder is sent over the **same channel the survey was delivered on**:

* **Email surveys** (email campaigns, CSV email, Shopify customer-segment email) → a reminder **email**.
* **SMS surveys** (SMS campaigns, CSV SMS, Shopify customer-segment SMS) → a reminder **text message**.
* **Shopify post-purchase / on-site surveys** → a reminder **email**, sent when Zigpoll knows the customer's email for the order, such as the email captured at checkout. Post-purchase reminders are tracked per order. A returning customer who skips a later survey still gets a reminder for that new order.

A reminder needs a way to reach the person: an email address or phone number. Anonymous surveys have no recipient, so the Nudge Non-Responders card is hidden on them.

### Customizing the reminder

When you switch reminders on, the email reminder starts with its own subject line, *"Still have a minute?"*, so it does not read as the same email sent twice. SMS reminders reuse the original message. To change either, use the Nudge Non-Responders card:

* **Reminder subject** *(email surveys)* — a different subject line for the follow-up email, e.g. *"Quick reminder: we'd still love your feedback"*.
* **Reminder message** *(SMS surveys)* — a different text for the follow-up message.

Clear either field to resend the original subject or message instead.

Reminder emails use your survey's email design (colors, logo, header) — adjust it under **Settings → Design → Email** on your survey.

If your survey has [language settings](/polls/language-settings.md) configured, reminders go out in the same language as the original send.

### When a reminder is skipped

A nudge is **not** sent if:

* The person responds before the reminder is due (the reminder is cancelled the moment a response is recorded).
* The survey is anonymous.
* There is no email address or phone number to reach the person.

### Tracking nudges

Sent reminders are visible in two places:

* **Activity feed** — filter by **Survey Nudges** to see every reminder that was sent.
* **Participant timeline** — a *"Sent a nudge to: …"* entry appears on the participant's history, followed by their response if they came back and answered.

{% hint style="info" %}
Nudge reminders count toward your account's email and SMS sending limits, just like the original survey send. See [Subscription Plans](/subscription-plans.md) for limit details.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.zigpoll.com/polls/nudge-non-responders.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.