The opportunity
Havenline is 60owner-operated offices, each with its own territory and its own calendar. So an enquiry needs two things at once: an answer now, and a booking in the right office's week. Here is how one agent does both.
The problem
A buyer ready to see a home, a seller weighing their options — they arrive with real intent and meet canned replies, or nobody at all. This is when there is nobody.
The whole agent
Intent is read on every message, not once at the start. Three paths capture and qualify before routing; one answers from your knowledge base; one closes politely and still keeps the capture. Two of them book against a real calendar.
What the visitor sees
Each step puts the decision on screen as something to tap, then takes it back out of the thread once used. The columns are the paths from the chart above — half the components appear on only one of them.
| Component | Buy or rent | Sell | Franchise | FAQ |
|---|---|---|---|---|
| Quick replies | ||||
| Contact form | ||||
| Answer with sources | ||||
| Listing card | ||||
| Office card | ||||
| Franchise team card | ||||
| Time-slot grid | ||||
| Confirmation card |
Tappable options under the agent's message — the opening split, the action inside each path, and the office list when someone wants a different one.
Capture & qualify, inline in the thread and checked there. Nobody is sent to a separate page to fill in a lead form — and this is the step that writes the enquiry to the CRM.
The FAQ path. A written answer with the pages it came from, so a visitor can check it — and so nobody has to trust an unattributed claim about fees or coverage.
The buy path only. Matched from your live feed, then routed straight to the seller or a licensed agent — a buyer never goes near the booking tool.
The sell path. The office whose territory covers their address, with the guide they would meet. The change button means the routing is a suggestion, not a verdict.
Same card, different occupant. A franchise enquiry is not a lead for the office down the road — it goes to the development team, so it is never routed by territory.
Live availability from that office's or team's own calendar, laid out by day. Choosing a time is one tap instead of a round of “does Tuesday work?”.
Who, where, when, and a reference — written to Google Calendar and to the CRM before the visitor sees it. The thing they screenshot instead of ringing the office.
Inside address → franchise
One node of the chart, in full. A network of owner-operated offices has no single calendar to book into, and a lead in the wrong inbox is worse than a slow one. The rules are tried in order.
The territories the network already runs on — one of 60.
No ↓
A lead outside every territory still belongs to somebody.
The office card carries a change button and every office is on the list. Someone moving cities is not an edge case, and the routing is a suggestion rather than a verdict.
A conversation opened on a property page goes to the office holding that listing, wherever the visitor happens to be. The listing already knows whose it is.
The fifth path
An agent that will not admit its limits costs more trust than it saves in staffing.
Not every visitor is a lead, and an agent that will not say so wastes an office's week. Someone outside what you cover is closed politely — and the capture is kept anyway, because “wrong region today” is not “wrong forever”. Alongside that, every path carries a Talk to someone option from the first message, and the agent reaches for it itself when a question falls outside what it should answer — a negotiation, a complaint, anything specific to a deal already in progress. The visitor is handed over with the conversation attached, so nobody starts by being asked to repeat themselves.