Why ATS Systems Miss Your Contact Info (And the 5-Second Fix)

I want to tell you about a candidate I almost ghosted by accident.

Senior software engineer. Strong background. Applied for a role at a Salesforce partner I was filling in 2021. Resume landed in our ATS, got a 74% keyword match score, cleared the first screening round. I flagged her profile for a recruiter phone screen.

Except the phone number in our system was blank. The email field showed a single broken character string.

She had put both in the header of her resume. Her name, phone, email, LinkedIn URL. All inside the document header section. Beautiful formatting. Clean design. And completely invisible to Workday’s parsing engine.

I found the contact info by opening the original PDF manually. But I was a thorough recruiter. Most aren’t. Most rely on what the ATS shows them. If the fields are empty, candidates don’t get called. They just disappear.

That’s what’s happening to a lot of job seekers right now.

The Number That Should Alarm You

A TopResume analysis of 1,000 resumes found that ATS systems fail to read header and footer contact information 25% of the time.

One in four resumes. The contact section that every single job seeker fills out. The part that costs nothing to include. Getting silently dropped by the software before a human ever sees the application.

This isn’t a formatting edge case. It’s a structural failure that affects a quarter of the people reading this article. And the fix takes five seconds if you know what to do.

Here’s the mechanic’s view of why this happens.

How ATS Systems Actually Read Your Resume

Most people think of an ATS as a search engine. Type in “Python developer,” get results. That’s part of it. But before keyword matching happens, the system runs a parsing process: it breaks your document into structured data fields.

Name. Contact Information. Work History. Education. Skills.

Each of those fields gets populated from the raw text of your resume. The parser scans for patterns. Email addresses follow a recognizable format (text@domain.com). Phone numbers follow regional formats. LinkedIn URLs follow a recognizable structure.

Here’s the problem with document headers.

In Microsoft Word and Google Docs, document headers are a separate layer from the body text. They sit in a different part of the file structure. When Workday, Greenhouse, Lever, or iCIMS ingests your resume, the parser reads the body of the document. The header is treated as metadata, not content.

Some ATS systems handle this well. Some don’t. The systems that don’t? They read your name from the first line of body text, then start scanning for contact info. If your contact information only exists in the header, those fields come back empty.

You get flagged in the system as an incomplete application. Depending on the recruiter’s workflow, that might mean a follow-up. More often it means you get skipped.

The same resume. The same qualifications. Different formatting choices. Wildly different outcomes.

This is Zone 1 failure in my Three-Zone ATS framework. If the system can’t even parse your document correctly, you never reach keyword matching. You never reach human review. You lose before the game starts.

The Four Contact Info Mistakes That Kill Applications

It’s not just headers. Here are the four formatting choices that cause contact information to disappear inside ATS systems.

Mistake 1: Putting Contact Info Inside a Document Header

The most common. People design their resume with their name and contact info in the document header section (Insert > Header in Word, or the equivalent). It looks professional. Clean margins. Visually consistent. And it breaks parsing.

The fix: Delete the header. Put your name, email, phone, and LinkedIn URL as the first lines of body text. Physically type them into the document body. Not in a text box. Not in a header. In the body.

Mistake 2: Using Text Boxes

Design-forward resumes often use text boxes to create visual layouts. Two columns, styled name plates, sidebar sections. Text boxes are another parsing nightmare.

ATS systems read content sequentially. When text exists inside a text box, the parser often reads the box’s contents separately from the surrounding text, or skips it entirely. Contact info in a text box becomes unpredictable. Sometimes it shows up. Sometimes it doesn’t.

The fix: Convert text boxes to regular paragraph text. Lose the sidebar layouts. I know this sounds like you’re making your resume uglier. You are making it more reliable. Those are different things, and reliability matters more.

Mistake 3: Using Image-Based Contact Icons

Modern resume templates love the little icons. A phone handset before your phone number. An envelope before your email. A LinkedIn logo before your URL. These look sharp in a PDF. They mean nothing to an ATS.

Some systems read through images to grab adjacent text. Others treat the entire element as non-parseable and skip it. When your phone number is formatted as [image] 416-555-0142, the parser may extract “416-555-0142” or it may extract nothing at all.

The fix: No icons. Just the text. Your phone number is a phone number. Your email is an email. ATS systems recognize them without visual decoration.

Mistake 4: Formatting Phone Numbers in Unusual Ways

This one sounds minor. It isn’t. ATS parsers recognize phone numbers by matching against standard formats. North American numbers: (416) 555-0142, 416-555-0142, 416.555.0142, +1-416-555-0142. These all work.

What doesn’t work: 416 555 0142 with unusual spacing, numbers split across lines, extensions formatted in non-standard ways, or international formats that the parser’s regional settings don’t recognize.

The fix: Use standard dashes or dots. Keep the entire number on one line. No line breaks, no unusual spacing.

The 5-Second Contact Info Test

Before you submit your next application, do this. It takes less than five seconds.

Open your resume. Copy it into a plain text editor (Notepad on Windows, TextEdit in plain text mode on Mac). If your contact information disappears or turns into gibberish when you paste into plain text, your ATS parser is going to have the same problem.

Plain text strips all formatting. What remains is what ATS systems actually read.

Your contact section should look like this in plain text:

Jane Smith
jane.smith@gmail.com | 416-555-0142 | linkedin.com/in/janesmith | Toronto, ON

If you see broken characters, blank fields, or missing information, your resume has a Zone 1 failure. Fix the formatting before you send another application.

What Fully Compliant Contact Info Looks Like

Here’s the template. Copy this structure exactly.

Line 1: Your full name (in body text, slightly larger font if you want, but not in a document header)

Line 2: Email | Phone | LinkedIn URL | City, Province/State

What to include:

• Professional email address (firstname.lastname@gmail.com format)
• Phone number in standard format
• LinkedIn URL (the clean version: linkedin.com/in/yourname)
• City and province or state (just city and region, not your full street address)

What to omit:

• Street address (unnecessary, creates privacy risk, wastes space)
• Multiple phone numbers (one is enough)
• Social media handles other than LinkedIn (unless directly relevant to the role)

Where ATS Failures Really Cost You

Contact info failures aren’t equally distributed across all job applications. They’re worse in high-volume hiring environments.

When a company posts a role on Indeed, LinkedIn, and their careers page simultaneously, they might receive 500 to 2,000 applications in the first 48 hours. Recruiters aren’t manually opening 2,000 PDFs. They’re working from the parsed data that the ATS presents.

Filtered views. Ranked lists. Candidate cards generated from extracted fields.

If your contact fields are blank, you don’t appear in those filtered views the way complete applications do. In some ATS workflows, incomplete applications get auto-deprioritized or require manual intervention to surface. At volume, manual intervention doesn’t happen. Recruiters work from the clean data.

This is why you can have a strong resume that scores well on keyword matching and still never hear back. Your application is technically in the system. But your contact data is invisible, and no one can reach you even if they wanted to.

99% of Fortune 500 companies use ATS software, according to TopResume’s analysis. You are not getting around this layer. You need to work with it.

How to Test Your Resume Before Applying

The plain text test catches obvious formatting failures. But it doesn’t catch every ATS parsing error.

For a more thorough check, run your resume through JobCanvas. Sign up free, upload your resume, and the ATS analysis will show a field-by-field breakdown of what the parser extracted. If your contact fields show up blank or malformed, you’ll see it before a recruiter does. The check takes 30 seconds.

The Rest of the Parsing Checklist

While you’re fixing your contact info, run through this. These are the other Zone 1 failures I see consistently.

Section Headers: Use standard names. “Work Experience” or “Professional Experience,” not “My Journey” or “What I’ve Done.” ATS systems have pattern libraries for section names. Custom headers don’t match those patterns.

File Format: Submit .docx unless the job posting specifically requests PDF. Word format gives parsers a structural document map. PDF rendering is more variable. Some ATS systems handle PDF well. Some don’t. .docx is the safer default.

Font: Stick to system fonts. Arial, Calibri, Times New Roman, Georgia. Embedded custom fonts can render inconsistently depending on whether the parser’s environment has that font installed.

Tables: Same issue as text boxes. Table cells are parsed sequentially and often incorrectly. If your resume uses a table layout for dates, job titles, or any content, convert it to regular text.

Columns: Two-column resume formats are design traps. ATS systems read columns left to right across the full width, not column by column. A two-column layout that puts your work history on the left and your skills on the right will get read as: “[company name] [skill] [job title] [skill] [date] [skill].” That’s incoherent to a keyword matcher.

The skills section topic is covered in depth in The Resume Skills Section Nobody Reads (And What to Do Instead), which covers how to structure the section that ATS systems scan first.

Why “ATS-Friendly” Resume Templates Aren’t

Here’s the part that will make you angry.

Most resume templates marketed as “ATS-friendly” on Canva, Zety, and similar platforms are not ATS-friendly. They’re visually formatted templates that look clean to humans and fail parsing tests.

The icons, the dividers, the two-column layouts, the custom headers. All design choices that market well to job seekers who don’t know what ATS parsers actually do. The templates sell because they look professional. They underperform because professional appearance has nothing to do with parsing compliance.

I’ve tested dozens of these templates through ATS simulators. The ones that look the most polished tend to score the worst.

The templates that actually work look boring. Plain single column. Standard fonts. Clean section headers. No icons. No text boxes. No decorative elements that sit outside the main document body.

If your resume looks like it was designed in 2009, it probably parses correctly. If it looks like a modern design portfolio, it probably doesn’t.

That’s the trade-off. You’re not building something for a human to admire. You’re building something for a machine to read accurately. Make peace with that, fix the formatting, and let your actual qualifications do the work.

For context on the broader ATS landscape and how skills-based filtering has changed the game, Skills-Based Filtering: The 2026 ATS Trend That Changed Everything is worth reading alongside this.

The Bottom Line

75% of job applications don’t reach human reviewers. The ATS filter is where most resumes die.

Your contact information is the piece that makes everything else matter. Pass the keyword match, pass the skills scan, and then have empty contact fields because your email was in the document header. That’s not a skills problem. That’s a formatting problem with a five-second fix.

Delete the document header. Move your contact info to the body of the document. Run the plain text test. That’s the fix.

Then you can stop wondering why you’re not hearing back.

Fix Zone 1 first. Everything else builds on it.