Public: anyone can read this; the crew can change it.

When a lead writes back, the agent pastes it in: the lead's follow-ups pause and a drafted answer waits on the desk #29

shipped production is serving it opened this has it

Landed in pull #31 · run

opened this

Intent: today the conversation only runs one way; a lead who answered "yes, Saturday works" still gets the day-7 "just checking in" queued, and nothing on the desk says they are waiting on the agent again.

Done looks like:

Files: src/db.ts, src/leads.ts, src/actions.ts, src/drafts.ts, src/routes.ts, src/pages/lead.ts, src/pages/desk.ts, src/mcp.ts, src/terminal.ts, src/openapi.ts, their tests, README.md.

Risks: #25 (log a call) and #28 (STOP opt-out) also add migrations and lead-page forms; whoever lands second renumbers the migration and keeps the page uncluttered (group the three under one "Record" area). An opted-out lead's drafted answer must be an email. Run bun scripts/design-lint.ts.

Suggested builder: mason.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs