> 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/tutorials/fulfillment-survey.md).

# Fulfillment Survey

Automatically email surveys when an order is marked as fulfilled

Automatically send a survey to your customers when their order is marked as fulfilled. Post-purchase customers are significantly more likely to respond to surveys, making this an ideal time to collect feedback.

#### Step #1: Create Your Survey

1. Go to **Surveys → New Survey**. Enter a title for your survey.
2. For the delivery method, select **Order Fulfilled** from the template options.
3. Set the delay — we recommend sending the email **1 hour** after the order is fulfilled, but you can enter any value you prefer.
4. For the last step, select a template or build your own questions from scratch. We recommend a **Post Purchase** template or the **Attribution** template.

#### Step #2: Make Your Survey Live

Once you have previewed your survey and are happy with how it looks, flip the visibility switch on the top right hand corner. The survey will now automatically be emailed whenever an order is marked as fulfilled with the delay you specified.

{% hint style="warning" %}
Only orders fulfilled after the survey is live are emailed. Orders fulfilled earlier, or while the survey is hidden, are not. To reach past customers, send a campaign from **Campaigns → Email**. To change the trigger or delay later, go to **Settings → Delivery → Format**.
{% 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/tutorials/fulfillment-survey.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.