Legal requests that route, staff, and become matters on their own.

She configures the whole request layer — practice areas, the request taxonomy, the fulfiller team with the right legal roles, the self-service intake form, and the routing that gets each request to the correct people. Everything is grounded in your live setup and staged in one reviewable package inside the legal workspace.

That's the product working as designed — Legal Service Delivery is deliberately walled off from platform admin and governed by dedicated legal roles. Phyllis never proposes handing someone admin to 'fix permissions'; she recommends the correct legal role instead, so confidential matters stay confidential.

No — those are live case records that people and workflows create day to day. Phyllis configures the intake, routing, and templates so a submitted request flows correctly and promotes cleanly into a matter; she doesn't hand-write the requests or matters themselves.

No. Phyllis discovers, proposes a plan, and waits — nothing is written to your instance until you approve. Every build lands in a reviewable package you can inspect or roll back.

Every finding is read from and cited to your live instance — your real practice areas, request types, and routing — never assumed from a template. Where there's no safe, supported way to configure something, she flags the gap in the plan instead of forcing a risky change against your legal data.