Clean contacts before anyone is asked
Fill In Missing Contact Names Automatically
Guest checkouts, booking forms that only ask for an email, a batch someone added in a hurry last year: contacts arrive without names, and review requests go out to them anyway. The fix is not better wording in the email; it is a routine upstream of it. Find the routes that create nameless contacts, give an automation the job of filling the name where it can, and park the rest in a list a person clears each week, so no request leaves until a name is set or someone decided it does not need one.
- Trace where nameless contacts come from
- Fill names by automation where you can
- Hold the rest in a list someone clears
The problem, solved
Where missing names come from, and what fixes each
Contacts and smart lists are on every plan. The automated parts need Pro.
Guest checkouts arrive with only an email
The store knows the name from the billing details, but the contact reaches StoryProof without it.
With StoryProof: Each automation has its own secure URL another tool can call. Check what your store sends to it, and whether the name travels with the order.
Contacts appear before anyone checks them
By the time someone notices a blank name, the request has already gone.
With StoryProof: An automation can start when a contact is created, so the check runs the moment a contact appears rather than at sending time.
The name exists in another system
Your CRM or booking tool has the customer’s name, and nobody wants to copy it across by hand.
With StoryProof: An automation can call any API with your own headers and authentication and use the response in later steps, and a contact action can fill in a name or business name.
Some names cannot be found anywhere
An enquiry form with only an email address leaves nothing to look up.
With StoryProof: A contact action can add a tag and put the contact on a Smart List, so nameless contacts wait in one place for a person to fill in.
Requests reach people we have not checked
A request automation that runs on every new contact does not know the name step has not finished.
With StoryProof: Start requests from the list of checked contacts instead of from contact creation. An automation can start when a contact joins a Smart List.
We cannot tell if the routine works
A silent failure means weeks of requests with blank greetings before anyone notices.
With StoryProof: Automation logs show every enrolment, every step that ran and why a run ended, kept for 30 days.
Flip the switch to see how StoryProof handles each one.
Team checklist
Set up the name routine
Run the first group with whoever knows your other tools, build the second in StoryProof, and hand the third to one owner.
Ticks stay in this browser tab. Nothing is saved or sent.
Contacts before and after the routine
Before
- Every new contact is asked at once
- Blank names found by customers, not by you
- Nobody knows which tool drops the name
- Fixes happen in the email wording
After
- Contacts are asked from a checked list
- Missing names wait in a list with an owner
- The worst source is known and fixed upstream
- The email reads from clean records
In StoryProof
Order of work
- You will need
- A StoryProof workspace on Pro or above
- Access to the tools that create your contacts
- 1
Give the owner the right access
Roles give each teammate only the parts of the workspace they need; the person clearing names needs contacts.
- 2
Build the check before the request
Publish the name automation first. Nothing runs until you publish, and work saves as you go.
- 3
Move requests onto the checked list
Change your request automation to start when a contact joins Ready to ask, and use the request step that skips anyone already asked.
- 4
Watch the first week
Read the logs daily for a week, then weekly.
What happens next: When the Needs name list stays near empty for a month, check the top source again; tools change their exports.
Before you start
What this routine cannot promise
Fields a condition can test
This page does not claim which contact fields a condition can check. Confirm it in the builder before relying on a name branch.
What another tool sends
Whether your store or CRM includes the customer’s name in its webhook or API response depends on that tool. Check its documentation.
Tests are live
From Pro, automations are built on a visual canvas or started from ready-made templates; work saves automatically and nothing runs until you publish. Running a test runs every step for real; it is not a dry run.
Logs are kept 30 days
Older runs are gone. Note anything you want to keep.
Names can be wrong, not just missing
An automation fills what it is given. A nickname or a company name in the source arrives as is.
FAQ
Questions people ask
Short answers to what usually comes up next.
Should I just send requests without a name?
Sometimes that is fine, with wording that does not need one. The routine lets you decide that per contact instead of by accident.
Where does the automation get the name from?
From a value you can reach in the builder, such as an API response from your CRM. Check in the builder which values the fill-in action can use.
What about a large batch of contacts added at once?
Check the names in the batch before you add it. Cleaning a list once is faster than clearing hundreds of contacts one by one afterwards.
Will this stop requests to people who were already asked?
That is a separate setting. The request step can skip anyone who already reviewed or was asked recently.
Still have a question? Ask the StoryProof team or book a demo.
Ask customers by name
Clean contacts automatically before a single request goes out.
Last updated 2026-11-19.