Handle a formal patient complaint or grievance
An investigation plan and a written grievance response that meets common timeline and documentation expectations for healthcare organizations.
The prompt
Help me handle a formal patient complaint at our clinic.
How it was received: [phone, letter, portal, in person, via payer or state agency]
Date received: [DATE]
Summary of the complaint: [WHAT THE PATIENT SAYS HAPPENED and what they want]
Type: [billing, access/wait times, staff conduct, communication, privacy, quality of care concern]
What we have found so far: [FACTS from staff statements, records, call logs]
Applicable requirements: [e.g. our grievance policy, Medicare or Medicaid plan rules, accreditation standards, state rules - PASTE if known]
Give me:
1. Triage: is this a simple complaint resolved on the spot, or a grievance needing written response? Flag immediately if it involves a possible privacy breach, abuse, or a patient safety issue, and who must be notified (privacy officer, medical director, risk management).
2. An investigation checklist: who to interview, which records and logs to review, and what to document.
3. A written response letter to the patient: acknowledges the concern, states the steps we took to investigate, the outcome and any corrective action in general terms, and a contact for further questions. No blame on named staff, no admission of liability, and no clinical judgments. Mark unknowns as [CONFIRM].
4. A timeline table: Step | Owner | Due date, using our policy's deadlines (mark as [CONFIRM] if I haven't given them).
5. How to log it for trend tracking.
Any complaint that alleges harm from care should be reviewed by our medical director and risk manager before we respond.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Customer Support prompts
What to fill in
- phone, letter, portal, in person, via payer or state agency
- DATE
- WHAT THE PATIENT SAYS HAPPENED and what they want
- FACTS from staff statements, records, call logs
- CONFIRM
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Write order, shipping, refund, and delay noticesTransactional messages: confirmations, cancellations, refunds, shipping updates, and delays.
- Respond to a customer who wants to cancelA response and save-call plan that finds the real reason for cancelling and offers the right fix, or exits gracefully.
- Decline a customer feature request without damaging the relationshipA reply that says no or not now to a feature request, offers alternatives, and keeps the customer feeling heard.
- Tell my accounts about a product change that affects themCustomer-specific messages about a deprecation, migration, or major product change: what it means for each account and what they must do.