gmial.com, hotmal.co, and a missing dot
Typos in Customer Email Addresses
A bounced request is the lucky outcome. The unlucky one is a typo that happens to be someone else’s real inbox: a stranger gets your customer’s name, your branding and an invitation to praise a service they never used. Most typos are made once, at checkout or at the front desk, and then copied into every list you build. Clean them before the request goes out, using the checklist below.
- Spot the common typo patterns
- Fix them where they were typed
- Contain a request sent to a stranger
The problem, solved
Where a mistyped address does its damage
Typos are cheap to make and expensive to send to. These are the cases worth planning for, and what StoryProof does in each.
Situation 1 of 5
The same bad address keeps coming back
You fix it in the request list, then the next export from the booking system brings the typo straight back.
How StoryProof solves it
Contacts and smart lists are on every plan. Correct the contact in StoryProof and in the system it came from on the same day, so the next import agrees.
Situation 2 of 5
A request went to a stranger
The typo was a real address. Someone with no idea who you are now has your customer’s first name and a request to praise you.
How StoryProof solves it
Nothing a customer submits goes public until you approve it, so if the stranger replies, their answer sits in your queue rather than on your site.
Situation 3 of 5
We cannot tell the wrong inbox to stop
Follow up reminders keep going to the stranger, which turns one mistake into three.
How StoryProof solves it
From Pro, an automation can remove a contact from Smart Lists or unsubscribe them, so the wrong address stops getting reminders.
Situation 4 of 5
We only find out weeks later
A typo that bounces sits unnoticed in a dashboard until someone wonders why responses are low.
How StoryProof solves it
From Pro, an automation can start when a request bounces, so a likely typo reaches someone the same day.
Situation 5 of 5
The customer is in front of us now
At the counter or at the end of a job, spelling an address aloud is where most typos start.
How StoryProof solves it
StoryProof sends requests by email only, but the collection link can also be shared by hand or printed as a QR code, so the customer can open it themselves.
Before you press send
Typo address check
Run through this list on any batch of customer addresses before they get a request, and once on the form or desk where addresses are captured.
This checklist runs in your browser. It does not read or store any address.
An apology to someone who got your request by mistake
Sample wording, illustrative only
Hello, you received an email from us this week asking about a recent visit. It was meant for one of our customers and reached you because of a typing mistake on our side.
We have removed your address and you will not hear from us again. Sorry for the bother, and thank you for letting us know.
In StoryProof
Keep typo addresses out of StoryProof
- 1
Check the batch before adding it
Run the checklist on the export before it becomes contacts, and correct what you find at the source.
- 2
Catch the ones that slip through
On a plan with automations, start a flow when a request bounces and alert whoever owns the list.
- 3
Stop mail to a wrong address
Remove the contact from its lists or unsubscribe it, so no reminder follows the first mistake.
- 4
Keep stray replies unapproved
If someone who is not a customer replies through the link, leave it unapproved and then reject it.
What happens next: Once a month, look at where your typos came from. If one form or one desk produces most of them, change how addresses are captured there.
Before you start
What StoryProof does not do here
No address validation is claimed
This page does not claim StoryProof checks or corrects addresses for you. The checks above are done by a person or in your own tools.
Bounces do not catch real typos
A typo that is somebody else’s working inbox will not bounce. Only checking before you send prevents it.
It cannot recall a sent email
Once a request is delivered, it is in that inbox. You can stop what follows, not what already arrived.
No SMS fallback
Requests are email only. If you cannot get a good address, share the link by hand or with a QR code instead.
FAQ
Questions people ask
Short answers to what usually comes up next.
What are the most common typos in customer email addresses?
Misspelled popular domains, a wrong ending such as .con instead of .com, stray spaces or commas, and names with two letters swapped. Sorting a list by domain makes most of them easy to see.
What should I do if a stranger fills in my review form?
Do not approve it. Thank them if they wrote to you, explain it was sent by mistake, stop further emails to their address, and reject the submission.
Is it better to ask customers to type their own address?
Usually, yes. People rarely mistype their own address, and they cannot misspell it the way a person listening over a noisy counter might.
How is this different from cleaning up bounces?
Bounces tell you after the fact that an address does not exist. This page is about checking before you send, including typos that reach a real person and never bounce.
Still have a question? Ask the StoryProof team or book a demo.
Send requests to the inbox you meant
Keep contacts tidy, catch problems fast, and keep anything a stranger sends off your site.
Last updated 2026-11-20.