Triage inbound service leads with a model that drafts the reply while rules decide the follow-up timing
A newsletter author describes a small services business that classifies enquiries, drafts a first reply and tags the owner in Slack, with human review and fixed follow-up rules, cutting handling time per lead.
Evidence: The author reports this. We have not checked it beyond reading the source.
The business problem
A small services business gets 30 to 60 enquiries a week and a person spends 12 to 18 minutes on each choosing the service, drafting a reply and routing it.
What was tried
An orchestration framework sends each enquiry and the service menu to a language model, which returns structured fields: lead category, likely intent, missing clarifying questions and a draft email. The draft is assembled, the lead owner is tagged in Slack, and a human reviews and sends it. Follow-up timing comes from deterministic rules based on lead age and category, because an early version that let the model decide over-followed leads that needed patience. A guardrails layer is meant to stop the model following instructions hidden in lead text, and it may not change prices or promise beyond policy.
What was reported (positive)
The author reports time per lead falling from 12 to 18 minutes to 5 to 7 minutes, about five hours saved a week on 50 leads, and drafts that consistently asked for budget, timeline and decision maker.
Limitations
A single anecdote with no sample size or time frame, no classification error rates and no conversion figures even though conversion was the motivation. The model, costs, hosting and guardrail implementation are not stated, and the triage prompt is not shown.
What you need
An orchestration framework (the post uses LangGraph), a language model account, Slack, and a service menu with clear boundaries. Costs and build time are not stated.
Sources
- The Anthropic Stack (Substack) ↗ Firsthand write-up, published April 22, 2026
Source published: April 22, 2026. Last reviewed here: October 11, 2026. Spot a mistake? Tell us.
Tools in this workflow
Related workflows
Send a Monday business metrics email from Stripe, Notion and Sheets with Claude writing the narrative in n8n
A shared n8n template pulls last week's Stripe revenue, Notion deal pipeline and a Sheets row of support numbers, has Claude write a three-paragraph summary, and emails and posts it to Slack.
Ship a conversion-focused landing page for a digital product in a weekend with Claude Design
A paid newsletter post explains two prompts and a workflow for designing a landing page with Claude Design, matching your brand, then handing the design to Claude Code to build.
Rebuild a landing page and assessment funnel with Claude Design, Claude Code and email automation
A creator used Claude Design to build a brand system and landing page from her existing copy, Claude Code to build the assessment site, and an email tool to send profile-specific sequences.
Replace three transactional emails with a behaviour-triggered lifecycle sequence planned and built by Claude Code agents
A developer says a SaaS with only welcome, reset and receipt emails lost users after a day, and a Claude Code command planned and built six lifecycle sequences that check app state between sends.