The whole change, built in your instance.On every ServiceNow product — ITSM to HRSD, CSM to SPM. Catalog items, flows, rules and ACLs, built in one update set, with every write read back.
- Created catalog item New Laptop Request · sc_cat_item · read back
- Reused variable set Laptop Configuration · io_set_item · read back
- Created UI policy “Require accessory details when Other is selected” · catalog_ui_policy · read back
- Created client script “Recommend RAM for laptop model” · catalog_script_client · read back
Build complete — all 4 layers verified. Update set Phyllis - AdHoc - NewLaptopRequest - 2026 left in progress.
- Explored 2 sources · Ran for 33s
Short answer: the P2 “breaches” mostly come from duplicated SLA definitions piling clocks onto a queue nobody owns, not from slow resolution on one clock.
Stacked SLA definitions. Several overlapping SLA sets attach to P2 incidents, so one late P2 shows up as many breaches.
No owner. Of the 36 active P2 incidents, 33 have no assignee.
Wrong SLAs attached. “IT Support P1/P3 — Resolution” clocks are attached to P2 incidents.
- Explored 43 sources, wrote 1 document · Ran for 3m 46s
The assessment is done and the full report is in the Artifacts panel. It scores the CMDB 57/100 (Poor, D).
Nothing on the instance was changed.
- Explored 11 sources · Ran for 3m 40s
A rebuilt, single canonical “Travel Request” catalog item and its full fulfilment lifecycle — order form, tiered approvals, Travel Desk booking and notifications.
33 stories across 7 epics, each with effort, points and acceptance criteria.
- Ran suite SPM — Regression Suite · TES0001108 · 1 minute
The suite ran on acmedev: 8 passed, 0 failed. Each test and its result is open beside the chat, with the run record.
- Previewed on acme-test · No conflicts · health checks clean
Previewed the update set on acme-test — no conflicts. Seven records are captured, all in the right scope.
Promote Phyllis - AdHoc - NewLaptopRequest - 2026 to acme-test? Approve
- Explored 23 sources · Read your team conventions
The Build Book lists the skills and team conventions I’m following, and every reference resolved on your instance before anything is built.
Built for every product on the platform
- Every ServiceNow product
- ITSM · HRSD · CSM
- SPM · IRM · ITOM
- Scoped update sets
- Every write read back
Guided, change by change
Phyllis shows the plan, then builds in a single update set — asking for approval on each change, or the rest of the build at once.
Every write, read back
After each write she compares what ServiceNow actually stored with what was sent, and names any field a policy dropped — then fixes it and checks again.
Your conventions, every chat
Team standards — scoping, naming, how approvals are done — applied in every conversation, with memory per person, instance and project.
Real records. Not snippets.Guided builds show you the plan first, then ask before each change. Approve one at a time, or the rest of the build.
“Build a catalog item for laptop requests with manager approval.”
Catalog“Create a flow that notifies the CAB when a high-risk change is submitted.”
Flow Designer“Add a business rule that sets priority from impact and urgency.”
Business rules“Lock Assigned to once an incident is resolved.”
ACLsNothing ships without your approval.
Signs in as you.
Per-user OAuth — she inherits your roles and ACLs, and every change is logged under your name.
ApprovalsApproval on every change.
Approval cards before changes are written — one at a time, or the whole approved build. Nothing reaches production from chat.
ApprovalsPer-instance controls.
Build, Read-only or Backlog only per instance. Table rules and switched-off tools are enforced on every request.
ApprovalsQuestions & Answers
What can Phyllis actually build?
The real records — catalog items, Flow Designer flows, business rules, client scripts, UI policies, ACLs, workspaces and AI Agents — wired together and delivered in one update set.
Will she follow our standards?
Yes. Your team’s conventions apply in every chat, and she remembers what matters per person, instance and project.
What if ServiceNow quietly drops a field?
She’ll tell you. Every write is read back and compared with what was sent, and any dropped field is named and fixed.
Can I choose the model?
Yes — teams choose which models are on, with Auto routing between them.
Get started with Develop.
See it on your own instance in thirty minutes.