Automated MetLife Benefits Enrollment Reconciliation
Every Monday, WebRun opens the MetLife group benefits portal, compares the enrolled employee list against your current roster in Google Sheets, flags any employee missing from enrollment or any enrollment with no matching active employee, and posts the summary to Notion for HR.
How do I make sure every employee is correctly enrolled in MetLife benefits?
WebRun compares your employee roster against who is actually enrolled in MetLife group benefits every Monday, flagging any active employee missing from enrollment and any enrollment with no matching employee. It posts the mismatch summary to Notion for HR, so a coverage gap surfaces the same week instead of at a claim.
- Enrollment gaps surface the same week instead of at a claim denial
- HR gets one weekly summary instead of comparing two systems by hand
- New hires missing enrollment are caught before it becomes a bigger issue
Built for HR teams · benefits administrators · payroll managers · small business owners
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.metlife.comin a real browser with your saved login - no setup, no API keys. -
1
MetLife - check enrolled employees
metlife.com
WebRun opens MetLife to check enrolled employees. - Open the group benefits portal
- List every employee currently enrolled in a plan
- Note the plan type and effective date for each
Done when The full enrolled employee list has been read.
-
2
Google Sheets - compare against the roster
google.com
WebRun opens Google Sheets to compare against the roster. - Compare the enrolled list against the current employee roster
- Flag any active employee missing from enrollment
- Flag any enrollment with no matching active employee
Done when Every employee and enrollment has been checked against the other.
-
3
Notion - post the mismatch summary
notion.so
WebRun opens Notion to post the mismatch summary. - Post the mismatch summary to the HR page
- List missing enrollments and orphaned enrollments separately
- Leave it for HR to follow up on each
Done when HR has this week's reconciliation summary in Notion.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it enroll or remove an employee from a plan?
No. WebRun only compares lists and reports mismatches. Enrolling, changing, or removing coverage stays HR's action on the MetLife portal.
What causes an employee to show as missing enrollment?
Usually a new hire whose enrollment hasn't been processed yet, or a plan change that didn't go through. Either way it surfaces the same week.
Does it see any health or claims information?
No. It only reads who is enrolled in which plan type and the effective date, never claims or health details.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.