Christine Copeland

Prompt für alle Modelle

You triage the support inbox. Read the email below and return only JSON with these keys:

category        one of: billing (invoices, payments, charges), delivery (where is the order, shipping,
                address change), complaint (damaged, wrong or defective goods, warranty claims),
                technical (login, app or system errors, integrations), cancellation (cancel an order,
                contract or subscription), sales (quotes, prices, interest before buying)
priority        one of: urgent, high, normal, low (rules below)
sentiment       one of: positive, neutral, negative (the customer's tone)
customer_name   full name of the customer who wrote the request
order_number    the customer's order number, if mentioned
invoice_number  invoice number, if mentioned
amount          the amount of money the request is about (number)
currency        ISO 4217 code of that amount (USD, EUR, CZK, …)
deadline        the date by which the customer wants a resolution or answer (YYYY-MM-DD)

Priority rules:
- urgent: the customer cannot work right now, or the deadline is at most 1 day after the email date
- high: the deadline is at most 7 days after the email date, or the customer threatens to cancel
  or escalate (lawyer, ending the business)
- low: the customer says explicitly that it is not urgent
- normal: everything else

Rules:
- A thread: judge the newest message; order numbers, invoice numbers and amounts may come from the
  quoted earlier messages. A forwarded email: the customer is the original sender, not the
  colleague who forwarded it.
- Resolve relative deadlines ("by Friday", "by tomorrow", "by the end of the month") against the
  date of the message that states them.
- Support ticket numbers, tax IDs and phone numbers are not order or invoice numbers.
- If a value is not in the email, return null. Do not guess.
- Amounts as numbers with a decimal point, no thousands separators and no currency symbol.

So bewerten wir

Exakte Übereinstimmung pro Feld nach Normalisierung von Datumsangaben, Beträgen und Leerzeichen. Fehlende diakritische Zeichen zählen als Fehler. Die Kosten sind der reale Tokenverbrauch dieses Laufs, umgerechnet zum Kurs in der Fußzeile.