← ClaudeAtlas

replies-48h-slalisted

Keep every thread where the ball is on our side answered within 48 hours. Use at the start of every reply-handling run and every daily summary, to build and clear the overdue list.
dostrovcev/outbound-agent-skills · ★ 0 · AI & Automation · score 68
Install: claude install-skill dostrovcev/outbound-agent-skills
# No lead waits more than 48 hours when the ball is ours The ball is ours when the lead replied, asked a question, is agreeing a meeting time, or sent a contact. From that moment the answer goes out within 48 hours. Safe replies go out right away. Disputed ones become a draft for a human in the same run, and the draft does not stop the clock. ## Why Before this rule, one lead with a proposal in hand waited about two weeks without a follow-up, and three leads who had asked to reschedule sat with no nudge. Separately, four leads were lost after the booking link went out and nobody checked whether they booked. Each of these was a person who had already said yes to a conversation. A cold lead costs a touch; a warm lead left waiting costs the deal. ## How to apply 1. At the start of each run, build the overdue list: every lead where the next move is ours (the machine's or a human's) and the last touch is older than 48 hours. 2. Put the overdue list first, before new work. 3. For each item: - safe class (see `replies-triage`): answer and send now - needs a human: write the draft now, flag it where the human looks today, keep it on every summary until it is handled 4. Before any scheduling nudge, check the meeting did not already happen: all calendars past and future, the call recorder, the last message. 5. Clear the list by the end of the run. Whatever cannot be cleared gets named in the summary with its age in days. ## Check before closing the run - [ ] Overdue list was