taro-play-runner

Selecting a customer success play involves matching the account situation to a configured TARO framework with trigger, action, resource, and outcome. The system evaluates health alerts or lifecycle stages to recommend plays like adoption pushes or renewal acceleration with execution-ready outreach.

The TARO play framework structures customer success motions around Trigger, Action, Resource, and Outcome. It produces execution-ready deliverables such as email drafts, meeting agendas, and action plans calibrated to the specific account context and lifecycle stage.

Yes, customer-ready email drafts for renewal acceleration can be generated through play execution. The system produces contextualized outreach deliverables calibrated to the account profile and selected play, ensuring internal health details are scrubbed from customer-facing output.

Yes, configured CSM context files are required for play execution. The system needs access to plays context from CLAUDE.md and company-profile.md to generate accurate, account-specific outreach and action steps aligned with the escalation matrix.

Escalation routing during at-risk recovery play execution enforces trigger confirmation and routes steps according to the configured escalation matrix. It applies governance guardrails to prevent leaking internal risk or health details into customer-facing outputs.

Automated customer success outreach generation is limited by its dependency on configured CSM context files and requires trigger confirmation to proceed. It cannot execute plays without access to CLAUDE.md and company-profile.md, and all outputs must align with the configured escalation matrix.