Check your AI agent bill against your own tickets

A total does not tell you which conversations produced it. To check a per-resolution bill, compare the vendor's billed conversations with the conversations your own support records count under one clear rule.

You are comparing two rules over the same conversations: the vendor's published rule, which produced the bill, and your rule, which produces your record. The check shows where they differ, line by line.

What you need

• The vendor's invoice or, where the vendor offers it, its list of billed conversations.
• Your own ticket export for the billing month, plus a week or two after it. Late reopens and returns land after the month closes.
• The rule you think should decide. Start with the vendor's published resolution definition.

Compare the two lists

1. Build “your record” as a CSV containing only the conversations you count as resolved. Put one conversation on each row with its conversation ID, per-resolution price, and date.
2. Open the Invoice Audit tool. Load the vendor's billed list as the vendor invoice, then load your CSV as your record.
3. Map the conversation ID as the key, plus the amount and date columns. The vendor file needs an amount on each line. If the billed list has no amount column, add one with the per-resolution price. Run the comparison.
4. Read the lines that appear on the vendor's billed list but not in your record. Then read the other direction: rows in your record that were never billed. The result keeps the evidence beside each difference.

If the vendor gives only a total, compare your count with the billed count first. Then ask the vendor for the conversation list so you can compare the same lines.

What the result means

The tool shows each difference with the evidence behind it. It does not approve or reject the invoice. What you do next is your call and depends on your contract.

If every line matches, that is a result too. A clean bill means the vendor's count and your records agree, and you can stop checking by hand. If a line can't be read or could match two rows, the tool says so and leaves it out of the totals. It won't guess.

Send a line-by-line list

Export the findings and send the rows you want to discuss. A shared list of conversation IDs, amounts, dates, and reasons gives both teams the same starting point. It is easier to resolve than two different totals with no shared lines.

Keep customer data out

Your files are processed to produce this result and are not stored. No cell value, amount, or column name is sent to analytics. No account needed.

Remove customer names, email addresses, and message text before you load or share an export. The check needs IDs, amounts, and dates only.

Scope

This process compares two records by a key, an amount, and a date. It does not decide the contract's meaning or what either party should do.

Continue

• Open the Invoice Audit tool.
• Read how AI support vendors count a resolution.
• Read the acceptance lifecycle.