Build a Customer Health and Retention Planning Agent
Build an agent that combines product usage, support history, and renewal dates into account health summaries. Recommend evidence-backed follow-up plans and track human-approved actions without inventing retention outcomes.
What you are building
The core problem, expected build, and operating context for this challenge.
A customer success manager prioritizing accounts that need attention.
Build an agent that combines product usage, support history, and renewal dates into account health summaries. Recommend evidence-backed follow-up plans and track human-approved actions without inventing retention outcomes.
Usage history
Support tickets
Renewal dates and intervention policies
Join account usage, support, and contract data.
Check data freshness and instrumentation health.
Explain account risks and propose relevant follow-up actions.
Build a prioritized customer-success review queue.
An account health dashboard with trend charts, supporting events, renewal dates, and editable follow-up plans.
Prioritize an account review for A1 and an instrumentation investigation for A2, with separate explanations and no automatic discount.
A working local application with the specified review interface.
Source code, dependency lockfile, and setup commands.
A recorded end-to-end demo using the supplied starter data.
Example outputs, action logs, and automated tests.
These fictional records are a small development fixture, not a production dataset. Implement the mock services described in the brief.
```json { "accounts": [ { "id": "A1", "weekly_active_users": [ 100, 90, 30 ], "collector_healthy": true, "open_incidents": 2, "renewal_days": 14 }, { "id": "A2", "weekly_active_users": [ 100, 0, 0 ], "collector_healthy": false, "open_incidents": 0, "renewal_days": 60 } ], "policy": { "automatic_incentives": false } } ```
Use synthetic records and draft actions. Do not contact customers or offer incentives. Choose an available model that supports your implementation. Record its identifier and version.
Review the complete application, not only the starter-case answers.
The account summaries cite the supplied events.
A2 is not labeled disengaged from missing telemetry alone.
No retention improvement is claimed without outcome data. Add one normal case, one incomplete-input case, and one failure-recovery case.
Participation guide
Use synthetic records and draft actions. Do not contact customers or offer incentives.
How work is evaluated
Review workflow completion, interface usability, evidence quality, and safe failure handling. No agent execution has been verified.
A working local application with the specified review interface. Source code, dependency lockfile, and setup commands. A recorded end-to-end demo using the supplied starter data. Example outputs, action logs, and automated tests.
Challenge datasets
Public datasets, plus the private datasets you have access to.
What you should walk away with
Join account usage, support, and contract data.
Check data freshness and instrumentation health.
Explain account risks and propose relevant follow-up actions.
Build a prioritized customer-success review queue.
Reference links and supporting material
Supplied fictional starter records: Usage history, Support tickets, Renewal dates and intervention policies. The overview includes the complete JSON bundle. Implement local mock services and extend the sample coverage.
Challenge setup
Configuration summary for this challenge.
Challenge input
Input details are not configured.
Pydantic AI
Typed Python agent framework.
Evaluated output
No output checks are configured.
- No evaluation checks are configured.
- 1 public reference case
- 1 configured tool
Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.
View technical recipe
Configured tools
- Pydantic AI ยท Optional
Evaluation contract
- No evaluation checks are configured.
Reference cases
- 1 public reference case
Workflow tasks
No workflow tasks are configured.
Recipe freeze marker
No recipe freeze time is recorded.