The prompt
Score 10 of 10, Excellent
Use it when You have just finished a customer call and need accurate notes on the ticket, so the next person can pick it up without asking again.
- {{note_reader}}
- {{call_notes}}
- {{note_format}}
Full prompt and why it works
Prompt
Turn my notes or transcript from a customer support call into ticket notes, so that the next agent, or I next week, can pick up the case without asking the customer anything again. Write them for {{note_reader}}, who will read them in the ticket system. The call notes or transcript: """ {{call_notes}} """ Our required fields or note format, if we have one: {{note_format}} If we have no format, use these labels, each on its own line: Reason for call: one sentence in the customer's terms. Account details: identifiers mentioned, such as order or account number, plan or device. What we checked: numbered, with the result of each. What we told them: any promise, timing or policy we quoted, in close to the exact words. Outcome: resolved, pending with us, pending with the customer, or escalated. Next steps: who does what by when. Customer mood: one short phrase, such as "frustrated about repeat contact". Keep it under 200 words and factual. A good note lets someone who was not on the call continue the case without listening to the recording. For example, a "What we told them" line with the right precision: "Told the customer a replacement would ship within 2 business days; did not promise a delivery date." Record only what is in the notes. Do not add troubleshooting that did not happen, interpret what the customer meant beyond what they said, or include sensitive data such as full card numbers, passwords or health details; if the notes contain any, leave it out and add the line "Sensitive data removed from notes". Leave out opinions about the customer as a person. If something important is unclear, such as whether a promise was made or what the customer agreed to, write "[UNCLEAR: check recording]" in that field rather than guessing. If the outcome is not stated, write "Pending: not confirmed on call".
Variables
- {{note_reader}}
- Who reads the notes next, for example "the billing team" or "any agent on the queue".
- {{call_notes}}
- Your notes or the call transcript.
- {{note_format}}
- Your team's required fields, or "none".
Why it works
- Format. Seven fixed labels give every ticket the same shape, so the next agent finds the promise and the next step without reading the whole call.
- What to avoid. Card numbers, passwords and health details are stripped out, and nothing that did not happen on the call is added.
- If unsure. Unclear promises are marked for a check of the recording, since a wrong note about what was promised is worse than a gap.