Followup

GPTClaudeDeepSeek··▲ 596 copies·updated 2026-07-14

followup.prompt

---
title: CRM — Follow-up
owner: unassigned
status: populated
volatility: stable
last_reviewed: 2026-06-28
inject_into: [crm-workflows]
tokens_approx: 0
---

# CRM — Follow-up

Task: draft a customer-facing follow-up after a scoping call or demo, logged from the CRM. Register: warm, professional, complete sentences, no internal jargon (`voice.md`).

## Structure

1. **Thank + reflect** — name back the application they described (volume, menu, sites) so they know we listened.
2. **Recommendation recap** — the equipment family and the attach (beans + service), framed to their goal. Specifics only from the catalog.
3. **Next step** — a scoping/quote conversation with an advisor, never a price.

## Rules

- No prices, lead times, discounts, or SLAs (RULE-01/RULE-02) — route to an advisor for a configured quote.
- No recommendation if scope was incomplete; instead, ask the missing discovery question.
- Flag anything ungrounded with `[REVIEW: ...]`.
- One clear next step. Don't stack asks.

## Output

A send-ready email/CRM note in the customer register, ending with one concrete next step.

when to use it

Community prompt sourced from the open-source GitHub repo matthewjbis/context-kit (no explicit license). A "Followup" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.