You bring the whole team.
The buyer waits
for one of them.
A buyer enquires on Sunday night after an open home. Somewhere in the largest network in the country there is a salesperson who can answer them, and the buyer hears nothing until Tuesday. This is a concept for those two days: the questions answered from what is already in the file, the price expectation stated only as the vendor agreed it, and a lead that arrives at a salesperson already knowing what it cares about.
“We bring the whole team.”
Ray White New Zealand · their own headline, 30 July 2026The wait between enquiring and hearing a voice
They walked through it at 2pm, talked about it over dinner, and sent the enquiry while the kids were going to bed. Nothing will happen now until an office opens. The three things they asked about are all answerable from the listing file tonight.
Your network is the asset and the enquiry queue is where it stops being one. A buyer cannot tell the difference between a big team and a slow one. The wait is the only part of the journey where scale works against you, and it is the only part nobody has designed.
What happens now
A form receipt, then a callback in the next business day or two, from whoever picks the lead up.
What it costs
The buyer who enquires on four listings on Sunday works with whoever answers first. It is rarely a question of who had the better house.
What the concept does
Answers what the file can answer, says plainly what only the vendor can authorise, and hands a salesperson a lead that has already told them what matters.
Every moment a buyer waits on your team.
Each of these is a moment your customer already spends with you. Each can carry what the phone above shows: watch the work, earn the wait, answer one thing.
Be relevant — right thing, right moment · Be respectful — short, skippable, quiet by design · Be measurable — real impact, on the record · Be Aotearoa — built here, for how Kiwis actually wait
Every wait between “enquire” and a person calling back
Six gaps in a buyer’s week. Each one is a moment they already spend on your listing, and each one currently holds a form receipt.
Four steps, every time.
- The signalSomething in your own systems says a person is now waiting, and roughly how long for.
- The predictionHow long this one will really take — not the average, this one.
- The valueSomething worth their attention goes into that window: an answer, a credit, a thing prepared while they wait.
- The exchangeThey get value. You get a customer who stayed, and one optional answer you have always wanted.
This is the reward layer, running for real on this page. Drag to scratch it. Nothing is collected, nothing is sent — it is here so the idea is something you do, not something you read.
US retailers lose an estimated $37.7 billion a year to customers who abandon because of long queues, split roughly $15.8b to competitors and $21.9b abandoned outright (Adyen with 451 Research). The New York State Department of Labor reported a 48% reduction in hang-ups after introducing virtual queuing. Theme parks moving to virtual queues reported a 36% lift in per-capita spending, because guests spent the wait somewhere that sold something. A Seattle-Tacoma Airport study found 63% of passengers said they shopped or ate more because they saved time in the security queue.
Every figure on this page carries its source. Overseas figures are shown as overseas figures — we have not found a published New Zealand equivalent, and we will not invent one.
undefined
undefined
A template sends the same thing to everyone and changes the name. What matters here is the case that should get something different — or nothing at all.
The rules beside each draft are placeholders. A pilot replaces them with your actual policies. We have not seen those, and this concept does not guess at them.
A buyer asks what it is worth. What may it say?
Real estate has the most specific conduct rules of any category in this fleet, and an AI in a listing journey lands on five of them immediately. Every rule below is quoted from the Real Estate Agents Act (Professional Conduct and Client Care) Rules 2012. Three of these come back as a refusal.
These are real rules, and this is an independent concept. Ray White New Zealand has not commissioned, reviewed or endorsed it. Sources: Real Estate Agents Act (Professional Conduct and Client Care) Rules 2012, rules 6.4, 9.4, 10.2, 10.7, 10.9 and 10.12 · rea.govt.nz. Anti-Money Laundering and Countering Financing of Terrorism Act 2009 has applied to real estate agents since 1 January 2019.
What it refuses to say
Every refusal here traces to a rule a licensee is already accountable under. The concept is safer than a person having a fast conversation, because it cannot be talked into a number.
Drafts are held against Real Estate Agents Act 2008 and the Professional Conduct and Client Care Rules 2012, the Fair Trading Act 1986, the Privacy Act 2020, and the AML/CFT Act 2009.
Press run to see what it catches — and what it refuses to produce at all.
One room. Your people, your agents, every action on the record.
Every concept on this page would run inside a private room like this: your team and the agents in the same space, drafts appearing with receipts, a named person saying yes. It runs on infrastructure you approve — and what is said in the room stays in it.
receipt sources: your rate card · rules: yours · held for approval
Client information stays in your room. Six months later, “where did this come from?” is one line, not a search.
Yours
Runs where you approve — your own room, your own record. Nothing in it leaves it.
On the record
Every agent action lands as a line a person can read — not a log only a vendor can open.
People decide
Drafts wait for a named person. The room shows who said yes, and when.
This panel is a concept picture, not a live room — a pilot stands up the real one, on infrastructure you approve.
undefined
Illustrative and fictional. No production access is requested by this concept.
| Enquiry | What they asked | Answered from | Waiting on | Status |
|---|---|---|---|---|
| Sunday, after an open home | Chattels, school zone, heating | The listing file and the LIM | Nobody — it closes itself | Answered in full from documents already on the listing. |
| Price expectation | What the vendor wants | The vendor’s written agreement | Nobody, where it is agreed | States it as the vendor put it, and says so. |
| Price, not agreed | What the vendor wants | Nothing — it will not estimate | A licensee | Held. Rule 9.4 makes a guess here a breach. |
| A defect the buyer noticed | Is that crack structural | Known defects on file | A licensee, same day | Discloses what is known and refuses to assess what is not. Rule 10.7. |
| An appraisal request | What is my place worth | Comparable sales, assembled | A licensee to write it | Never produces the number. Rule 10.2(a). |
undefined
Every draft carries its own working.
Not a log somebody has to go and find. The provenance travels with the work — what it read, which rules it held, who must approve it, and what it refused to do.
This matters most on the day someone asks why it said what it said.
- Artefact
- a signed record of what was answered, which document each answer came from, and which salesperson approved it
- Read
- undefined
- Rules held
- undefined
- Refused
- undefined
- Approver
- A named person. Unsent until then.
- Prepared
- —
- Reference
- —
Why this concept, for Ray White, now.
Nothing on this page is modelled, projected or borrowed from a slide. These are your own published facts, and the concept above is built on them.
The same evidence, on one page you can print or send: the one-pager →
What this will never do
It does not send. It prepares, and a named person sends. It does not publish to any channel, commit spend, move money, or make a decision that belongs to a person. It does not pretend to be a person — every draft says it was prepared by a machine and approved by a human.
No production access is requested by this concept.
Scope
One enquiry type on one office’s listings, for six weeks: the after-hours buyer enquiry. Not appraisals, not vendor communications, not the CRM.
Access
Read-only access to the listing documents that office already publishes, and the vendor’s written price agreement where one exists. No buyer data leaves your environment and nothing writes to a listing.
Scorecard
Drafts a salesperson sends without rewriting. Time from enquiry to a real answer against a control office. Whether buyers said they knew where they stood. And: would that salesperson be annoyed if you switched it off?
Fail any line of the scorecard and we change the design or stop.
What a pilot actually asks of you.
Written out in full, because the honest version of this is short and most of it is your time, not your money.
One named person
The approver. Every draft stops with them and nothing reaches a customer until they say so. Expect about two hours a week — reading drafts, not managing a project.
One situation, not the business
One enquiry type on one office’s listings, for six weeks: the after-hours buyer enquiry. Not appraisals, not vendor communications, not the CRM.
Read-only access, nothing that writes
Read-only access to the listing documents that office already publishes, and the vendor’s written price agreement where one exists. No buyer data leaves your environment and nothing writes to a listing. No production credentials, no write permissions, no access to anything the pilot does not need.
Your actual rules
The policies, limits and words the drafts must be held against. Every rule on this page is a placeholder standing in for yours. An afternoon with whoever owns them is usually enough.
Six weeks, then a real decision
Scored on: Drafts a salesperson sends without rewriting. Time from enquiry to a real answer against a control office. Whether buyers said they knew where they stood. And: would that salesperson be annoyed if you switched it off? Fail any line of that and we change the design or stop. You keep everything drafted either way.
A fixed fee, agreed in writing first
No number is published on this page, because it depends on which situation you pick. Whatever it is, it is agreed before any work starts and it does not move.
Run the pilot.
Say yes to the six weeks above, and add anything you would change first. Nothing here is fixed — most pilots move a line or two before they start, and the notes below are how that happens.
Opens your mail app to assembl@assembl.co.nz with your notes in it. Nothing is collected by this page.
- Six weeks, one situation, scored against a written line
- Read-only access, nothing production
- A named approver — nothing sends without them
- A fixed fee, agreed in writing before anything starts
- Stop any time. You keep what was drafted
Pick a verb.
Not “book a demo”. Any of these is a real next step, and the last one is a perfectly good answer.
What is the one constraint we have got wrong?
Every concept is built from the outside. There is always something about how Ray White actually runs that we could not see. One line is enough.
Opens your mail app to assembl@assembl.co.nz. Nothing is collected by this page.