"I never got your email"
Fix Testimonial Request Emails in Spam
A customer who promised feedback says your request never came, and then finds it in their junk folder. Spam filtering is decided by the receiving mailbox, so nobody can switch it off for you. What you can do is remove the reasons a filter has to doubt the message. The checklist below covers the parts you control, in the order worth testing them.
- Checks you can run today without a developer
- Your sending domain, your wording, your list
- A fallback when a request still goes missing
The problem, solved
Why a request disappears, and what StoryProof lets you do about it
None of these promise inbox placement. They remove reasons for a filter or a customer to doubt the message.
Situation 1 of 5
They do not recognise who it is from
A customer who bought from "Sam at the bakery" gets a request from an address they have never seen and reports it.
How StoryProof solves it
The collection link can be shared by hand, so you can paste it into a reply on a thread the customer already knows, from your own mailbox.
Situation 2 of 5
We sent it to everyone we ever served
Old addresses bounce and long quiet contacts ignore or flag the email, which does the sender no favours with the next recipient.
How StoryProof solves it
Contacts and smart lists are on every plan, so requests can go to the recent customers you choose rather than an old export.
Situation 3 of 5
Reminders arrive at odd hours, again and again
Repeated chasers at three in the morning look like a machine, and annoyed customers press the spam button rather than reply.
How StoryProof solves it
From Pro, follow-ups send only inside the quiet hours you set, skip anyone who unsubscribed and stop once the customer leaves a testimonial.
Situation 4 of 5
The email is gone and they are in front of you
At a handover or an appointment, a customer is happy to help but cannot find the message anywhere.
How StoryProof solves it
The same link can be printed as a QR code, so they can open it on their phone there and then without any email.
Situation 5 of 5
We assumed a text would get through instead
Switching channel feels like the answer when email fails, but it changes the tools and the permissions you need.
How StoryProof solves it
StoryProof sends review requests by email only and does not send SMS. For other channels, copy the link and send it yourself.
Deliverability checks
Work through what you control
Start with the test send: it tells you whether the problem is everywhere or only for some customers. Stop at the first item you cannot tick and fix that before moving on.
Your ticks stay in this browser tab and are not sent anywhere.
The same request, written for a filter and a busy person
Easy to doubt
- Subject: "FREE GIFT for your REVIEW!!!"
- Sent from a no-reply address the customer has never seen
- Three links, an attached PDF and a large banner image
- Mailed to every contact since the business opened
Easy to trust
- Subject: "Quick favour after your project, Ana?"
- Sent from the person they worked with, on your usual domain
- One link to your collection page, no attachments
- Sent to customers from the last few weeks only
In StoryProof
Send requests that are easier to trust
- 1
Test before the real send
Send the request to your own test addresses first and look in spam as well as the inbox.
- 2
Choose a recent, small list
Add the customers you served lately as contacts and send to them rather than to an old export.
- 3
Use the personal route for key customers
Copy the collection link into a reply on a thread they already know, from your own mailbox. They can answer with video, audio or text.
- 4
Keep reminders polite and timed
From Pro, follow-ups wait days between emails, respect your quiet hours, skip anyone who unsubscribed and stop once a testimonial arrives.
What happens next: If one customer still says nothing arrived, do not resend the same email three times. Send the link once by hand, or show them the QR code next time you meet.
Before you start
What nobody can promise
Filters belong to the recipient
Gmail, Outlook and company filters make their own decisions. Every check here lowers the odds of a request being filtered; none removes them.
No claim about StoryProof’s sending setup
This page does not describe how StoryProof’s own request emails are sent or authenticated. If you need that detail, ask StoryProof support.
Domain records need care
Changing SPF or DKIM records wrongly can break your normal email. Ask whoever manages your domain before editing them.
Not legal advice
Email rules on consent and unsubscribing vary by country. This page covers delivery checks, not your obligations under those rules.
FAQ
Questions people ask
Short answers to what usually comes up next.
Does StoryProof send requests from my own domain?
This page makes no claim either way. Ask StoryProof support about the sending setup. If you want the request to come from your domain today, copy the collection link and send it from your own mailbox.
Will adding a reward make the email more likely to be opened?
Prize wording in a subject line is one of the patterns filters and people distrust. If you offer a thank-you, mention it plainly in the body, not the subject.
Should I ask customers to check their spam folder?
For one or two people, yes, and ask them to mark your address as safe. If many customers need telling, fix the causes in the checklist first.
How do I know if SPF and DKIM are working?
Send a test to a Gmail address, open the message and choose to show the original. The summary lists whether SPF and DKIM passed for your domain.
Still have a question? Ask the StoryProof team or book a demo.
Send requests customers recognise
Share your collection link from your own inbox, by QR code or by email, and keep reminders polite and timed.