Where inquiries come from
| Visitor action | Creates |
|---|---|
| "Ask a question" on a listing | an inquiry (INQUIRY, code IQ-XXXX-XXXX) linked to the listing |
| "Request a viewing" on a listing | an inquiry (VIEWING, code VW-...) and a viewing with status REQUESTED on the requested date and time |
| The contact page | a general inquiry without a listing |
The visitor gets the code on screen. Viewing requests accept dates from today up to 60 days ahead, between 08:00 and 20:00 in the agency's time zone. Each IP can send 5 requests per minute.
Assignment
New inquiries and viewings go to the listing's agent. General inquiries (and listings without an agent) wait as "Not assigned" until an admin assigns them. Agents see only what is assigned to them. Reassigning an inquiry also moves its open viewings to the new agent.
The inquiry pipeline
NEW ──> CONTACTED ──> QUALIFIED ──> WON
│ │ ^ │
│ │ └──────────┘ (buyer went quiet)
└──────────┴──────────────┴──> LOST ──> NEW / CONTACTED (reopened)
WON is final. Every change of status or agent is written to the inquiry's notes with the person and time, next to the notes the team adds.
Viewings
REQUESTED ──> CONFIRMED ──> DONE
│ ├──> NO_SHOW ──> REQUESTED / CONFIRMED (rebooked)
└────────────┴──> CANCELLED ──> REQUESTED / CONFIRMED
The Viewings page shows a week calendar (today highlighted) or a list from 30 days ago. Click a viewing to confirm it, mark it done or no-show, cancel it, move it to another date or time, leave a note, or (admins) give it to another agent. Changes are logged on the inquiry.
Staff can also book a viewing from an inquiry (Inquiries > Book viewing) for a phone call or a walk-in.
Notifications
Dar does not send emails or WhatsApp messages by itself: the dashboard is the inbox. To be notified, add a call to your provider in createInquiry() and createViewing() in src/lib/leads.ts.
API
Public: POST /api/inquiries, POST /api/viewings. Dashboard: /api/dashboard/leads... and /api/dashboard/viewings.... See API reference.