Repository navigation
Send in the recipient's business hours; one bump when a thread goes quiet for 7 days - #129
Merged
Merged
Conversation
…retire bounced addresses Hunter's outreach planner, run by the worker instead of remembered by a person: - Every address is verified before its first message and again after 90 days (MX, then an SMTP RCPT probe where port 25 allows; a blocked port sends on MX alone). Verdicts are cached in email_verifications, 25 fresh checks per run. - A bounce the delivery report pins to an address marks it invalid for good and stops the person's cadences. The sender query skips invalid addresses. - A campaign whose bounce rate passes 2% over 50+ sends pauses itself, re-verifies every queued address, drops the failures and resumes on a fresh window once a complete pass finds nothing waiting (campaign_list_health). - Accept-all addresses send only while the campaign bounces at or under 1%. - GET /autogtm/campaigns/:id/list-health, og leads health, MCP get_list_health. Migration 0053. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…udget holder Hunter's planner reaches four people per target company, one at a time, a month apart: budget holder, pain feeler (end user), blocker (legal, security, IT, finance) and champion (manager). Now automatic: - classifyPersona reads the job title deterministically (no model on the send path). - Autopilot orders each company's queued cards by persona behind its best card, without changing the order between companies. - A colleague emailed in the last 21 days, or on an active cadence, who has not answered holds the company; everyone else there waits, card intact. A reply releases it. Deliberately reverses the old "two mailboxes at one company both get written to in one run" test. - Drafts get a per-role angle added to the step's guidance. - GET /autogtm/campaigns/:id/accounts, og leads accounts, MCP get_campaign_accounts: who was reached, who is next, missing personas. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts: # apps/api/src/autogtm-docs.ts # apps/api/src/autogtm.ts # apps/cli/src/commands.ts # apps/mcp/src/tools.ts # packages/domain/src/index.ts # packages/pipeline/src/autopilot.ts # packages/pipeline/src/index.ts
…es the default Hunter's planner: test one variable, 50+ recipients per variant, measure by reply rate, carry winners forward. Now automatic, hourly per workspace: - decideAbTest: every arm needs 50+ sends; the leader wins at a one-sided 95% two-proportion z-test against the runner-up, or once every arm has 200+ the best wins (A keeps its place on a tie). Opens are not an input. - promoteAbWinners makes the winning angle the step intent, clears the variants and records the test in ab_results; later tests on the step count only runs after the decision. - Fix: the variant report counted only `replied`, but the mailbox poll writes `responded`, so every polled reply was missing from A/B results. The query now lives in the pipeline (variantStats) and reads both. - GET /cadences/:id/variants now includes `decided`; GET /ab-results; og cadences ab <id>; MCP get_ab_results. Migration 0054. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…uiet for 7 days Hunter's planner: send during business hours; gone quiet, one bump at 7 days. - recipientTimezone infers an IANA zone from the person's location, then the company's, then the mail domain's country code (US state codes only as a ", XX" suffix, after every place name). Falls back to US Eastern. - Autopilot holds a cold card outside Monday-Friday 08:00-17:00 local and says when it opens. The worker turns this on; tests stay hour-independent. - bumpQuietThreads (hourly): an interested/question reply we answered, then 7+ days of silence, gets exactly one follow-up card, marked by its guidance. It goes through the triage answer path (draft, live policy, decideAutoReply), so it sends unattended only where autonomous replies are already allowed and is an approval card everywhere else. Threads older than 30 days are never woken; bumps are only created in business hours. - The reply composer gets a follow-up mode that grounds in our last message. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts: # apps/server/src/index.ts # packages/domain/src/index.ts # packages/pipeline/src/autopilot.ts
This was referenced Oct 7, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fourth Hunter outreach-planner feature, fully automated: "send during business hours" and "gone quiet: one bump at 7 days".
Business hours
recipientTimezoneinfers an IANA zone with no lookups. It tries the person's location first, then the company's, then the country code of the mail domain. US state codes only count as a ", XX" suffix, and only after every place name has been tried: "or" and "co" are ordinary words, and "Toronto, ON, CA" is Canada. Anything left over falls back to US Eastern.businessHours: true). Tests leave it off, so the existing suites don't depend on the hour they run at.One bump after 7 quiet days
bumpQuietThreadsruns hourly. A thread qualifies when the person answeredinterestedorquestion, we answered them, and 7+ days have passed with nothing back. It gets exactly one follow-up card, marked byguidance = 'follow_up_bump'.decideAutoReply. So it sends unattended only where autonomous replies are already allowed, and is an approval card everywhere else. Human approval stays the default.No migration.
Tests: domain
timing.test.ts(12: zones, open/closed hours, next opening), pipelinetiming.test.ts(4: gate closed and open, one bump only, nothing before 7 days or after 30). The triage, composer, draft, autopilot and domain suites all pass locally (412 tests).🤖 Generated with Claude Code