Verifying an Unsolicited Message Before Sending Documents
Match unexpected recruiting contact to your Lumen application and independently verify document requests before sending identity or financial information.
Updated October 26, 2026
Security Clearance
If you applied online and were contacted by a Lumen recruiter unexpectedly, match the message to your application receipt and verify the contact through Lumen’s published support route before sending identity or financial documents. Lumen’s own FAQ directs candidates with suspicious recruiting contact to its Contact Us page.
Key takeaways
- Match the application: Compare the role, requisition identifier, and submission record with what the sender claims.
- Keep links untrusted: Inspect the displayed destination without signing in, opening attachments, or submitting information.
- Confirm independently: Obtain support details from the company’s published careers pages rather than the unexpected message.
- Verify each request: Establish the hiring stage, purpose, recipient, and approved upload channel before releasing documents.
What should you check after applying online and hearing from a Lumen recruiter?
Start with the application you submitted, not the documents the sender wants. Locate your original confirmation, compare the advertised role with the message, and check your candidate account through the route you already know. Record mismatches as questions; neither a familiar title nor an unexpected approach settles authenticity.
Keep the message intact while you check. Note the sender address, claimed role, requisition identifier, requested action, and any stated deadline. You are building a record of the approach so support can evaluate it, not trying to satisfy the request by providing more information.
Compare the employer name, position title, location, and job identifier with your receipt. If the sender refers to another opening, ask for its public listing and the connection to your earlier application. Treat that explanation as something to verify through the employer, rather than proof supplied by the person being checked.
A real application does not automatically authenticate later correspondence. You still need to connect this sender, this request, and this destination to the actual hiring process. Likewise, an unfamiliar role is a reason to clarify the contact; it does not establish that every unsolicited recruiter message is fraudulent.
The Lumen recruiter interview provides background on candidate fit and recruiting. Use it for context, while directing verification of your specific message to the company’s current published support route. An older interview cannot confirm the identity of someone contacting you now.
How can you inspect links without handing over information?
Read the complete sender address and inspect the link destination using your mail application’s preview tools, without visiting the destination or submitting anything. If the destination is unclear, shortened, or inconsistent with the request, leave it alone and ask the independently located support contact to confirm the correct route.
On a desktop, a link preview or copy-link function may let you examine the address in plain text. On a phone, use the application’s supported preview behavior only if you know how it works. There is no need to experiment with an unfamiliar gesture that could open the page.
Look at the whole address. A company name in the visible link label or elsewhere in the address does not tell you who is collecting the information. Avoid trying to resolve uncertainty by entering a password, uploading a harmless-looking sample document, or downloading the proposed form.
Keep link inspection in perspective. You are looking for questions to resolve, not issuing a technical certificate of authenticity. A polished page, familiar logo, or professional signature should not replace the separate check with the company.
If you cannot comfortably interpret the address, skip that step. Go directly to the company’s known careers site and locate its support information. That is a practical decision, not a failure to complete a technical investigation.
How do you use Lumen’s published support route?
Find the support route independently and ask whether the contact and requested documents belong to the hiring process for your application. Provide enough context to identify the message, while withholding the identity or financial documents that prompted the concern. Ask support how it wants suspicious-message evidence supplied.
Lumen’s recruiting FAQ tells candidates who believe an outside party contacted them about a Lumen position to use Contact Us with details about who approached them and what was requested. Follow that specific recruiting route rather than guessing at an employee’s address or using a customer-service number supplied by the sender.
The published careers Contact Us page lists [email protected] for the United States and Canada, alongside regional support contacts. Read the page when you need it so you can use the currently published route for your region. A matching address in someone else’s signature is not the same as independently obtaining it.
Send a short verification request along these lines:
I submitted an application for [role and requisition] through your careers site. I received an unexpected message from [sender address] requesting [document types] through [claimed service or destination]. Before providing documents, could you confirm whether this contact is authorized for my application, what stage the request relates to, and the approved way to continue? I have retained the original message and can supply it using your preferred method.
Leave the requested document contents out of that inquiry. Describing a request for a driver’s license or banking information is enough to raise the issue; attaching the license or bank details would create the exposure you are trying to avoid. If support needs the original message, ask how to transmit it and check for unrelated personal information before doing so.
Which hiring stage should require the documents?
Ask the verified employer contact to explain each document’s purpose, the current stage, who collects it, and the approved submission channel. An assertion that something is needed “for verification” is incomplete. Confirm the request itself, rather than relying on the fact that employers sometimes collect sensitive information during hiring.
The FTC’s warning about fake recruiters describes requests for driver’s-license, Social Security, or bank-account information before an interview. It also describes pressure to provide financial details before the supposed recruiter answers questions about the job. That pattern is a reason to stop and verify.
Lumen’s FAQ describes possible pre-employment checks, including a Social Security trace. That published list does not authenticate an email asking for your Social Security number, establish that every candidate receives the same checks, or identify the correct document-collection channel for your case. Ask the verified hiring contact to connect the request to your actual stage.
| Request or signal | What it establishes | What to verify |
|---|---|---|
| Correct job title | The message names a familiar opening | Sender’s authority and application connection |
| Resume request | Someone wants your career information | Recipient, purpose, and permitted contents |
| Identity-document request | Sensitive information is being sought | Hiring stage and official collection method |
| Outside screening-service link | A separate destination is proposed | Whether the employer confirms that service and link |
| Urgent deadline | The sender wants prompt action | Whether the verified employer confirms the timing |
Clarify whether the request concerns an entire document or particular information within it. A verified contact should be able to tell you what to submit, how to correct a mismatch, and where to direct questions. If the instructions are unclear, ask before modifying or uploading the file.
For example, suppose the sender asks for identification to fix a name discrepancy. Your independent inquiry can describe the discrepancy without including the identification itself. Ask support to confirm the correction process and the intended recipient, then follow those confirmed instructions. Keep the support response with your application record rather than relying on your memory of a call.
For a cleared job search, keep the distinction between a career summary and supporting security documentation. The advice on describing a clearance on your resume can help you prepare a suitable career document. It does not make an unsolicited request for investigation records or identity documents legitimate.
When can you resume the hiring process?
Continue once the independently reached employer contact confirms the application connection, the request, and the submission route. Use the route that contact confirms, and provide only the requested material. If the response leaves the destination or purpose unresolved, keep the document request pending.
Record who confirmed what. “Support confirmed the recruiter” is different from “support confirmed this upload link and document request.” Preserve the answer alongside the original receipt so a later request can be checked against the same trail.
You can remain responsive without releasing documents immediately. A brief acknowledgment through an already verified conversation can state that you are confirming the document channel. The broader advice on responding to recruiter emails and calls helps maintain a professional exchange while you resolve the specific uncertainty.
If the company cannot confirm the approach, follow its instructions for reporting the message and stop using the proposed destination. Keep factual notes about the response. Do not label an unrelated real employee a scammer based solely on the name used in an unverified message.
Frequently Asked Questions
Does an application confirmation make the later message legitimate?
No. It documents your submission, while the later sender and document request still need verification. Compare the role and requisition, then contact the employer independently to connect the message to your application.
Should I send a redacted identity document first?
Keep the document request pending until the recipient, purpose, and submission route are confirmed. Redaction is not a substitute for authenticating the request. Ask the verified contact what material is needed and whether a reduced version is acceptable.
Does an external screening service prove it is a scam?
The different destination alone does not settle legitimacy. Ask the independently verified employer contact whether it uses that service for your application and how to reach the correct submission page. Avoid relying on confirmation supplied only by the unexpected sender.
What if the sender says I will lose the opportunity?
Treat the deadline as another claim to verify through the published recruiting support route. Keep the message and its requested action together. Before releasing any documents, obtain independent confirmation of the recipient and the approved upload destination.