11 min read
You applied through Workday, got the auto-confirmation, and sent a polite note to the internal recruiter listed on the posting. Silence for a week. You're not rude. You're sending the same shape of message every candidate sends, and the recruiter can't tell you read the req. That's fixable in one edit pass tonight.
The bar for a reply is low and specific. Name the req ID from the confirmation email. Pull one proof line from your top Experience bullet, not your Skills rail. End with one ask they can answer without opening your calendar. Internal recruiters don't grade prose. They search their queue by req number and scan for fit signals they can verify in Greenhouse.
Check your resume for free before you mention an application in email or a portal message. If Experience is empty in preview, even a warm note won't survive the next screen. Below: weak scripts judged against strong ones across roles, plus copy-paste US templates you can adapt after you apply.
These teardowns target corporate internal recruiters on US reqs in Workday, Greenhouse, Lever, and iCIMS. Swap the bracketed fields. You're not blasting the same text to twenty employers. One req, one proof line, one ask under 120 words.
Quick Wins
- Copy the req ID from your application confirmation before you write.
- Pull one proof line from your first Experience bullet, not your summary adjectives.
- Cap the body at 120 words; one ask only.
- Run Workday or Greenhouse preview on your resume before you hit send.
What weak internal recruiter messages share
Most templates online fail the same four tests. Internal recruiters on corporate reqs don't want a second cover letter. They want a searchable hook tied to the req they already own.
No req ID. "I'm interested in the software engineer role" could mean four open reqs in a 40-person eng org. The recruiter searches by number first. Without Req 88421 or Job Requisition ID from the portal, your note lands in a manual pile or gets ignored.
Flattery without evidence. "I admire your innovative culture" could go to any Fortune 500. It signals a mail merge. A line like "I applied to Marketing Coordinator II (Req 33107) and built weekly campaign reports in HubSpot during my internship" proves you did homework.
Skill dumps your resume can't back. Notes that name Python, Tableau, and SQL while your parsed Experience says "assisted with projects" create distrust when they open Workday. One keyword from your top bullet beats five you can't defend.
Multiple asks in one email. "Can you review my resume, refer me, and schedule a call?" forces the recruiter to triage three favors. Pick one: timeline, parse check, or whether external apps are still open.
Edge case: the posting lists a generic careers inbox instead of a named recruiter. Use the req ID in the subject line and address "Talent Acquisition team." Still keep the body under 120 words with one proof line.
Edge case: you applied through a referral link and already have an employee advocate. Message the internal recruiter only to confirm your file parsed. Don't ask the advocate and the recruiter for the same favor on the same day.
A composite mid-level analyst kept sending "following up on my application" with no req number. Three employers, zero replies. She rewrote one note naming Req 44218 and one bullet on variance models. Same resume underneath. One inbox reply asking for availability the same week.
Read how to follow up after sending your resume when you need email timing after the portal submit. This page focuses on what to say to the internal recruiter once you're in the queue.
How to message internal recruiters (US templates): role teardowns
Each pair shows a weak version candidates still send, then a version with req ID, one proof line, and one ask. Customize brackets. Keep the body under 120 words.
Software engineer after a Workday submit
Send within 48 hours of confirmation. Name the exact title and req ID. You're not asking them to bypass the process.
Before: "Hi, I'm a passionate developer who loves your company. Please review my resume for any engineering role. I'd be a great fit for your team!"
After: "Hi [Name], I applied to Software Engineer II (Req 88421) via Workday yesterday. My current role shipped three REST endpoints in Java that cut API latency on checkout flows. Is external screening still active for this req? Thanks, [Your name]."
Subject: Req 88421 · Software Engineer II · [Your name]
Hi [Name], applied to Software Engineer II (Req 88421) this morning. Top bullet: built [service/feature] in [language] at [employer]. Quick sense of timeline for external apps? Thanks, [Your name].
Marketing coordinator on a Greenhouse req
Marketing reqs flood inboxes. Your proof line should mirror a posting activity: campaigns, CRM, content calendars, not "creative thinker."
Before: "Hello, I'm very interested in marketing at your firm. I'm a fast learner with great communication skills. Can we connect?"
After: "Hi [Name], I applied to Marketing Coordinator II (Req 33107) today. My internship built weekly email reports in HubSpot for 12 campaigns. Did my resume import cleanly on your side? Thanks, [Your name]."
Subject: Req 33107 · Marketing Coordinator II · parse check
Hi [Name], submitted Req 33107 via Greenhouse. Experience bullet covers HubSpot reporting from [internship]. Any flag on my file parsing blank? Appreciate it, [Your name].
Operations analyst with a logistics posting
Ops recruiters filter on tools and scale language from the req. Pull a number from your bullet if you have one. Illustrative counts inside examples show shape, not market claims.
Before: "I'm hardworking and detail-oriented. I'd love any operations role at your company. Please keep me in mind for openings."
After: "Hi [Name], I applied to Operations Analyst (Req 55290) yesterday. I tracked inbound SLA for 400+ SKUs in my last role using Excel and WMS dashboards. Is this req still screening external candidates? Thanks, [Your name]."
Hi [Name], Req 55290 · Operations Analyst. Applied via [portal]. Proof line: managed [metric] across [scope] in [tool]. Still accepting external apps? [Your name].
Registered nurse on a hospital system req
Clinical internal recruiters scan license, unit, and shift fit first. Name the unit from the posting and one patient-population line from your resume.
Before: "I'm a dedicated nurse looking for new opportunities. I have great bedside manner and teamwork skills. Any openings?"
After: "Hi [Name], I applied to RN Med-Surg Nights (Req 11804) via iCIMS today. My current unit precepted four orientees on a 32-bed med-surg floor. Is external hiring still open for nights? Thanks, [Your name]."
Subject: Req 11804 · RN Med-Surg Nights · [Your name]
Hi [Name], applied to Req 11804. Top bullet: [unit type] · [patient population] · [cert if req asks]. Timeline for external RN apps on nights? Thanks.
Customer success associate on a SaaS req
CS internal recruiters want renewal, ticket, or onboarding proof. Tie one metric-shaped bullet to the posting's customer segment.
Before: "I'm excited about SaaS and customer success. I'd love to join your amazing team. Can you refer me?"
After: "Hi [Name], I applied to Customer Success Associate (Req 6673) this morning. I managed 45 SMB accounts in Zendesk with 96% CSAT in my last role. Any quick sense of screening timeline? Thanks, [Your name]."
Hi [Name], Req 6673 · Customer Success Associate. Applied [date]. Bullet: [accounts/tickets] in [tool] with [outcome]. External screening still active? [Your name].
Financial analyst on a rotational program req
Rotational reqs often share one posting across cities. Name the track you applied to, not "any analyst seat."
Before: "I'm a finance graduate seeking analyst roles. I have strong Excel skills and leadership experience. Please review my application."
After: "Hi [Name], I applied to Financial Analyst Rotational Program Dallas track (Req 9012) today. My internship built monthly variance packs in Excel for three business units. Did my file populate in Workday on your end? Thanks, [Your name]."
If they say the file was blank, fix layout before the next apply. Read resume rejected by ATS for the parse checklist that pairs with this follow-up.
Copy-paste internal recruiter message templates
Template A · After apply (under 120 words):
Subject: Req [ID] · [Job Title] · [Your name]
Hi [Name], I applied to [Job Title] (Req [ID]) via [Workday/Greenhouse/iCIMS] on [date]. One line from my resume: [proof bullet shortened]. [Single ask: timeline / parse check / external apps open?] Thanks, [Your name].
Template B · One-week follow-up (shorter):
Subject: Following up · Req [ID] · [Your name]
Hi [Name], quick follow-up on Req [ID]. Still interested. [Repeat proof line in one sentence.] Any update on screening for external candidates? Thanks, [Your name].
Template C · Rejection reply (diagnostic, not argumentative):
Hi [Name], thanks for the update on [Job Title]. I'm tightening my file for similar reqs. Did my resume parse correctly on your side, or had the req moved internal? Appreciate the clarity, [Your name].
Outreach tracker (one row per req):
Company · Req [ID] · [Title] · Portal · Applied [date]
Recruiter contact · Message sent [date] · Proof line used
Preview populated Y/N · Reply [Y/N] · Follow-up due [date+7]
Track ten reqs at a time, not fifty. Quality notes with a parse-ready resume beat a spreadsheet of ignored emails.
Patterns that kill replies before you get one
Mass-blasting the same script. Recruiters at the same employer compare notes. Identical wording gets flagged. Change the proof line every time.
Messaging before you apply. "Can you tell me about the role?" without a req ID wastes their time when the answer is on the careers page. Apply first unless you have a referral hook that names you.
Attaching a second resume in email. Workday already has your file. A conflicting PDF version creates version confusion. Mention you applied through the portal. Fix the upload if preview failed.
Asking to hop on a call in the first note. Calendars are expensive. Earn the call with a tight question first. Offer times only after they show interest.
Profile and resume mismatch. If your headline says "open to anything" but your resume targets one function, the recruiter stops. Align headline, top bullet, and the skill you name in the note.
Pasting your entire cover letter. When a posting wants a short letter, draft structure in the cover letter generator, then paste into the portal after your resume preview looks right. The recruiter email is not the cover letter field.
Sending three follow-ups. One bump after a week is fine. More reads as pressure. Silence means move to the next req.
Confusing internal with agency recruiters. Agency contacts need client name, location, and rate context. Internal contacts need req ID and parse proof. Swap templates and you'll look like you don't know who you're emailing.
Match your resume to the message you send
Run the free ATS checker with the job description pasted in. Your note might name HubSpot or med-surg precepting. If those terms aren't in your Experience bullets, the recruiter will notice the gap in Workday.
Score your job match on the reqs you're messaging about. Low scores with honest inputs mean retire the role from your outreach list, not send a fourth follow-up. High scores with a clean parse mean tailor once, apply, then send the internal recruiter note the same day.
What to send today
How to message internal recruiters with US templates comes down to three parts: req ID in the subject, one proof line from your top bullet, one ask under 120 words. Generic praise and early referral grabs get ignored because recruiters can't tell you read the posting.
Pick one open role where you already applied. Open your confirmation email. Copy the req ID. Pull one line from your first Experience bullet. Send Template A today. If you haven't applied yet, run preview on your resume, submit once, then message the same afternoon.
I've screened enough Workday queues to know the note gets you remembered only when the file behind it is readable. Fix parse quality first. Then outreach stops feeling like shouting into a void.
Read more
Frequently asked questions
After you apply through the official portal, when you can name the req title and ID from the confirmation email. Before apply only works with a real hook: their hiring post, a campus event, or a referral who told you to mention them. Cold notes that ask them to pull your file before you hit submit read like spam. Pair the message with a single-column resume that populates in Workday preview.
Under 120 words in the body. Open with the req ID, add one proof line pulled from your top Experience bullet, and end with one ask they can answer in a sentence. Attach nothing in the first note unless the portal or their auto-reply asks for it. Internal recruiters triage between screens. A cover letter pasted into email gets archived.
Internal recruiters own one employer's Workday or Greenhouse queue. They search by req ID and imported Experience fields. Agency recruiters juggle multiple clients and often need a sharp headline plus location and bill rate context. Internal notes should prove you applied on the right req. Agency notes should prove you match the client brief without asking them to guess your fit.
Send one follow-up after seven business days with a shorter version of the same ask. If silence continues, move on. Do not send three bumps. Silence usually means timing, volume, or a closed req, not a personal rejection. Fix your resume for the next posting and target a recruiter on a live req instead of chasing the same thread.
Mention one keyword that already appears in your Experience bullets, ideally in the first eight words of your top line. Do not list ten skills the recruiter will verify in Workday anyway. If your note says Python and your parsed profile shows only "team collaboration," trust drops before the phone screen. Mirror one posting term you can defend in an interview.