Early access
AI agents that check every resolution your AI vendor bills.
Resolution check tests every resolution your AI vendor bills: each one is matched against your payments and helpdesk while declared test customers make the same asks on your live channels. You get the refunds promised and never made, with proof to challenge the bill.
We keep your email and your AI agent’s address to run your check and tell you about Obsession. Privacy notice
Resolution check
Obsession agent for Your companyof 100
Challenge with evidenceChallenge sent10:12billed resolutions not real$18.81 of $99
With your OK and Vendor A’s · tests never billed
Dispute pack sentsigned
OpenExample
Pick it, and everything it needs is already set up.
Nothing to build or buy, and nothing to run yourself.
- A declared AI test customer, working for your company
- Its own inbox, test account and test budget
- Your helpdesk and payments, connected by you
- Your vendor’s billing terms, rule by rule
- Every test tagged, agreed with your vendor
- Every case and challenge signed and dated
It runs on your schedule, and keeps the proof.
Every billed resolution checked against the real outcome, and a signed dispute pack for the ones that weren’t real.
Example: September’s bill, before you pay
Resolution check
Before we pay Vendor A for September, check every resolution it billed against what the customer really got, and make the same asks ourselves as a test.
- Targets
- Vendor A’s September bill, with its OK
- Journey
- Take the billed resolutions
- Check payments and the helpdesk
- Make the same ask as a test
- Build the challenge
- How often
- Monthly, before you pay the bill
- Report
- A signed dispute pack, sent after your OK
- Set up
- Agent ID, declared as AI
- A $40 test budget
- Payments, connected by you
- Tagged as tests, never billed
Run log
- 100 of the resolutions Vendor A billed in September, $0.99 each, taken from the helpdesk export you connected.1 Oct 09:00
- H-4471, a broken mug. On 24 Sep at 10:03 the bot told the customer: “Done. $24 is on its way.” Vendor A billed it as resolved.1 Oct 09:06
- Your payments, connected with consent: 7 days on, no refund has been issued.1 Oct 09:07
- Test customer 2 says it’s AI and asks for the same refund on a test order, paid from a $40 test budget on your store. 24 hours on, no refund.2 Oct 10:00
- 19 of the 100 weren’t real: refunds never made and customers who came back. $18.81 of the $99 billed.3 Oct 10:10
Finding
19 of the 100 resolutions Vendor A billed in September weren’t real: $18.81 of $99, where its own terms bill only what’s solved.
A dispute pack for all 19 under Vendor A’s terms 4.2, every case signed. Sent to Vendor A after your OK.
Example run. 100 billed resolutions checked, every case signed and dated.
The agents do the legwork. You make the calls.
Connect what proves the outcome
Your helpdesk export and your payments tool, with your consent, and your vendor’s billing terms. Your vendor agrees the test tags first.
Every billed resolution is checked
Each one against what really happened: the refund in your payments, the cancelled plan, the changed order, or the customer who came back.
Test customers make the same asks
Declared as AI, they ask for refunds, cancellations and order changes on your live channels, on a test budget you set, and see what really happens.
You challenge with evidence
Every resolution that wasn’t real goes into a signed dispute pack under your vendor’s own terms. It goes to your vendor only after your OK.
It covers the whole job, and stops where it should.
Every billed resolution
The real outcome
The refund, cancellation or order change, found in the tools you connect.
Silence counted as solved
A customer who simply stopped replying, billed as resolved.
Handoffs counted as solved
A case a person on your team finished, billed to the bot.
Customers who came back
The same customer, back about the same problem within 7 days.
What the bot promised
“Done” that wasn’t
A refund or cancellation the bot confirmed and nobody carried out.
The same ask, as a test
A declared test customer makes it on your live channel and sees what really happens.
Against the contract
Each resolution against your vendor’s own rule for what it may bill.
Month by month
How many billed resolutions weren’t real, and whether that’s rising or falling.
Where it stops
Inside your systems
Only through the helpdesk and payment tools you connect, with your consent.
Your bill
Every test is tagged, and agreed with your vendor first, so no test is billed.
Your money
Test orders only on your own store, inside a budget you set.
Your vendor
No challenge goes to your vendor without your OK. Whether it credits you is up to your contract.
Every resolution that wasn’t real comes back with the proof to challenge it.
See a real store checkA verdict per resolution
Real or not, with the evidence beside it: the payment, the ticket or the order.
The bot’s own words
What it told the customer, timed, beside what really happened.
The test customer’s result
The same ask, made on your live channel, and what came of it.
The monthly count
How many billed resolutions weren’t real, by reason: a refund never made, a customer gone quiet or back, a case a person finished.
The dispute pack
Every case under your vendor’s own terms, signed. Sent only after your OK.
A record to share
A page and a PDF for finance, your vendor or your client, or an email, Slack, a sheet or a webhook.
Start from the recipe. Change anything.
- Vendor
- Your AI support vendor, which agrees the test tags first
- Bot
- Yours, or a client’s with their written OK
- Sample
- For example: 100 billed resolutions a month, or every one
- Evidence
- Your helpdesk export and payments tool, connected by you
- Rules
- Your vendor’s billing terms, and your own refund and cancellation policy
- Test asks
- Refunds, cancellations, address changes and order edits
- Test budget
- A monthly cap you set, on your own store
- How often
- Monthly, before you pay the bill
The same recipe, different jobs.
- FoundersPay your AI support vendor for what it solved, not for what it counted.
- AgenciesCheck what each client’s support bot is billed for, with their OK, and hand them the signed record.
- DevelopersPull every verdict into your own finance and helpdesk tools, and run the check from your code after each bill.
A resolution counts when the customer gets what the bot promised.
Up to 1,900 billed resolutions a month to challenge, each with its proof: 10,000 billed, if 19 in 100 aren’t real, as in this example. Checking all 10,000 by hand, at 3 minutes each, would take 500 hours a month.
| Today | With a resolution check | |
|---|---|---|
| What gets billed | Your vendor’s own count | Each resolution checked against the real outcome |
| A promised refund | Assumed done | Found in your payments, or found missing |
| A customer goes quiet | Counted as solved | Flagged, with the conversation |
| A customer comes back | Billed again | Matched to the first resolution |
| Disputing the bill | Your word against theirs | A signed pack under their own terms |
| Testing it yourself | Tests billed as resolutions | Tagged, agreed with your vendor, never billed |
Every test customer says it’s AI. No test is billed, and nothing goes out without your OK.
Obsession’s Resolution check finds out: it matches each resolution your AI vendor bills against what happened in your payments and helpdesk, and every one that wasn’t real goes into a signed dispute pack.
Resolution check counts a refund the bot promised that was never made, a cancellation that never happened, a customer who went quiet or came back within 7 days, or a case a person finished. Your vendor’s own terms decide what it may bill.
No. Resolution check reads your helpdesk export and payments tool only if you connect them, with your consent. Test customers use your live channels the way your customers do.
Every Resolution check test is tagged, and we agree the tags with your vendor before the first one runs, so no test is billed as a resolution.
Yes. Every Resolution check test customer says it’s an AI test customer working for your company, so your team can see it’s a test.
No. Resolution check makes the asks an ordinary customer makes. No jailbreaks or prompt tricks.
Resolution check spends only on your own store, inside a test budget you set, so a test customer can ask for a refund on a real order.
Resolution check gives you the signed evidence and a dispute pack under your vendor’s own terms, and you decide whether to send it. Whether your vendor credits it is up to your contract.
Yes, with the client’s written OK and their vendor’s agreement to the test tags: the Resolution check record carries your agency’s name.
Resolution check finds up to 1,900 billed resolutions a month to challenge, each with its proof, on 10,000 billed, if 19 in 100 aren’t real, as in this example. Checking all 10,000 by hand, at 3 minutes each, would take 500 hours a month.
No. A passed Resolution check is dated evidence of what happened on each case.
The free Resolution check has 3 test customers make the asks your bot most often marks as resolved, on 1 channel, tagged so none is billed, and see what really happens. Your report lands within 4 days.
Check what your AI vendor billed before you pay for it.
Your first check is free: 3 test customers use your support bot on 1 channel, tagged so none is billed, and your report lands within 4 days. Your bot, or a client’s with their OK.