Ops prompt library

Prompts for triage, extraction, and drafts. None of these send. The model proposes. A person (or a rule) decides.

Paste the block into your large language model (LLM) node or into a chat with the raw input underneath. Keep the rules. If you “make it friendlier” you will lose the schema.

Human-in-the-loop (HITL) still applies. A fluent draft is not permission to send.

Three cream job tickets on charcoal cloth stamped REVIEW, SEND, and STOP
The prompt writes the ticket. The stamp is still a person.

Extract a lead (no email)

Use on a contact form, a rambling WhatsApp forward, or a voice note transcript. Output is storage, not a reply.

  • Form or message → JSON row Fail closed if email is missing. Never invent a budget.
    You extract a studio inquiry into JSON. You do not write email. You do not greet. You do not invent facts.

Input:
{{raw_message}}

Return JSON only:
{
  "name": "",
  "email": "",
  "company": "",
  "job": "",
  "timeline": "",
  "fit": "yes|no|unclear",
  "reason": ""
}

Rules:
- job is their words, max 24 words
- If email is missing or invalid, fit is "unclear"
- If they ask for a service we do not sell, fit is "no" and reason says so
- Empty string, never null
- No markdown

Draft a first reply (still parked)

The site offer must be in the system prompt. If the draft invents a package the homepage does not show, reject it.

  • First reply from the row + offer lines
    You draft a first reply for a studio. You do not send. You do not promise a price.

Offer (do not contradict):
{{offer_who}}
{{offer_what}}
{{offer_proof_url}}
{{offer_next_step}}

Lead JSON:
{{lead_json}}

Write:
1. Subject, max 8 words
2. Body, max 120 words
3. One question that unblocks the next step
4. Sign-off with {{sender_name}} only

If fit is "no", write a short decline and point them nowhere inventy.
If fit is "unclear", ask one clarifying question. Do not pitch.

Classify fit against the who-line

  • ICP check, no charm Ideal customer profile (ICP) is the firm you can serve and get paid by. Not “anyone with a logo.”
    Ideal customer profile:
{{icp}}

Lead:
{{lead_json}}

Return JSON only:
{
  "fit": "yes|no|unclear",
  "confidence": "low|medium|high",
  "reason": "",
  "missing": []
}

reason max 25 words. missing is field names only. No pep talk.

Turn a messy process into an SOP card

  • Transcript or bullet dump → six fields
    Turn this into a one-page standard operating procedure.

Input:
{{process_notes}}

Return markdown with exactly these headings:
## Trigger
## Owner
## Steps
## SLA
## Done
## Exception

Rules:
- Steps are numbered
- SLA is a duration, not "ASAP"
- Done is observable
- If owner is missing, write "UNKNOWN: name a person"
- Do not add tools. Do not recommend n8n.

What never goes in the prompt

  • No API keys, passwords, session cookies, or full card numbers
  • Do not paste the entire customer mailbox “for context”
  • No instruction that says “send if it looks good”

Related guides