Automated Ooma Extension Directory Reconciliation
Every Monday, WebRun opens Ooma Office, compares the extension directory against your current active employee list, saves any discrepancy such as an extension for someone who left or a new hire without one to a Google Drive sheet, and alerts the admin in Slack.
How do I reconcile my Ooma extensions against my team?
WebRun compares your Ooma extension directory against your active employee list every Monday, saves any mismatch to a Google Drive sheet, and alerts the admin in Slack, so an extension left active after someone leaves, or a new hire missing one, gets caught within the week instead of sitting unnoticed.
- Extension drift is caught every week instead of at audit time
- Departed employees are flagged if their extension is still live
- New hires missing an extension are surfaced the same week
Built for office managers · IT admins · small business owners · HR teams
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
office.ooma.comin a real browser with your saved login - no setup, no API keys. -
1
Ooma - list current extensions
ooma.com
WebRun opens Ooma to list current extensions. - Open Ooma Office and list every active extension
- Note the name and department attached to each
- Flag extensions with no name or an unfamiliar one
Done when The current Ooma extension directory is fully listed.
-
2
Google Drive - save the discrepancies
drive.google.com
WebRun opens Google Drive to save the discrepancies. - Open the extension reconciliation sheet in Google Drive
- List extensions with no matching active employee
- List active employees with no extension assigned
Done when This week's extension discrepancies are saved to Drive.
-
3
Slack - alert the admin
slack.com
WebRun opens Slack to alert the admin. - Post the discrepancy list to the admin channel in Slack
- Name each mismatched extension and each missing one
- Keep the alert to one short message
Done when The admin has this week's discrepancy list in Slack.
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
Does WebRun add or remove extensions itself?
No. It only compares the Ooma directory against your active employee list and reports mismatches. Adding or removing an extension is done by your admin.
What counts as a mismatch?
An active extension with no matching current employee, or an active employee with no extension at all, both directions are checked every week.
Why does this matter beyond tidiness?
An extension left active for someone who has left is a real access risk, so catching it weekly closes that gap faster than an annual audit would.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.