10 min read
You uploaded a resume that looks perfect on your screen. The Workday preview shows your skills block and your last employer, but the phone field is empty. You're not imagining it. The parser read your file and didn't map a callable number into the contact slot. That's a silent failure, and it's more common than most candidates expect on US corporate reqs.
Before you reformat your whole resume, check your resume for free on the exact export you'll upload tonight. You're not chasing a vanity score. You're confirming whether your digits survive extraction. This page walks the symptom, three causes, how to tell which one is yours, and the fix for each.
Job searching is already draining. You don't need a qualified file dying because your phone number sat in a header the parser skipped. The fix is usually ten minutes of contact-block cleanup, not a new template. And you won't need to guess which cause fits. The paste test below sorts it fast.
So if you've been wondering why callbacks never come even when you're a fit, start here. Recruiters can't call a blank field. They'll email if they have time. Many won't chase a missing number when the queue is full.
Quick Wins
- Move phone, email, and city to line one of the body, not the Word header.
- Paste your resume into Notepad and Ctrl+F your area code.
- Strip slashes, spelled-out digits, and extension words that aren't x1234.
The symptom: your resume looks fine, the contact field doesn't
The clearest sign is the employer portal preview. You upload a PDF or DOCX. The parsed profile shows your name, maybe your email, and a blank phone slot. On Greenhouse you sometimes see digits jammed into the summary field instead of the phone field. On Workday the number might appear once in a sidebar preview and vanish on the recruiter's view.
You can still look qualified while being unreachable. The experience section parsed. Keywords matched. Nobody can call you without digging through email threads. That delay costs screens when the req moves fast.
Candidates often blame the ATS brand. Workday, iCIMS, Lever, and Taleo all extract phone numbers with pattern rules, but they only see character strings the file actually exports. If your number never becomes plain text, no parser invents it.
I've screened files where the PDF header showed a clean (312) 555-0142 and the imported profile had nothing. The recruiter assumed the candidate didn't care enough to include a number. The candidate assumed the PDF was the source of truth. Both were wrong about where the failure lived.
Read why your Workday resume looks different after upload when the whole preview is scrambled, not just the phone field. The paste test still starts with your area code.
A composite customer success manager kept getting email-only follow-ups from agencies. Her Canva PDF looked polished. Plain-text paste showed no digits at all. The icon row above her name was a graphic. Until she rebuilt in Word, every ATS treated her as email-only.
Another pattern: the number imports as one long string with no separators, like 3125550142. Some portals accept that. Others drop it as invalid. Standard US formatting removes that ambiguity.
Why ATS can't read your phone number sometimes: three causes and fixes
Missing phone data is almost always one of three problems. They're mechanical. None of them require a paid template or a new career story.
Cause 1: the number lives where parsers don't read
Symptom: PDF looks perfect. Paste into Notepad skips the first three lines or jumps straight to Experience. Your phone never appears in the pasted text.
Before: Name and phone sit in a Word header or footer, or inside a text box under a colored banner.
After: Name on line one, phone and email on line two, city and state on line three, all in the body with normal paragraph returns.
Headers and footers are invisible to many US parsers. So are text boxes, shape layers, and icon rows from design tools. The visual layer survives export. The character layer does not.
Before: Two-column contact table with phone in the right cell next to a LinkedIn icon.
After: Single-column contact lines separated by a middle dot or pipe character, typed as plain text.
Fix: open the master DOCX. Click into the body, not the header. Retype the number. Delete the header version. Re-export PDF and run the paste test on both files.
Cause 2: separators and words parsers don't expect
Symptom: digits appear in paste, but the ATS preview still shows a blank or garbled phone field. You used creative formatting that humans parse fine and machines don't.
Slashes, mixed dots and parentheses, spelled-out numbers, and extension prose are the usual triggers. 312/555/0142 reads as three unrelated chunks. One-two-three-four-five-six reads as words, not a callable string.
Before: Cell: 312.555.0142 / ext. four two one
After: 312-555-0142 x421
Fix: pick one separator style and keep it consistent. Dashes or parentheses around the area code both work on most US portals. Put extensions as x plus digits with no spaces inside the extension. Drop call me at and mobile: labels unless the portal has a dedicated label field.
Cause 3: image-only PDF or scan
Symptom: you can't select the phone number with your cursor in the PDF. Search for your area code inside the file returns no hits. The resume is a picture, not text.
Scanned paper, phone photos, and some design-tool exports create this. Keywords and phone data both die the same way. No amount of parentheses tuning fixes an image layer.
Fix: rebuild as typed text in Word or Google Docs. Save DOCX. Export a text-based PDF. Paste test until Ctrl+F finds your area code in Notepad. Read US resume file type for ATS when you're choosing which export to upload after the rebuild.
How to tell which cause is yours
Sixty-second paste test: open your upload file, select all, copy, paste into Notepad or TextEdit plain mode. Search for your area code.
No digits at all? Cause 1 or 3. Digits you can't select in the PDF before pasting? Cause 3. Digits present but weirdly formatted? Cause 2. Digits clean in paste but missing in preview? Check whether they're attached to a label word the parser strips, then simplify.
If the portal shows a preview step, screenshot it. Compare to your paste. That pairing ends arguments about whether the problem is your file or the employer config.
Fix for cause 1: copy-paste contact header
Copy-paste this block at the top of your body text and replace the bracketed pieces:
Jordan Lee (503) 555-0198 · [email protected] · Portland, OR linkedin.com/in/jordanlee EXPERIENCE Customer Success Manager | Relay Analytics | Mar 2021 to Present • Cut onboarding time from 21 days to 14 by rebuilding the kickoff checklist in Zendesk
No tables, no icons, no header field. Export DOCX and PDF from this same source. Paste both before you upload to Greenhouse or Workday.
Fix for cause 2: standard US formats that parse
Pick one line and stick with it across every application this month:
- (503) 555-0198
- 503-555-0198
- 503.555.0198
- +1 503-555-0198 for international applicants on US reqs
Avoid 503/555/0198, 503 555 0198 with double spaces, and 1-503-555-0198 unless the portal form expects it. Match the web form when you manually retype the number after upload.
Fix for cause 3: rebuild from text
Retype the resume in a single-column Word file. Eleven-point Calibri or Arial. No scanned signatures in the contact area. Export fresh. Run the checker on the new file before you retire the old PDF on your desktop.
Before and after: registered nurse contact line
Before: Phone listed as five-zero-three five-five-five oh-one-nine-eight under a stethoscope clip art banner in the header.
After: (503) 555-0198 on line two of the body under the legal name, RN license line on line three.
Before and after: warehouse supervisor upload
Before: Photo PDF from a phone camera, number visible but not selectable, Lever preview empty.
After: Typed DOCX with 503-555-0198 on its own line, PDF exported from Word, paste test passes, Lever phone field fills.
Edge case: two numbers on one line
Work and mobile on the same row confuse field mapping. List one primary number for applications. Add a second line only if you truly answer both. Most recruiters call the first number they see.
Edge case: online application form mismatch
Some portals strip punctuation and want ten digits only in the form box. Keep the formatted version on the resume and match the form's rules in the web field. If the form won't accept parentheses, type digits only there even when the resume uses dashes.
Edge case: Google Voice and VOIP numbers
VOIP numbers are valid when they're standard US ten-digit strings. Format them like a mobile line. Don't add app names or provider labels in the contact row. The parser cares about digits, not which app rings.
After you fix the file: re-upload discipline
Save the corrected export with a version suffix in your folder, not Resume_Final.pdf. Upload once per req. If the preview still drops the number, try DOCX when the posting allows Word. Read formatting mistakes that kill parser reads when other fields scramble too.
Where contact blocks quietly break
Hyperlinking the phone number. tel: links sometimes paste as URLs without exposing the digit string. Type the number as plain characters.
Non-breaking spaces around dashes. They look normal in Word and vanish oddly in paste. Retype the line manually if paste looks off.
Country codes on domestic US reqs. +44 or +91 on a US-only role can make parsers treat the field as international and drop it. Use a US line you actually answer for US applications.
Putting phone inside the summary paragraph. Some systems map the first paragraph to a summary field and never backfill phone. Keep contact lines above the summary.
Relying on the online profile alone. LinkedIn URL in the contact row is fine as text. Don't assume a social profile replaces a callable number on the resume file.
Using a fax or office main line you don't answer. Recruiters won't leave three voicemails on a front desk. List the mobile you pick up during business hours.
Font tricks. White text on white background, zero-width characters, or condensed spacing can hide digits from extraction. If paste looks wrong, retype from scratch.
Verify the number before you submit
Upload the same export to the free ATS checker and confirm the contact section populates. You're checking extraction, not keyword density.
If you're rebuilding from scratch, build your resume in a single-column layout with the contact block wired for parsers, then save DOCX and PDF from one source.
When the posting asks for a cover letter, draft it after your phone field passes the paste test. Use the cover letter generator so you're not fixing contact issues and rewriting a letter in the same panic hour.
Screenshot the employer preview when you get one. If a recruiter later says the number was missing, you have a timestamped record that your upload parsed correctly on your side.
Make the number impossible to miss
Why ATS can't read your phone number sometimes (US fix) comes down to text the parser can actually see. Headers, scans, and creative separators fail for different reasons, but the paste test sorts them in one minute.
Open your upload file tonight. Paste into Notepad. If your area code isn't there, move the digits into the body and re-export. If it's there but ugly, standardize the format. If you can't select the digits at all, rebuild as typed text.
This won't fix applying to roles you're not qualified for. It stops qualified candidates from sitting in a maybe pile because nobody could reach them. Recruiters move on when contact data is blank.
When the paste test passes, run the free resume check on that same file before you hit submit. One clean upload beats three hopeful retries with the same broken header.
Read more
Frequently asked questions
Use a ten-digit US number with a three-digit area code in one of these plain styles: (312) 555-0142, 312-555-0142, or 312.555.0142 with consistent separators. Put it on its own line in the body under your name, not inside a table cell or icon row. Avoid slashes, spelled-out digits, and country codes unless you are applying from outside the US.
No for most US corporate ATS uploads. Workday, Greenhouse, and Taleo parsers often skip header and footer regions, so a number that looks perfect on the PDF can import as blank. Repeat name, phone, and email on line one of the body text. If the paste test finds your number, the header placement is less risky but still not worth betting on.
+1 is fine when formatted as +1 312-555-0142 with a space after the country code. Avoid 001, double plus signs, or running +1 directly into parentheses with no space. If the posting is US-only and you live in the US, you can omit +1 entirely. Consistency matters more than whether the country code appears.
The preview reads extracted text, not what your eyes see. Numbers inside text boxes, graphics, or image headers do not export as characters. Run Ctrl+A on the PDF and paste into Notepad. If the digits are missing there, the ATS preview will miss them too. Rebuild the contact block as typed body text.
Yes. Paste your resume into plain text and search for the area code. Upload the same file to HireFlow's free checker and confirm the contact field populates. Some employer portals show a parsed preview after upload. Screenshot that preview when it appears so you have proof the number imported.