One graph behind every build.
Your standards on the inner ring. ServiceNow’s best practice on the outer ring.
NEWBuilding AI Agents with Phyllis
The AI teammate for ServiceNow
An AI-native ServiceNow teammate that doesn’t just advise — she analyzes, plans, develops, tests, and deploys.
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
Whatever you’re working on in ServiceNow. She does the work.
Run the platform, implement a product, upgrade, or assess and clean up — Phyllis does the work in your instance, grounded and safe.
Run · BAUYouPhyllisImplementUpgradePhyllisAssess
FixedRescan clean
Run the platform.
The everyday work — backlog, fixes, questions and health — done in your instance and scanned after every change.
Explore RunHR 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 AssessOne 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
One teammate for the whole lifecycle. Analyze, plan, develop, deploy, test.
From a sentence to a promoted, tested change — every step staged for your approval.
CMDB health scorecardcmdb_ci · 48,213
68of 100
CriticalDuplicate servers across SCCM and Discovery2,114 CIsFix with Phyllis
Analyze
Ask your instance anything
Phyllis grounds herself in the full context of your ServiceNow instance — its tables, ACLs, flows, update sets, configurations, and dependencies. Every answer is evidence-backed and traceable to the records it came from.
Explore AnalyzeImplement ITSM · 24 storiesITSM-101
ITSM-102Incident categories & assignment rulesDone5
ITSM-103Major incident workflowReady8
ITSM-104Change CAB approvals by riskReady5
ITSM-105Problem → known error handoffPlanned3
ITSM-106SLA definitions for P1–P4Draft3
Plan
From a sentence to a sprint-ready backlog
Say “I want to implement ITSM” and Phyllis returns sequenced stories with priorities, points, and acceptance criteria — synced both ways with Jira or ServiceNow Agile 2.0.
Explore Plansys_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
Develop
The whole change, built in your instance
Phyllis develops on the platform — from tables, business rules, flows, and ACLs to the records behind them — then verifies and tests every change.
Explore DevelopPromote · Feature: Warranty claim flowAwaiting approval
devtestprod
Records14
ATF12 / 12 passed
Instance ScanClean
Rollback planAttached
Promote to prod?Platform owner
Approve & promoteReject
Deploy
Sequence and promote from one canvas
Batch and release update sets through chat — in the right order, with conflicts surfaced before you promote.
Explore DeployATF run · Warranty claim flowPassed
12 / 1241s
Claim under $5k auto-approves4 stepsPass
Claim over $5k routes to approval6 stepsPass
Instance Scan after buildHundreds of checks · 0 criticalClean
Test
Prove every change before it ships
ATF suites and screenshot validation, plus an Instance Scan with hundreds of checks across six categories — nothing promotes until it’s green.
Explore TestYour standards. ServiceNow’s best practice. One graph behind every build.
Before Phyllis builds anything, she queries the Phyllis Knowledge Graph — your live instance, your team’s conventions, what worked last time, your backlog and meetings through Phyllis Plugins, hundreds of expert ServiceNow skill packs and checks, the official docs for your release and a curated learning corpus. So she reuses what exists, follows the standard, and leaves less tech debt behind.
Live query01 / 03
Add a laptop refresh request with manager approval.
Sources6 of 6
01
Your backlog & meetingsITSM-142 · agreed in the Teams workshop
02
Your live instanceHardware category and variable set
03
Your conventionsu_ prefix, scoped to x_acme_itsm
04
Build memoryManager approval flow · HR-214
05
Expert skill packsCatalog item + approval pattern
06
Official docsCatalog variables, for your release
What shipsUpdate set · laptop_refresh1 created · 2 reused · scan clean
Add a laptop refresh request with manager approval.
Ask in your own words.
One sentence — no template, no ticket form.
Your live instanceYour conventionsJira · ITSM-142Service Catalog skill packDocs · your releaseFive sources, one answer.
Your instance, your standards, the right skill pack and the docs for your release.
Laptop refreshCatalog item · your conventionsCreated
Hardware variable setNo duplicateReused
Manager approval flowFrom your last buildReused
Reused, not rebuilt.
Existing records reused and scan-clean before review.
Reuses what existsNo duplicate flows or tables
Built to standardYour conventions, CMA-grade
Less tech debtScan-clean before review
Upgrade-safeChecked against your release
Know what breaks before you change it.
Before Phyllis changes a field, a table or a script include, she maps everything that depends on it — including the references that only exist as names inside scripts and conditions.
Proposed change
Rename incident.u_business_unit
16dependents found
Every dependent, found first.
Half of them only exist as names inside scripts and conditions.
ACL · incident.writeScript
var unit = gs.getUser().getRecord().getValue('department'); answer = current.u_business_unit == unit;
Fails quietly, at runtime.
A typed reference fails the moment a form opens. A name in a script fails later — so she finds both.
08Visible to ServiceNow’s Reference Usage
3
UI policyTyped reference
2
Flow inputTyped reference
2
Form layoutTyped reference
1
NotificationIts template is customised too — revert together
08Only visible inside script and condition text
4
Business ruleBreaks at runtime, not at save
High2
ACL scriptFails silently — people get locked out
High1
Scripted RESTYour integration’s contract
High1
SLA conditionStops matching, no error
MediumEnterprise controls, enforced. Not just hidden from view.
Controls that hold at the connection itself — whichever tool, chat or workflow makes the call.
rm_storyrm_epicrm_scrum_tasksys_scriptsys_hub_flowsys_security_aclsys_propertiessys_ui_policysc_cat_itemProduction-safe by default.
Connect production for the backlog alone. Agile management only is enforced on every request Phyllis makes — not just hidden from view — and new production instances start there.
Read back 3 of 3 writes
Approved by you
Plan: create Laptop refresh
acme-prod set to Agile only
ApprovedApproved, read back, logged.
Nothing is written without your approval. Every write is read back and checked, and every approval and access change lands in the audit log.
Sonnet 5Default
Opus 5.5Long builds
Background scriptsacme-test
sys_user_has_roleBlocked
You set the rules.
Choose which models are on, block tables and switch off tools per instance, and watch credits move live while Phyllis works.
RCPSSM
acme-devacme-testacme-prod
AdminMemberPer-user access, per instance.
Every person connects with their own OAuth token, so Phyllis can only do what they can — and owners decide who sees which instance.
Phyllis is ISO/IEC 27001 certified — the international standard for information security management. Independently audited controls across access, data handling and operations, so your security team has a recognised baseline to sign off against.
Zero data retention by default, on every tenant
OAuth-scoped access — your roles and ACLs, honoured
Independently audited to ISO/IEC 27001:2022
Information security
ISO 27001 certified
CertifiedStandardISO/IEC 27001:2022
ControlsAccess, data handling, operations
AuditIndependent, external
Data retentionZero by default
AccessPer-user OAuth 2.0
SOC 2 Type IIIn progress
Plug Phyllis into how your team already works. Your backlog. Your meetings.
Phyllis Plugins connect her to the tools around your instance — your backlog, your meetings — so the work starts where the conversation happened.
Jira · ITSM boardSyncedLaptop refresh requestITSM-142 · 5 pts · Sprint 14Created
Manager approval for hardwareITSM-143 · 3 pts · acceptance criteriaCreated
P1 auto-reassignmentITSM-138 · status → In reviewUpdated
Assignment group rulesITSM-131 · comment from PhyllisComment
JiraWork trackingYour backlog, kept in step.
Stories, points and acceptance criteria land on your Jira board — and status, comments and changes sync back.
Azure Boards · PlatformPreviewKnowledge base migrationUser Story 4812 · Iteration 9New
Retire legacy KB templatesTask 4815 · linked to 4812New
CMDB health remediationUser Story 4790 · Iteration 8Active
Upgrade readiness reviewFeature 4701 · 3 child storiesBacklog
Azure DevOpsWork trackingComing soonWork items from Azure Boards.
The same backlog sync for teams planning in Azure Boards — user stories, tasks and iterations.
Teams · HR onboarding workshopTranscript“New starters need a laptop before day one.”HR lead · 12:04
“Managers should approve anything over $2k.”Finance · 18:37
Pre-boarding hardware requestStory · 3 acceptance criteriaDrafted
Manager approval thresholdStory · linked to 18:37 in the callDrafted
Microsoft TeamsMeetingsOn requestThe workshop becomes the backlog.
Bring in a Teams meeting transcript and Phyllis drafts the stories — each one traced back to the moment it was said.
Zoom · Customer service discoveryRecordingCase routing by product lineRequirement · raised at 06:12Captured
Escalate VIP accounts to tier 2Requirement · raised at 21:45Captured
Customer portal case statusRequirement · raised at 33:10Captured
Stories ready for review3 stories · sent to your backlogReady
ZoomMeetingsOn requestRecordings become requirements.
Connect Zoom and Phyllis reads the recording’s transcript, pulls out the requirements and turns them into stories for your review.
Built for ServiceNow, end to end. Not a generic model with a connector.
Book a demo3,000+typed ServiceNow tools
~230expert ServiceNow skill packs
Hundredsof health checks after every build
Questions? We’re glad you asked.
Can Phyllis change my instance without my approval?
No. Every change is built in a scoped update set and staged for review with the design doc, scan, and test results attached.
Promotion requires an explicit approval — there is no path where a change ships unattended.
What does “CMA-grade” actually cover?
The discipline of a Certified Master Architect, applied to every build: correct scoping and naming, scan-clean code, proper ACL coverage, and ATF where it applies — with a signed design document alongside each change, every claim cited to the record.
Does Phyllis replace Jira or ServiceNow Agile 2.0?
No — she sits alongside. Stories mirror into Jira or ServiceNow Agile 2.0 with two-way sync.
Adoption doesn’t depend on ripping out your existing stack.
Which ServiceNow products does Phyllis cover?
All of them — ITSM, CSM, HRSD, ITOM, ITAM, SecOps, IRM, SPM, App Engine, Now Assist and the rest of the platform.
Every product has its own use case describing what she analyzes, plans, builds and maintains there — [browse the use cases](https://phyllis.app/#use-cases) for the full list.
What access does Phyllis need in my instance?
She signs in as you. Per-user OAuth means she can only see and touch what your roles and ACLs already allow — nothing more.
No plugins to install, no shared super-admin account — she works entirely under your existing security model.
Where does my data go?
Nowhere. Zero data retention is the default on every tenant.
Nothing is kept to train a model, and findings live inside your instance.
The audit trail is written per operator, per action.
The full posture — encryption, authentication, sub-processors — lives on the [security page](https://phyllis.app/security).
What can Phyllis actually build?
The real records — catalog items, Flow Designer flows, business rules, client scripts, UI policies, ACLs and AI Agents — wired together, scoped correctly, and delivered in connected update sets. The catalog item, the flow behind it, the approvals and the ACLs land as one build, not fragments — across every ServiceNow product.
