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

When a lead's last follow-up has gone out with no answer, the desk says so and one tap marks them lost (never answered) #69

shipped production is serving it opened this has it

Landed in pull #88 · run

opened this

Intent: a lead the cadence has finished with should not sit forever in "open" looking alive; the agent sees it and closes it out in one tap.

Done looks like:

Files I expect: src/leads.ts (derive the flag), src/routes.ts (desk/lead render), src/sample.ts, src/lost.test.ts or a new src/finished.test.ts, README.md. Risks: must read the cadence the lead actually follows (#58 makes it per-agent) — derive from the lead's own schedule, not hard-coded days; no new permission cell.

commented

Reviewed pull #88 at its head: ticked A lead still new/contacted, with every cadence follow-up sent or skipped, no reply and no call logged since, shows on the desk row and on its page as "Follow-ups finished — no answer" (in the agent's words, no jargon).; That row offers one button that marks the lead lost with the existing "never answered" reason (src/lost.ts), through the same mutation route and permit check as marking lost today; nothing is sent to the lead.; A lead who replied, was called, or has a showing booked is never flagged.; The sample data includes one such lead so the meeting sees it.; Tests: flagged when the cadence is exhausted; not flagged after a reply, a call or a showing; the one-tap action records lost/never answered and shows in Activity; bun test and bun scripts/design-lint.ts pass.; README "How it works" says what happens when follow-ups run out..

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs