ReachLog 1.0.1: replies, follow-ups and fewer manual updates
ReachLog's 1.0 release adds optional AI reply triage, follow-up drafts and inbound lead capture. Version 1.0.1 also fixes the npm README screenshots.
ReachLog 1.0.1 is now on npm. The AI features introduced in 1.0.0 help with the work that sits between conversations: reading a reply, deciding what needs attention, drafting a follow-up and keeping the contact's status current.
The original reason I built ReachLog hasn't changed. I wanted to open a contact, see the conversation and know where things stood. The 1.0 release helps with the repeated reading and updating around that.
What it can help with
Reading replies. ReachLog can identify the sender's intent, requests and commitments, with quotes from the message so you can see what the assessment is based on. Strong evidence can move an opportunity forward in the pipeline. Suggestions that need a decision go into AI review.
Preparing the next email. Follow-up drafts use the recent conversation history. You can keep them as drafts to review, or explicitly enable automatic follow-ups within existing threads.
Capturing new enquiries. Business email that doesn't match an existing target can become a new lead or a review item, instead of staying disconnected from the rest of your contacts.
The decisions that stay with you
AI and automatic sending are off by default. ReachLog never automatically marks an opportunity Won, and it leaves pipeline stages alone if you changed them manually in the previous seven days.
Optional auto-send only works inside an existing thread. It has a daily limit, respects sending blocks and checks again after drafting. A newer reply, cancelled follow-up, reschedule or pipeline change can stop an outdated message from going out. It does not send cold outreach automatically.
There is a smaller fix I particularly like: out-of-office messages and automatic replies no longer cancel follow-ups or make a target look as though it has replied.
Choose your provider, or keep it manual
ReachLog works with OpenAI-compatible providers, including compatible local model servers. You supply the endpoint and model. Hosted providers receive the email content used for triage, drafting or lead extraction; a local endpoint can keep that processing on your machine.
The contacts, accounts, pipeline, SMTP/IMAP connections, templates, exports and backups are still there. You can use all of that with AI disabled.
Version 1.0.1 fixes the screenshots in the npm README. They now load from the public npm package CDN, using the published 1.0.0 image assets. The previous GitHub links required access to the private repository.
Try 1.0.1
The separate read-only demo includes sample conversations and AI review items:
npx reachlog demo
To start your own empty workspace:
npx reachlog
Both require Node.js 22 or 24. Existing installations retain their data when upgrading; keep your data directory and make a backup first. AI remains disabled until you configure and enable it.
ReachLog is free and MIT licensed.