An instance that heals on your approval.
Phyllis runs hundreds of Instance Scan checks across performance, security, maintainability, UX and upgradeability — after every dev task or on demand — then writes each fix into a scoped update set, staged for your approval.
Built by ServiceNow architects — CMA-grade by default
Grounded in your instance
Approval-gated delivery
CMA-grade documentation
Self-heal on your approval
A quick scroll through what Phyllis can do
Full instance scan
Slow queries
Stage indexes
ACL gaps
Security sweep
Upgrade readiness
Dead code
Update set hygiene
ATF coverage
Self-heal loop
Scan after tasks
Health trend
Full instance scan
Slow queries
Stage indexes
ACL gaps
Security sweep
Upgrade readiness
Dead code
Update set hygiene
ATF coverage
Self-heal loop
Scan after tasks
Health trend

Questions?
We’re glad you asked.
Findings across performance, security, upgrade-readiness, user experience and maintainability — slow or un-indexed queries, ACL gaps, deprecated APIs that block upgrades, broken UI policies, dead code — read from your live instance, each tied to the record it came from.
No. She stages the fix. For an approved finding she writes the remediation into a scoped update set, re-scans to confirm it's resolved, and closes the finding — you sign off on every fix; nothing changes on its own.
After every dev task and on demand, so the instance is re-checked as work happens — drift and tech debt are caught as they appear, not discovered the weekend before an upgrade.
Each finding is grounded in the actual artefact — the script, ACL or update set — with the reasoning and a remediation. You can dismiss what doesn't apply, and dismissed items are tracked, so the scan becomes your living risk register.
Yes. Upgrade-readiness is one of the scan's lenses — deprecated calls, skipped customisations and oversized update sets are surfaced ahead of time, so you walk into the upgrade knowing what will break.































