HR services that ship before the next intake cycle.
Centers of Excellence, HR services and case rules, lifecycle events with their activity sets, document templates and security policies — Phyllis builds the HRSD estate in your instance, 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
Discover the estate
Design the taxonomy
Build an HR service
Automate a lifecycle event
Route with AWA
Secure a COE
Integrate HR data
Generate HR profiles
Draft the design doc
Scan & self-heal
Sign & acknowledge
Escalate & notify
Discover the estate
Design the taxonomy
Build an HR service
Automate a lifecycle event
Route with AWA
Secure a COE
Integrate HR data
Generate HR profiles
Draft the design doc
Scan & self-heal
Sign & acknowledge
Escalate & notify

Questions?
We’re glad you asked.
A working HR service, not settings — the Centers of Excellence, topic categories and HR services, the service activities and task types, case templates, and the lifecycle events and activity sets that drive employee journeys. It lands in one reviewable package.
Yes. She builds the lifecycle events and their activity sets — onboarding, leave, transfers — so a single trigger fans out into the right tasks across HR, IT and facilities, instead of a case that just sits in a queue.
She reads your live HRSD configuration first — existing COEs, services and templates — and extends it, so new services match the structure your HR team already runs.
She configures the services and access model; the employee records and conversations stay in your instance under your controls. She reads configuration and metadata to do her work, not employee case content.
Right. Every service, template and lifecycle event is staged in a scoped update set for review. Nothing reaches Employee Center until you approve it.































