Esta página está disponible en inglés.
Property
From first enquiry to handover, and every call after.
Agents that know a unit from a payment milestone answer buyers and owners on WhatsApp, calls and email, and do the work in your systems.
Agent at work: the agent handles a WhatsApp enquiry about unit B-1402, then a call about an instalment for C-0807, checking your systems and rules at each step.
Your rules: the agent’s configuration, built with your team. Payment plans come from your property system, some decisions stay with your team, and the agent can only do what you permit.
What you see: the Overview shows conversations by hour with evening and weekend peaks, the top reasons for contact, the four agents and what was handed to your team today. Insights shows quality against your standard and two recommendations.
- A buyer asks about a unit at 22:40
- The agent checks the listing and live availability
- Price questions are routed to your sales team
- The lead is written to your CRM
- A second buyer asks about her next instalment
- Plan rules decide what the agent can offer
- A payment link sent, or your collections team
- Your rules, set up with your team
- Payment plans come from your system
- Some decisions always stay with people
- The agent can only do what you permit
- Peaks after 9pm and at weekends: when your team isn’t there
- The top reasons buyers get in touch
- Four agents, and what each resolved today
- What reached your team today, and why
- Every conversation scored against your standard
- Where a process keeps causing calls
Every enquiry answered. Nobody asked to start again.
Buyers and owners get the same standard of answer at any hour, from your own systems, and your team gets the conversations that need a person, with the history attached.
Salesforce, State of the Connected Customer, 2023
56% of customers often repeat themselves to different people
Salesforce, State of the Connected Customer, 2023
55% feel they deal with separate departments, not one company
Zendesk, CX Trends Report 2025
63% would switch after one bad experience
Works with the systems property teams run
Don’t see your system?
Many developers run in-house sales and handover systems. If yours exposes an interface, the agent can act on it, and we build that connection during implementation.
See every integrationLogos are trademarks of their owners. Their use shows systems our agents can connect to and does not imply partnership or endorsement.
Launch weekends flood the line. Handover season floods it again.
Where property conversations go wrong
Enquiries go cold overnight
A buyer who messages at 11pm about a unit they saw on a portal has usually asked two other developers by morning.
Payment questions queue behind sales
Instalment and milestone questions wait in the same queue as new enquiries, and buyers call again when nobody answers.
Snags fall between teams
A defect reported to sales, then to handover, then to facilities, is logged three times or not at all.
Built around how a property business runs
Three jobs that decide whether buyers trust you: answering enquiries, keeping payments on schedule, and getting handover right.
Layla Haddad messages at 22:40 from a Property Finder listing. The agent checks the listing, the live unit, her budget and Karim’s calendar, books a viewing for Saturday at 11:00 and records the lead in your CRM. When she asks about a cash discount, pricing stays with your sales team and Karim receives a brief.
- A buyer messages at 22:40 from a portal listing
- Checks the listing and the live unit
- Qualifies the buyer in the conversation
- Books the viewing in your sales calendar
- Records the lead in your CRM
- Pricing stays with your sales team
- Karim gets the brief, not a cold lead
Sales and enquiries
Every enquiry answered while the buyer is still interested
Portal and WhatsApp enquiries, at any hour
A buyer who messages at 11pm from a listing gets an answer about the actual unit, not a form.
Qualified against your criteria
Budget, timing and whether they’re buying to live in or invest, asked in the conversation.
Viewings booked with the right person
Slots come from your sales calendar, and the lead lands in your CRM with a summary.
Instalment 5 for C-0807 falls due after the 60% milestone. The agent checks consent and sending hours, sends a WhatsApp reminder, explains that the plan does not allow splitting, and the buyer pays by link, so the collections table shows C-0807 as paid. A restructuring request for B-0915 goes to your collections team with a brief, and the week’s totals follow.
- The milestone is reached in your system
- Checks consent and sending hours
- The reminder goes out on WhatsApp
- Plan rules decide what the agent can offer
- Paid by link, recorded in your system
- Restructuring goes to your collections team
- This week, at a glance
Payments and collections
Buyers kept on schedule, without chasing them
Reminders from your payment plan
Sent before each instalment to buyers who’ve opted in, within the hours you set.
Plans explained from your system
Construction-linked plans included, with the next instalment tied to its milestone.
Exceptions go to collections
Requests to split or restructure a payment arrive with a brief, for your team to decide.
The owner of B-1204 reports a kitchen cabinet door that won’t close, with a photo. The agent checks the unit and its warranty, logs ticket SD-30418 with the photo, books a contractor for Tuesday at 10:00 and confirms the owner. A week later the owner disputes the repair, and the handover team receives a brief with the full history.
- An owner reports a snag with a photo
- Checks the unit and its warranty
- Logs it in your service desk with the photo
- Books the contractor and confirms the owner
- A dispute goes to your handover team
- With the whole history, so nobody starts again
Handover and owner services
Every snag logged against the right unit
Handover appointments from the milestone
Booked as soon as the unit is ready, with reminders before the day.
Snags reported with photos
Logged against the unit in your service desk, and a contractor visit booked.
Disputes go to your handover team
With the full history attached, so the owner never starts again.
Your property agent, at work
Four situations every developer knows, from a launch weekend to the monthly report. Watch what the agent does, and what it hands to your team.
Saturday at 10:02, three buyers message at once: Hamdan Al Qasimi, Aisha Rahman and Daniel Okafor. The agent answers each from live availability and books their viewings, spreads the day’s bookings across Karim, Lina, Faisal and Noura, and hands five items to the sales team with briefs. Only then does the day’s summary appear: 348 conversations, 96 viewings booked and 5 handed to your team.
Rashid Al Mansoori, owner of B-1204, asks in Arabic for his service charge statement and a new access card, and in English about a leaking tap. The agent finds him, sends the statement, books the card collection for Thursday at 14:00, logs the leak as SD-30561 and books a contractor for Monday at 09:00. Everything lands on his record, and he is confirmed on WhatsApp.
Three portal leads have gone quiet. The agent checks consent and calling hours: Hassan Rizvi has not given consent and is not contacted. Hamza Khalil is called within your hours, books a viewing for Sunday at 16:00 with Karim, the CRM is updated, he is confirmed on WhatsApp and moves to Viewing booked.
The September insights show the top reasons for contact and what was resolved without your team. The agent writes the summary in plain English, finds a recurring cause (payment-date questions spike after statements are sent, because the statement does not show the next milestone) and recommends adding the next milestone date to the statement, then posts it to your leadership channel.
- Saturday, 10:02: three buyers at once
- Each one answered from live availability
- Viewings spread across your sales team
- The rest handed over with a brief
- Saturday, summed up
- An owner writes in Arabic and English
- Finds the owner and the unit
- Sends the statement and books the card collection
- The leak is logged and a contractor booked
- Everything lands on the owner’s record
- Confirmed to the owner, in their language
- Three portal leads have gone quiet
- Checks consent and calling hours first
- No consent: not contacted
- Calls Hamza within your hours
- Books the viewing and updates your CRM
- Confirms on WhatsApp
- Hamza moves to Viewing booked
- The top reasons buyers and owners got in touch
- Resolved without your team, by channel
- Written in plain English for your leadership
- The recurring cause, found across conversations
- And the change that would fix it
- Posted to your leadership channel
- Where a process keeps causing calls
Research and innovation
Agents that hold up in real conversations don't come from a model release. They come from sustained research into how an industry works, how its customers behave and what the technology can reliably do. We do that work so your team doesn't have to, and every deployment starts from it.