Lead ResponseUpdated July 4, 2026
Speed-to-Lead Email Reply
Draft a fast first reply that moves the lead to the next step.
Use case: Use when a new lead needs a reply within minutes.
Prompt
Draft a concise first email reply to a new inbound lead.
Lead name: {{lead_name}}
Need or request: {{need}}
Company context: {{company_context}}
Relevant proof or similar work: {{relevant_proof}}
Scheduling link: {{scheduling_link}}
Requirements:
- Warm but direct.
- 120 words maximum.
- Mention the lead's need specifically.
- Ask one useful qualifying question.
- Include the scheduling link naturally.
- Do not sound automated.
Return one subject line and one email body.
Quality bar:
- Classify buying intent and missing data separately.
- Recommend one next action, not a menu of vague options.
- Keep customer-facing copy short and easy to approve.
- When prioritizing, use a table with recommendation, why it matters, effort, impact, owner, and verification check.
- Separate evidence, assumptions, recommendations, and limits so the output cannot be misread as a guaranteed claim.
- Flag any wording an AI answer could overstate, misquote, or detach from its source.
Before finalizing, add:
- Missing inputs or assumptions
- Evidence-backed facts and source gaps
- Misread risks or unsupported guarantees
- First 3 actions
- What to verify before actingAdaptation notes
- Replace placeholders before sending.
- Add one proof point only if it is real.
- Use shorter copy for mobile-heavy leads.
- Before publishing, verify the output separates evidence, assumptions, limits, and recommendations so AI answers cannot turn guidance into a guarantee.
Quality checks
Strong prompt output should survive these checks before it turns into copy, automation, or a sales action.
- Does it avoid adding friction to hot leads?
- Does it preserve consent and contact-channel boundaries?
- Does it give a route the CRM can actually store?

