SingleTask.ai · CS Team
CS Manager + 3 workers. Onboarding, health monitoring, renewal/expansion.
How customer success works here
Keeps existing customers retained and expanded for SingleTask.ai.
Each morning the CS Manager reads the latest CCO strategy and runs across active customers — reviewing onboarding progress, health scores, and renewal windows. The Onboarding, Health Check, and Renewal workers materialize onboarding touches, compute health from cross-app signals (BoatLife / SingleTask DB reads), and draft renewal pitches. Every customer-facing send still routes through /queuefor your approval. A nightly health_check_sweep proposes one health check per active customer.
Wave 4 shipped — CS workers live
All 3 CS workers are real. Onboarding materializes 30-day sequences (emails awaiting approval, internal checks auto-execute). Health Check writes time-series signals + auto-flips at-risk customers. Renewal drafts pitches with usage context. Cross-app DB pools: 1 of 2 configured.
Without cross-app DB, Health Check still runs against customers.last_login_at on THE OFFICE side and produces a partial score. Configure BOATLIFE_DB_* / SINGLETASK_DB_* env vars for full cross-app signals.
CS Manager status
Schedule: "SingleTask.ai · CS Manager" (10 7 * * 1-5) — enabled · Health sweep: 0 3 * * *
Customer status mix
Live count from customers table.
No customers yet. The bootstrap script that seeds customers from BoatLife brokers lands in the next per-wave session — until then this table stays empty and the health sweep is a no-op.
Active onboardings
Customers within 30-day onboarding window.
No active onboardings.
At-risk signals
Customers with latest health_score below 50.
No at-risk customers. Health signals populate once the cross-app DB read pools (BoatLife / SingleTask) land in the next per-wave session.