Onboarding stall nudger
New customers stall during onboarding because nobody notices they're stuck on step three of eight. Design an agent that tracks each account's onboarding checklist and nudges the right people when things stall. Who does it message — the customer, your team, or both — and what tone lines can it never cross? How do you test that the nudges help rather than annoy before rolling it out broadly? Give me the short pitch you'd make to the onboarding lead.
decide_onboarding_nudge(days_since_progress: int, ignored_nudges: int, days_since_last_nudge: int, agent_silenced: bool) → str[5,0,-1,false]out"nudge_internal"[5,1,9,false]out"queue_customer_email"[1,0,-1,false]out"wait"Turn the fuzzy goal into a bounded agent task. Say what the agent reads, what it may do on its own versus draft for a human, and what it must never touch. Then earn the trust: how you’d verify it before rollout, and the pitch (the problem, what you built, why it matters).
Agent build: design the agent in plain language (or narrate it). The coach grades the decomposition, the guardrails, the verification plan, and the pitch.