The right contact depends on what you need changed or explained. A myExperience login failure is an access question. An unexplained payroll entry concerns a pay record. A question about benefit-group rules concerns HR or benefits administration.
Northwell’s handbook lists AskHR through Microsoft Teams, myExperience, and Northwell Connect, with live HR representatives available through AskHR during business hours. It also publishes separate payroll and IT contact routes. Source: Northwell Employee Handbook, AskHR and Contacts.
Choosing the route does not require you to diagnose the technical cause. Describe the task and the last step that worked.
Begin with the outcome you need
Write one sentence explaining the result you are seeking. Examples include confirming a benefit group, correcting a particular time entry, clarifying a payment destination, or restoring access to the employee portal.
This keeps the request focused on the underlying issue. “I need help with myExperience” could mean several different things, while “I can sign in but need an explanation of a deduction on the statement dated [date]” identifies a useful starting point.
| Situation | Information to emphasize |
|---|---|
| You cannot authenticate | The point of failure and exact non-sensitive error |
| A page fails after sign-in | The affected function, time, browser, and visible result |
| A payroll figure appears wrong | Statement date, pay period, and specific entry |
| A benefits record is unclear | Employee group, election or event, and disputed detail |
| A payment instruction needs review | Date of the change and intended arrangement |
The table organizes requests. It does not override internal instructions or establish which team owns every unusual case.
Use the documented payroll route for a payroll inquiry
Northwell’s handbook lists:
myExperience → Help → HR Service Requests → Create Service Request → applicable payroll category.
Use the category that matches your actual question. Source: Northwell Employee Handbook, Contacts.
If you need to prepare the facts first, the pay-statement guide explains how to identify a disputed entry. The direct deposit guide separates payment setup from payment timing.
Do not open several differently worded requests merely because you are unsure which category applies. Ask for routing guidance and retain any reference number provided so follow-up information stays connected.
Handle an access barrier separately
You may need assistance precisely because you cannot reach an authenticated help function.
The handbook lists IT assistance through Northwell Connect → myTech or (516) 470-7272, and the Human Resources Service Center at (516) 734-7000. Use the contact appropriate to the question. Source: Northwell Employee Handbook, Contacts.
Explain when a blocked account prevents you from completing a time-sensitive HR task. That creates two questions: how to address access and how the responsible team wants the underlying task handled meanwhile.
Do not assume that reporting the access problem automatically extends a deadline. Ask explicitly how to document the situation.
Build a short, usable request
An effective request usually has five parts:
- Task: What you were trying to do.
- Observation: What appeared or failed.
- Timing: When it happened and which period or event is involved.
- Evidence: The relevant non-sensitive wording or record reference.
- Question: What you need confirmed or corrected.
An illustrative request might read:
I can enter myExperience, but I need clarification of the payment method saved on [date]. My intended arrangement is [brief description without full account details]. Please confirm whether the record is complete and which payroll payment will use it.
There is no need to include unrelated employment history or every troubleshooting attempt. Include the facts that could change the answer.
Protect private records during follow-up
Use the employer’s approved channel for documents requested by the responsible team. Keep passwords, verification codes, and recovery secrets out of support descriptions.
If support needs a screenshot, inspect it for information from other tabs or applications. A narrow image of the relevant error may communicate the issue more clearly than an entire desktop.
Keep a record of the case reference, the team handling it, and any action you were asked to take. A request being received is not the same as the underlying record being corrected.
After receiving a response, check the original task again. For benefits questions, use the benefits-confirmation guide to identify what still needs confirmation.
