AI Connector
Ask once. Keep the report.
Every auction house has questions its standard statistics do not answer. Ask your AI assistant one of them, check the answer, and keep it: the report then sits in your back office, runs on current figures whenever anyone opens it, and exports to Excel.
The question that used to cost a week
“Can you give me the hammer total per category for last year?” “Which consignors brought in more than ten lots and sold fewer than half?” “How many bidders from Germany actually bid, not just registered?”
Today those questions travel by e-mail. Someone writes a query, sends a spreadsheet back, and the answer is correct for exactly one day. Six months later the same question is asked again, and nobody can find the spreadsheet, or the person who made it.
With the Auction Experts AI Connector you ask the question yourself, and you decide what happens to it. Some answers you need once. Some you need every month — those you keep.
How it works
1. Ask
Describe what you want in your own words: “hammer total per category, per month, for this year”. No report builder, no drag-and-drop, no SQL.
2. Check
Your assistant shows the figures and explains, in a plain sentence, what it counted — for example “the hammer price of sold lots, grouped by main category, for auctions that closed this year”. If that is not what you meant, say so and it tries again.
3. Keep it — or don’t
If it was a one-off, take the answer and move on. If you will want it again, give it a name and save it. From that moment it is a report in your back office.
4. Run it whenever you like
Anyone in your auction house opens it, fills in the period or the auction if the report asks for one, and gets today’s figures. Export to Excel when you need to send it on.
What people actually save
A saved report is worth having when the question comes back. These are the kinds that do:
| Report | Why it gets saved |
|---|---|
| Sell-through and average hammer per category, per month | The figure that tells you what to take in more of |
| Lots still awaiting the consignor’s decision, with their age | The work that quietly gets forgotten after a sale |
| Buyer’s premium as a percentage of hammer, per auction | Shows at a glance where an exception or a cap is costing you |
| Consignors who brought in lots this year, with what their lots made | The conversation before the next intake |
| Bidders per country who bid, not just registered | Where your marketing actually landed |
| Unsold lots with bids above a given amount | The after-sale list that is worth a phone call |
| Texts and e-mail templates still missing in a language | The housekeeping nobody sees until a buyer does |
None of these are built into the platform as fixed reports, and they do not have to be. Your questions are not the same as another auction house’s.
What is stored, and what is not
The instruction, not the numbers
A saved report holds the query and your original question — never a frozen copy of the figures. A report about this year keeps counting up as the year runs; a report about last year gives the same answer every time, because the data did.
Your own words, kept next to it
The question you asked is stored with the report. It documents what the report means for the next person, and if the platform ever changes underneath it, your assistant can rebuild the report from it instead of you having to describe it again.
Reports ask for what they need
A report can take a period, an auction or a category, so one report answers this month, last month and last year. Ask for “this year” and it stays current by itself.
Shared, not personal
A report belongs to the auction house, not to the person who made it. One colleague builds it, everyone uses it, and it survives a holiday, a handover and a change of staff. That is the point: the knowledge of how to ask a question stops being one person’s.
How it is contained
A report can only see what the connector sees.
The same boundary
A saved report runs with the AI Connector’s own read access — the curated set of auction information, and nothing else. It cannot reach another auction house, and it cannot reach parts of your own system the connector does not expose.
Personal data stays masked
E-mail addresses and phone numbers are masked in a report, exactly as they are in an answer. Secret settings are not there at all.
Reading only
A report reads. It cannot change a lot, an auction or an invoice, whoever runs it.
It has to finish
A report is checked before it is saved and has a time limit when it runs, so a heavy question cannot sit on your database during a sale.
Frequently asked questions
Do I need to know SQL to build a report?
No. You describe what you want in your own words. Your assistant works out the query, shows you the result, and saves it only once you are satisfied.
Does a saved report freeze the numbers?
No. What is stored is the instruction, not the numbers. Every run reads your data as it is at that moment, so a report on the current year keeps counting up.
Who can run a saved report?
Anyone in your auction house. Reports are shared: one person builds it, the rest use it, and it is there long after the conversation that produced it.
Can a report be changed later?
Yes. Ask your assistant to adjust it — another column, another period, a different grouping — check the result, and save it again.
What happens to a report if the platform changes?
The question is stored next to the query, in your own words, so your assistant can rebuild the report rather than you having to describe it again.
Can a report show my bidders’ e-mail addresses?
No. A report reads exactly what the AI Connector reads, so e-mail addresses and phone numbers are masked and secret settings are not in it at all.