“Which conventions are in force here?”
GovernBest Practice Studio
Your standards. Built in.
Write down how your team builds once. Phyllis follows it in every chat, cites the rule she followed, and stays inside the controls you set for each instance.
ISO 27001 certified
Per-user OAuth
No training on your data
Approval-gated changes
Lands in your update sets
5,000+ ServiceNow tools
230+ product skills
Hundreds of health checks
Jira & Agile 2.0 two-way sync
Context graph on every build
ATF where it applies
Every write read back
Tables and tools per instance
CMA-grade builds
01Standards, applied
She follows your rules. And says which.
The conventions in force for this chat are listed, and every build cites the one it applied — so a reviewer sees why, not just what.
Laptop warrantyacmedev606 credits
- Checked the conventions in force: acme · acme-dev — 14 on, 2 switched off here
- Named it u_warranty_expiry: Following your naming convention — u_ prefix, readable label
- Flag in a script include, not a global business rule: Following Phyllis library: script includes first
- Built in Feature: Laptop warranty: 2 of 2 read back
@ for records · / for commands
Phyllis is AI and can make mistakes. Please double-check responses.
02In your own words
Governance, in your own words.
Set the rules once in Best Practice Studio. Then ask her what’s in force, and why she built it the way she did.
“Why did you name it u_warranty_expiry?”
Cited
“Build the approval the way our standards say.”
Applied
“Can you write to acme-prod?”
Instance access
“Is sys_security_acl blocked here?”
Blocked tables
“Which accelerators has our team switched on?”
Studio
03How governance works
Standards she follows. Controls she can’t cross.
Best Practice Studio.
Every convention, accelerator and prompt book your team uses, in one place — Phyllis’s library, your edited versions and your own. Switch each one on per instance — or per customer, for partners.
Start from the standards you already have.
Upload your development standards. Phyllis routes each passage to the right domain and drafts conventions cited to the passages they came from — nothing applies until an admin accepts it. Available on selected plans.
A library that never changes under you.
Library items stay linked to Phyllis’s best practice. Edit one and your version stays in force; when the library moves on, you see the difference and choose — it is never applied silently.
Controls held at the connection.
Build, read-only or backlog-only per instance, blocked tables and switched-off tools — enforced on every request, whichever chat or workflow makes the call.
An audit trail for every move.
Every tool call, access change and setting change recorded under the person who made it — exportable to CSV.
04How it works
From your standards to every build.
Set the standard
Best Practice StudioStart from Phyllis’s library or your own standards document, then edit what you need.
Scope it
Per customer · per instanceSwitch each convention on where it applies — and off where it doesn’t.
Build with it
Cited in every chatPhyllis follows the conventions in force, cites the one she applied, and stays inside your instance controls.
05Safe on your instance
Nothing ships without your approval.
Controls that hold at the connection itself — whichever tool, chat or workflow makes the call.
Signs in as you
Per-user OAuth — she inherits your roles and ACLs, and every change is logged under your name.
Approval-gated changes
Approval cards before changes are written — one at a time, or the whole approved build. Nothing reaches production from chat.
Per-instance controls
Build, Read-only or Backlog-only instances. Blocked tables and switched-off tools are enforced on every request.
Audit log
Every approval, write and access change recorded — exportable to CSV.
06Questions
Govern, answered.
Still curious? Talk to the team — or book a demo and ask Phyllis in your own instance.
01What is Best Practice Studio?
One place for the conventions, accelerators and prompt books your team uses — Phyllis’s library, your edited versions and your own — each switched on per customer or instance.
02Can I import our existing standards?
Yes. Upload the document and Phyllis drafts conventions from it, each line cited to the passage it came from. An admin reviews and accepts them before they apply.
03What happens when Phyllis updates the library?
Items you use as-is pick up the new text. Items you edited keep your version — the change is shown to you, never applied silently.
04How do I know which rules she followed?
Every chat shows the conventions in force, and Phyllis cites the convention she applied in her answer.
07The whole lifecycle
One teammate. The rest of the lifecycle.
Analyze
Ask ServiceNow anything — your instance, the docs, best practice.
See AnalyzePlan
A sentence, a workshop or a meeting — to a sprint-ready backlog.
See PlanDevelop
The whole change, built in your instance — every write read back.
See DevelopTest
Orders, flows, AI Agents and ATF — run for real, in your instance.
See TestDeploy
Batch and promote update sets — just ask.
See DeployAdopt
Capability maps, adoption roadmaps and user guides — get value from what you own.
See Adopt08Get started
Ready to 10× the team you already have?
Your instances, your backlog and your meetings on one side; the Phyllis Knowledge Graph on the other. Phyllis does the work in between.