Card disputes that intake, credit, investigate, and resolve on the clock.

The full banking-servicing surface: the institutions, networks and servicing offers your customers raise, plus the case types, routing, guided playbooks, forms, agent workspace, resolution clocks and portals that turn a raised dispute or complaint into a worked, closed case. She discovers what's already live, then configures the gaps against your approved design.

No, and that's deliberate. Customer accounts and transactions are protected data that governs who can see which customer's records, so they're never created one row at a time. Phyllis sets up the target structure and a controlled bulk-load path for the data, but the live cases and transactions stay in your team's hands — she builds the machinery, your agents and customers create the work.

Yes. New case types and their forms and workspaces are built in their own application space, kept separate from the packaged banking product so upgrades stay clean and access stays contained. She reuses the shipped agent and viewer roles rather than re-authoring them, and handles product variants like deposit, loan and card through the platform's built-in inheritance — no guessed fields.

Phyllis discovers, proposes, and only builds once you approve. Every change lands in a scoped, reviewable change set that stays open until you ask to complete it — nothing is deployed or finalized without you saying so.

Every finding is cited to the exact record it came from — the actual servicing offer, case type or role — read live from your instance. She verifies each change by checking it back against the platform, so a silently dropped detail is caught and surfaced rather than reported as success.