Customers
Every buyer, in one profile
From the boutique collector who joined yesterday to the consignor with twenty years of history — one customer record across web, mobile, and the rostrum.
Data domains
Who your customers actually are
The Customer domain is the single source of truth for every buyer your house has registered, whether they came in through the website, the mobile app, an in-person paddle desk, or an absentee form. Each record carries identity (legal name, paddle number, region), verification (KYC status and tier), preferences (categories followed, contactability), and value (lifetime spend, average winning hammer).
Because the same record powers the auctioneer console, the post-sale invoice, and the email engine, you never have to reconcile two views of the same buyer. The MCP server exposes a stable identifier so external AI tools and warehouses can join on it without ambiguity.
Ask your data
From a question to a customer cohort
Pose a strategic question in plain language. The MCP server resolves it against the customer schema and returns the cohort, ranked the way an analyst would have written the query by hand.
Access & governance
Role-scoped from day one
The Customer domain holds the most sensitive data in your house. Access is opt-in at the role level, and personally identifying fields are masked unless the role has the explicit `customers.read.pii` capability.
Default analyst role sees aggregate spend and category preferences only — names and contact details are masked.
Every MCP query against this domain is recorded in an immutable audit log with timestamp, role, and the bounding filter that returned the result set.
Bulk export of more than 100 customer records requires a second-role approval and an exported-row receipt that links back to the requesting query.
Related domains
Customers connect everywhere
Let's talk
Ready to modernize your auction house?
Book a personalised demo and see Auction Rabbit tailored to your sale calendar