Prompt Library
Starter prompts your team can use today.
A sampling of the kind of prompts we ship with every engagement. Filter by industry or category. Each prompt is tuned to reduce hallucinations and make the output easy to review.
13 of 13 prompts
Front Desk
Patient Email Triage
You are triaging an inbound patient email for a small medical clinic.
Classify the email as one of: scheduling, billing, prescription, clinical_question, other.
Then draft a polite, concise reply in the clinic's voice. If scheduling, propose 2 time slots from the provided availability. Never give medical advice; defer clinical questions to a clinician.
Email:
{{email_body}}
Availability:
{{availability}}
Output JSON: { "category": ..., "reply": ..., "needs_clinician_review": bool }Medical Assistant
Intake Form → Structured Note
Summarize this patient intake form into a structured note with these sections:
- Chief complaint
- Symptoms (with onset + severity)
- History (relevant only)
- Medications
- Allergies
- Red flags (if any)
Use bullet points. Do not infer anything not present. Mark missing required fields as [MISSING].
Intake form:
{{intake_text}}Doctor
Voice Summary → Visit Note
Convert the spoken visit summary below into a structured SOAP note.
Rules:
- Use only information stated by the clinician; do not fabricate findings.
- If the clinician did not cover a section, write [NOT DOCUMENTED].
- Keep it concise and clinical.
Spoken summary:
{{transcript}}Office Manager
Weekly Practice Report
Generate a weekly practice summary for the owner from the data below.
Include:
- Patients seen (with delta vs prior week)
- Cancellations and no-shows
- Revenue totals
- Top 3 trends worth attention
- One recommended action
Tone: concise, executive.
Data:
{{weekly_data}}Accountant
Invoice → Accounting Entry
Extract a clean accounting entry from this invoice.
Return JSON with: vendor, invoice_number, date, total, currency, tax, line_items[{description, quantity, unit_price, amount}], suggested_category.
Use the chart of accounts below for suggested_category. If uncertain, set suggested_category to null and explain in a "notes" field.
Chart of accounts:
{{chart_of_accounts}}
Invoice text:
{{invoice_text}}Accountant
MoM Variance Narrative
Write a month-over-month variance narrative for the numbers below.
For each line with >10% change, explain the likely driver in one sentence based on the notes. Do not speculate beyond what the notes support. End with a 3-bullet "watch list" for next month.
Numbers:
{{numbers}}
Notes:
{{notes}}Admin Staff
Client Email Reply (Accounting)
Draft a reply to the client email below.
Rules:
- Match the tone of the firm: warm but precise.
- If the question is about deadlines, confirm them against the calendar provided.
- If the question requires partner sign-off (tax filing, engagement scope), say so and offer to route it.
Calendar:
{{calendar}}
Client email:
{{email_body}}Property Manager
Tenant Email → Maintenance Ticket
Read the tenant email and produce a maintenance ticket.
Return JSON:
- unit (if mentioned)
- category (plumbing | electrical | hvac | appliance | other)
- urgency (emergency | same_day | standard)
- description (1-2 sentences)
- suggested_contractor_type
- tenant_reply (confirmation message with expected timeline)
Tenant email:
{{email_body}}Property Manager
Lease Summary
Summarize the lease below in a 1-page brief:
- Parties
- Term (start, end, renewal terms)
- Rent and escalations
- Deposit
- Maintenance responsibilities (who does what)
- Notable clauses (pets, subletting, early termination)
- Key dates in the next 90 days
Lease:
{{lease_text}}Property Manager
Rent Reminder Draft
Draft a rent reminder to the tenant.
Tone: friendly, not threatening. If this is the second reminder, be slightly firmer and include payment methods. If third, include the late fee per the lease and a request to reply by a specific date.
Tenant: {{tenant_name}}
Unit: {{unit}}
Amount due: {{amount}}
Reminder number: {{n}}
Due date: {{due_date}}Dispatcher
Service Quote from Request
Generate a service quote from the customer's request and our pricing rules.
Include: diagnostic fee, estimated labor hours, likely parts, total estimate range, assumptions, and what could change the price. Keep the language plain. End with a clear call-to-action to schedule.
Pricing rules:
{{pricing_rules}}
Customer request:
{{request}}Dispatcher
Dispatch Match
Pick the best technician for this job from the roster below.
Consider: skill match, current location, workload today, customer location. Return the top choice and a backup. Explain the pick in one sentence each.
Roster:
{{roster}}
Job:
{{job}}Admin
Post-Job Follow-up
Write a follow-up to the customer after the service visit.
Include: thanks, brief recap of work performed, any recommended next steps, maintenance tip relevant to the work, and a review request with the link.
Visit notes:
{{visit_notes}}
Review link: {{review_link}}Try it
Describe a task — we'll write the prompt.
Powered by Claude. This is the same approach we use to build client prompt libraries.
Want the full library?
Every engagement ships with 50–100 prompts tuned to your workflows, roles, and tone.