Recall campaigns, quality cases and dealer claims that run themselves.

She stands up the configuration that makes commercial operations run — recall campaigns, the quality investigation setup, dealer and service records, product-linked labor codes, and sales promotions with their eligibility and claim rules. The live cases and claims stay in your team's hands; Phyllis configures the engine that routes, prices, and adjudicates them.

She builds the whole campaign structure — the phases, corrective actions, and the part and labor rules dealers claim against. The steps that take a recall live are deliberately left as your call; Phyllis stages the build, and you flip it live when you're ready.

Quality cases and investigations are day-to-day records, so she reads them for discovery rather than creating them. What she configures is everything around them — the problem-capture setup, the choices, routing, review targets, workspace, and reporting — and she can map a legacy quality app onto this rather than rebuilding from scratch.

Correct. Phyllis discovers, proposes a plan, and only builds on your explicit approval, staging every change in a reviewable package. Because commercial operations spans several areas, she keeps each area's changes cleanly separated, and self-heal fixes run only when you approve them.

Every claim is cited to what she found in your live instance — the installed apps and release, a live campaign's corrective actions, the labor codes a claim charges against, the promotion rules in play. She reads your real setup rather than assuming out-of-box defaults, because on migrated instances dealer, promotion, and quality config drift from the baseline.