Auto replies to testimonial requests
Requests Hitting Out of Office Replies
You send a testimonial request and an auto reply comes straight back: away until the 14th. The customer has not said no. They have not seen it yet, and by the time they do, two reminders may be stacked on top of it. StoryProof does not read replies or spot auto replies, so this is a routine for you: notice the return date, stop the pile up, and ask again when they are back. From Pro, automations do the waiting for you.
- Note the return date from the auto reply
- Ask again a few days after they are back
- Plan longer waits around holidays
The problem, solved
What an away message does to your ask
None of these is the customer refusing. Each is a timing problem you can fix.
Situation 1 of 5
They come back to three of our emails
A request plus two reminders, all unread, looks like pressure from a stranger rather than a friendly ask.
How StoryProof solves it
From Pro, the follow-ups automation can send only during working hours, skip weekends and cap how often one person hears from you.
Situation 2 of 5
We know the date they are back
The auto reply told you exactly when to try again, and that information usually goes nowhere.
How StoryProof solves it
Add the customer by hand to an automation that waits the number of days or weeks you choose, then sends the ask.
Situation 3 of 5
Our holiday send is half away messages
A request sent the week everyone leaves gets treated as silence by a reminder that fires a few days later.
How StoryProof solves it
Build the reminder on the no response trigger, with a number of days you choose, so a holiday send waits longer before chasing.
Situation 4 of 5
We cannot tell what they already received
Before asking again, you need to know which emails reached them and which are still queued.
How StoryProof solves it
Automation logs show every enrolment and every step that ran, with the reason a run ended.
Situation 5 of 5
They replied “ask me when I’m back”
Some customers answer the request by hand before they leave, and a formal resend would feel cold.
How StoryProof solves it
The collection link can be shared by hand, so you can paste it into a personal note on the day they return.
Auto reply routine
What to do when a request gets an away message
Keep this next to the inbox where replies to your requests arrive.
Ticks stay in this browser tab. Nothing is saved or sent.
Reading the auto reply
Away messages say different things. What each one means for your request.
In StoryProof
Set up a return-date resend
- 1
Check what is queued
Open the automation logs to see which request and reminder steps have run for this customer.
- 2
Create a resend automation once
Start it when you add people by hand, add a wait of days or weeks, then send an email with merge tags and your collection link.
- 3
Add the customer when an away message lands
Enrol them by hand and set the wait so the email arrives a few working days after their return.
- 4
Keep reminders gentle
Turn on quiet hours, weekend skipping and a per-person cap so a customer just back never gets two emails in a day.
What happens next: If they still do not answer after the fresh ask, let it go for this round. A customer who was simply busy is a good candidate for next quarter.
Before you start
What StoryProof does not do here
No auto reply detection
StoryProof is not described as reading replies or recognising away messages. You spot them in the inbox your replies go to.
It does not read the return date
You type the wait yourself. Nothing parses dates out of an away message.
Recently asked customers can be skipped
The review request action skips anyone asked recently. For a resend soon after the first ask, send an email with your collection link instead.
Plan dependent
Automations, waits and quiet hours are available from Pro.
FAQ
Questions people ask
Short answers to what usually comes up next.
Does an out of office reply count as a response?
Not to StoryProof. The request is not completed until the customer leaves a testimonial, so reminders still run unless you plan around the absence.
Should I reply to the auto reply?
No. Nobody reads it while they are away. Put your effort into a fresh email that arrives after they are back.
How long after their return should I ask again?
A few working days. Their first morning back is spent clearing urgent mail, and a testimonial request will not be on that list.
What if I get away messages from half my list?
That is a sign the send went out at a holiday peak. Move the next batch to a quieter week and give reminders a longer no response window.
Can I forward the request to the colleague the auto reply names?
Only if that colleague worked with you too and could give their own testimonial. Otherwise wait for the person you actually asked.
Still have a question? Ask the StoryProof team or book a demo.
Ask again when they are actually back
Use waits, manual enrolment and quiet hours so an away message delays the ask instead of ending it.
Last updated 2026-11-20.