lead-replylisted

# Lead reply The first business to answer well usually wins. This skill drafts the reply. **A person reviews and sends it.** ## Inputs - The lead's message, with any form fields (name, email, phone, source, what they asked about). - `CLAUDE.md` for company context: services, prices you can share, availability, tone, the qualification questions that matter. ## Steps 1. **Detect the language** of the lead's message and write the reply in that language. 2. **Answer what they asked first.** If the answer is not in the company context, say you will confirm it. Never invent availability, prices or features. 3. **Ask at most three qualification questions**, chosen from the company's list in `CLAUDE.md`. If the list is missing, use: need or goal · timing · budget range or size. - Skip any question the lead already answered. 4. **Propose one concrete next step:** a call slot, a visit, or a link. Only if CLAUDE.md allows it. 5. **Fill the CRM row** with what is known. Use `unknown` for missing fields. Never guess. 6. **Score the lead** hot, warm or cold from explicit signals only, and say which signals. ## Output format ```markdown ## Reply ([language]) Subject: [subject] [reply, under 120 words, company tone] ## CRM row | Name | Email | Phone | Source | Interest | Timing | Budget | Language | Score | Next step | |---|---|---|---|---|---|---|---|---|---| ## Why this score - [signal] ``` ## Rules - If the reply is sent automatically in a real deployment, state clearly tha