# Sending a survey (/en/businesses/marketing/surveys/sending)

A survey reaches customers in three ways. An email gives each customer their own link, which knows who they are without signing in. The shared link and its QR code work for anyone. A workflow sends the survey to each customer at the right moment, such as the day after a class.

---

## By email and push [#by-email-and-push]

**Send** on the survey's page starts a new [email](/businesses/marketing/emails) with the survey in it. You choose the recipients and the email type as for any email, and each recipient gets their own link.

The survey in the email shows as a **Button**, or as its **First question** with numbers to click when the survey starts with a rating or a Net Promoter Score question. A customer who clicks a number lands in the survey with that score picked.

**Answers are about** ties the answers to a course group, such as the course you are asking about. **Also send a push notification** asks the customers who use the Thril app in the app too, and opens the survey there.

**Personal links expire after** decides how long the link in each email works.

---

## With the link and QR code [#with-the-link-and-qr-code]

**Link and QR code** on the **Sharing** tab has the survey's shared link, its QR code and an **A4 poster** with the code to print. Use them where you can't email: at reception, courtside, on a screen after the last class, in a newsletter from another tool.

A customer signed in to Thril answers under their name, unless the survey is anonymous. Others answer without a name, or leave their email at the end if you **Ask for email at the end**.

For a link and QR code about one course group, pick it in **Answers are about**. Answers through that link show under the course group.

---

## Automatically, with workflows [#automatically-with-workflows]

**Add an automation** on the **Sharing** tab creates a draft [workflow](/businesses/marketing/workflows) with the survey already picked. Check the email, then publish the workflow.

| Automation                             | Who gets the survey                                                                           |
| -------------------------------------- | --------------------------------------------------------------------------------------------- |
| **After an event**                     | Each customer marked present at an event or class, the day after                              |
| **After a court booking**              | Each player on the booking, the day after it ends                                             |
| **After a coaching session**           | The customer, the day after their coaching session ends                                       |
| **When someone joins a customer list** | Each customer a day after they join the [list](/businesses/marketing/customer-lists) you pick |

Each answer is about the event, course, court booking or coaching session that started the workflow. Answers about an event or a course also show on its page. A survey asked at some of your venues goes out only from those venues. A customer who joins a list gets it from one of them. A survey that is closed when the workflow reaches it sends nothing.

### Acting on an answer [#acting-on-an-answer]

Two automations start when a customer answers. **Thank respondents with credits** gives credits and sends a thank-you email. **Follow up on low scores** creates a task for staff to get in touch with a customer who gave a low score.

Both build on the **Customer answers a survey** trigger. Its conditions read the score a customer gave to a question, or the options they picked, so a workflow can email a promoter a link to your Google reviews, or add a customer who wants private lessons to a list. An anonymous survey doesn't say who answered, and its answers start no workflows.

<Callout type="warn">
  Reward the act of answering, never the score. A reward for good scores makes
  your results worthless.
</Callout>