ModelVerdict

Tyler Brown

English (US)Email9 fields

Document en-p0016 · layout thread · 9 fields · public part of the dataset · Same invoice in Czech → · Report an error in this example

Email text (the model received exactly this text)

From: Tyler Brown <tyler.brown@whitaker-anderson.example>
To: support@miller-jones.example
Date: Wed, Nov 19, 2025 at 1:58 PM
Subject: Re: Can't log in

Hi,

I'm following up on the message below, nothing has happened so far. Thank you for handling this. Our operations are at a standstill right now.

Kind regards,
Tyler Brown
Whitaker, Anderson and Miles

On Thu, Nov 13, 2025 at 1:25 PM, support@miller-jones.example wrote:

> Hello, thank you for your message. We've logged your request as ticket #92733 and are looking into it.
>
> Miller-Jones

> On Thu, Nov 13, 2025 at 11:58 AM, Tyler Brown <tyler.brown@whitaker-anderson.example> wrote:

> > Hi,
> >
> > Since this morning we can't log in to your portal, the page shows a 500 error.
> >
> > Kind regards,
> > Tyler Brown
> > Whitaker, Anderson and Miles

Verdict

Cheapest with no errors: GLM-5.3 Flash at $0.46 per 1,000 documents.

  • Gemma 4 31B is 3.7× cheaper, but: wrong value (Sentiment).
  • GPT-6 Luna is 3.6× cheaper, but: wrong value (Sentiment).
  • Mistral Small 4 is 3.2× cheaper, but: wrong value (Sentiment).

Prompt given to every model

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.

How we score

Exact match per field after normalizing dates, amounts, and whitespace. Missing diacritics count as an error. Cost is the actual token spend of this run, converted at the rate shown in the footer.

Free with login

Every model's output for this document, field by field. The first three examples of each task are open.

Just your email, no password.

Log in with email

We use your email only to log you in (and for the digest if you tick it). No spam.