Responses are coming in but no email arrives. Work through these in order — the first cause accounts for most cases.
1. The recipient list is empty on a brand-new install
a fresh install ships with email notifications enabled but with no recipient addresses saved. The switch looks correct, but there is nobody to send to, so nothing is ever delivered. Until you open Notification settings and save at least one address, notifications cannot work.
- Open Drip Surveys and go to Notification settings.
- Look at the Emails field. If it is blank, that is your answer.
- Enter the address that should receive alerts.
- Click Save.
The field is required, so as soon as you save anything on that page you are forced to fill it in.
2. Notifications are switched off
Confirm Enable email notifications is ticked on the Notification settings page and save if you changed it.
3. A bad address in the list
Recipients are entered as a single comma-separated list. Every address in that list is used as a recipient.
- Check each address for typos.
- Remove any stray comma, which produces an empty recipient.
- Remember the whole field is capped at 255 characters. A long list can be truncated, silently dropping the addresses at the end.
4. The email was delivered but filtered
Check the spam or junk folder of the recipient inbox, and any inbox rules that might be moving the message.
5. Delivery failed silently
The notification email is sent inside the response submission request, not from a background queue. If the mail server rejects it, nothing in the app tells you. The response is still saved. If you have ruled out everything above, this is the remaining possibility and you should contact support.
Confirm it end to end
- Make sure your survey is live and can be submitted.
- Place a test order and submit a response.
- Confirm the response appears on the Responses page.
- Check the recipient inbox, spam included.
Good to know
- Responses are always saved to your dashboard even when the email does not arrive, so feedback is never lost.
- A typo in a
%customer_name%token does not stop the email. It just sends the literal token text.