Who can see HR cases, and why?
01 · Ask anything, any time.
What a flow does, why a rule fired, who can see what — answered from your records and cited. Ask mode is read-only on the server.
Run · BAU
Run the platform. Every day, without the backlog.
Keeping the lights on is most of the job. Phyllis answers the questions, works the backlog, fixes what breaks and scans after every change — so your team spends its time on the work only people can do.
14.2%
Why do P1 incidents keep getting reassigned?@ for records · / for commands
Ask
acmedevProject
acmedevProject Read the assignment rulessys_assignment_rule · 3 rulesRead
Read the reassignment historysys_audit · last 30 daysRead
Two rules match P1 on categoryCited to 14 recordsCause
Fix staged for your approvalMerge into one ruleProposed
Built for the platform
3,000+typed ServiceNow tools~230expert skill packsHundredsof health checks8acceleratorsISO 27001 certifiedPer-user OAuthApproval on every changeLands in your update setsATF on every build
How it works. Step by step.
Sprint 149
02 · Work the backlog.
Stories pulled from Jira or ServiceNow Agile 2.0, built in your instance and synced back — each in its own update set.
FixedRescan clean
03 · Scan after every change.
An Instance Scan with hundreds of checks runs after every task — findings cited, fixes staged for your approval.
Everything your team needs, day to day. Enterprise controls built in.
Ask Phyllis about your instance…
Ask your instance anything.
Answers grounded in your records — cited, and read-only by default.
sc_cat_item
item_option_new
sys_hub_flow
Every write, read back.
After each change she re-reads the record and checks it matches.
Owner
Admin
Member
+
Control who has access.
Owners, admins and members — and per-instance limits.
Connect your stack.
ServiceNow, plus Jira, Teams and Zoom through Phyllis Plugins.
Plan.docxStoriesDesignTests
PhyllisPriya · BASam · read-only
Plan together, privately.
Private projects with BA and read-only stakeholder modes.
One teammate for every role. Pick yours.
Whoever you are on the team, she takes the work you’d rather hand off.
Business Analyst
From a brief to sequenced stories.
Turn a one-sentence brief — or a workshop transcript — into sized user stories with acceptance criteria, grounded in the live instance, not a workshop guess.
She’ll take requests like- Turn yesterday’s HR workshop into stories.
- What already exists for onboarding?
- Size these stories and add acceptance criteria.
Onboarding case intakeHRSD-212 · 21 pts
HRSD-213Manager intake record producerReady3
HRSD-214Lifecycle event activity setsReady5
HRSD-215IT provisioning tasks via FlowPlanned5
HRSD-216Equipment request integrationPlanned3
HRSD-217ATF suite for intake → tasksDraft2
Developer
Builds real records, not snippets.
Business rules, client scripts, flows and ACLs in scoped update sets — every write read back and staged for your approval.
She’ll take requests like- Build the warranty claim flow with approval over $5k.
- Why does this business rule fire twice?
- What breaks if we rename u_business_unit?
sys_script · P1 network auto-assign+6 −0
1(function executeRule(current, previous) {
2 if (current.priority != '1') return;
3 var onCall = new OnCallResolver().forGroup('Network Ops');
4 if (!onCall) return;
5 current.assigned_to = onCall.user;
6 gs.eventQueue('network.p1.page', current, onCall.user);
7})(current, previous);
Update setFeature: P1 network auto-assign
ATF12 / 12 passed
Architect
Built to your standards, every time.
Correct scoping, naming and ACL coverage across the whole estate — every decision cited to the record it came from.
She’ll take requests like- Review this custom app against our conventions.
- Where are we duplicating flows?
- Is our CMDB CSDM-aligned?
Review gate · x_acme_assetPassed
Scoped to x_acme_assetnothing left in GlobalPass
Naming conventionu_ prefix · readable labelsPass
No hard-coded sys_ids3 references resolved by namePass
ACL coverageread / write / create on every tablePass
Platform Owner
Healthy, safe and upgrade-ready.
An Instance Scan with hundreds of checks after every task, self-healing on approval — and controls that hold on production.
She’ll take requests like- Run a health scan on acme-prod and fix what you can.
- Are we ready for the Australia upgrade?
- Show me what Phyllis delivered this quarter.
Instance Scan · acme-testPassed
Hundreds of checks · 0 critical1 high finding fixed with approvalClean
Delivery Lead
The whole plan, end to end.
The implementation sequenced and synced to Jira or ServiceNow Agile 2.0, released to test on approval — so the team always knows what ships next.
She’ll take requests like- Build me the ITSM Pro backlog.
- What’s ready to move to UAT this week?
- Sequence these update sets for release.
Batch · Asset return rollout3 update sets
1 · Asset return — data modelu_asset_return · 6 recordsReady
2 · Asset return — fulfilment flowdepends on 1 · 5 recordsReady
3 · Asset return — portaldepends on 2 · 3 recordsReady
devtestprod
QA Engineer
Proven before it promotes.
ATF written and run for what changed, screenshots checked against the build — nothing moves until it’s green.
She’ll take requests like- Write ATF tests for the warranty claim flow.
- Run the impacted suites before release.
- Order the laptop refresh item end to end.
ATF · warranty_claim4 tests
Claim under $5k auto-approves4 stepsPass
Claim over $5k routes to approval6 stepsPass
Missing serial blocks submit3 stepsPass
Rejected claim notifies the customer5 stepsPass
Configuration Manager
Keeps the CMDB honest.
Class audits, orphaned CIs, stale references — Phyllis reads the live CMDB, cites every finding, and stages the cleanup for your approval.
She’ll take requests like- How healthy is our CMDB before ITOM?
- Find duplicate servers across discovery sources.
- Stage the cleanup as stories.
CMDB health scorecardcmdb_ci · 48,213
68of 100
CriticalDuplicate servers across SCCM and Discovery2,114 CIsFix with Phyllis
Where teams start.
IH-118: Instance Health Remediation6 records
Index on the queried incident columnIndexCreate
Reworked incident business ruleBusiness RuleCreate
Field-level read ACLsACLCreate
Async GlideAjax rewriteClient ScriptCreate
Ready to deploy?6 records — 6 to create
Approve & DeployRejectEsc to go back
Health
Instance health & self-heal
Hundreds of checks across every category — and unlike the native engine, Phyllis self-heals findings on your approval.
Read the use caseCHG-301: Governed Normal Change Model6 records
Normal Change model + statesChange ModelCreate
State transitions + rejection revertTransitionsCreate
Change Risk Assessment + thresholdsRisk AssessmentCreate
Production + business-hours risk conditionsRisk ConditionCreate
Ready to deploy?6 records — 6 to create
Approve & DeployRejectEsc to go back
ITSM
Implement ITSM
From “implement ITSM” to a sequenced backlog to staged update sets — incident, problem, change, catalog, SLAs.
Read the use caseAUT-118: Governed Request-to-Fulfilment Flow6 records
Request-to-fulfilment flow + triggerFlowCreate
Hardware/software branches + error handlerFlow LogicCreate
Fulfilment subflowSubflowCreate
Licence-assignment actionActionCreate
Ready to deploy?6 records — 6 to create
Approve & DeployRejectEsc to go back
Automation
Flows & automation
Flow Designer flows, business rules, AI agents, notifications — automation built, tested, and approval-gated.
Read the use caseQuestions, answered.
Will Phyllis change production?
Only as far as you allow. Production instances start as Agile management only — she can maintain your story backlog there and nothing else — and every change needs your approval.
Does she replace our platform team?
No. She takes the repeatable work — questions, small enhancements, fixes, scans — so your team can spend its time on design, stakeholders and the decisions only people can make.
How does she fit our sprint?
Stories come from Jira or ServiceNow Agile 2.0, and status, comments and changes sync back both ways.
Whatever you’re working on.
ImplementUpgradePhyllisAssess
HR onboarding workshop
Implement a product.
ITSM, HRSD, CSM and every product in between — planned, built, tested and ready to promote.
Explore Implement148
Upgrade.
Skipped records triaged, regression tested and released to test — on your approval.
Explore UpgradePhyllisAssessment · acme-prod · 29 Sep 2026
CMDB & CSDM health
62/100
Needs attentionMeasured: 14 checks · Not measured: 2 · Not licensed: Service Mapping
Now · 4Next · 7Govern · 3
| Finding ↓ | Records | Severity | Remediation |
|---|---|---|---|
| CIs without a servicecmdb_ci_server | 212 | Map to application services | |
| Duplicate server CIscmdb_ci_server | 87 | Reconcile on serial number | |
| Stale discovery sourcecmdb_ci | 1,340 | Retire or rediscover | |
| Class not in CSDM 5cmdb_ci_appl | 46 | Move to the business application | |
| Missing ownercmdb_ci_service | 19 | Assign a managed-by group |
cmdb_ci_server · no cmdb_rel_ci to a service · 212 rowsAssess and clean up.
CMDB, tech debt, performance, licences and AI readiness — each ends in a report you can hand over.
Explore Assess
