Integrations
Property
How the agent handles portal enquiries and works inside the property management systems developers and landlords run.
On this page
A developer or landlord runs two customer conversations. Before the sale, it is enquiries: a buyer sends the same question to several developers, and the first useful reply usually gets the viewing. After the sale, it is a relationship that can run for years: payment milestones, handover, snagging (the defects a buyer reports at handover), maintenance and service charges. Connecting the agent to your property portals and property management systems lets it answer enquiries as they arrive and act on the units, leases, handovers and maintenance requests behind the second conversation.
What connecting your property systems lets the agent do
| Ability | What it means for you | Example |
|---|---|---|
| Answer and qualify portal enquiries | Enquiries arrive as they do today, and the agent replies, answers questions and qualifies the buyer | A Friday evening enquiry answered and a viewing booked before Saturday |
| Answer project and unit questions | Tower, floor, view, completion stage and service charge, from your own data. Configured during implementation | "Unit 1204 faces the marina and is on the twelfth floor" |
| Match requirements to available units | The agent checks live inventory against what the buyer asks for. Configured during implementation | Three available two-bedroom units within the buyer's budget |
| Explain payment plans | Payment structures are retrieved from your systems; the agent cannot construct terms outside them. Configured during implementation | The milestone schedule on a construction-linked plan |
| Log snagging and maintenance requests | Defects and requests are logged against the right unit and tracked. Configured during implementation | A cracked tile logged against unit C-0807 at handover |
| Coordinate handover | Handover appointments and the questions around them. Configured during implementation | A handover inspection booked and confirmed |
Integrations in this category
| Integration | Type | What the connection covers |
|---|---|---|
| Property Finder | Property portal | Enquiries from your listings, handled as they arrive |
| Yardi | Property management system | Units, leases, residents, service charges and maintenance requests |
| MRI Software | Property management system | Units, leases, residents, service charges and maintenance requests |
Regional and in-house property systems connect the same way, as custom actions. See Custom actions.
How the connection works
For portal enquiries, the enquiry reaches the agent through the route agreed during implementation, typically the lead feed your CRM (the system that holds your customer records) already receives. The agent replies in the buyer's language, asks your qualification questions as part of the conversation, and creates or updates the lead in your CRM. Your listings and your portal account stay as they are.
For property management systems, the agent reads unit, lease and resident data during the conversation, and writes the requests your team has agreed it may create, such as a maintenance request or a handover booking. Your property management system stays the system of record for units and leases.
Decisions stay with your team: price negotiation, cancellations and refunds, changes to a payment plan, disputed snagging items and anything heading towards a legal dispute. See Decision boundaries.
The technical detail
Each system connects through its standard API (application programming interface: the documented way other software exchanges data with it) or, for older and in-house systems, another interface agreed with your IT team. The connection uses a dedicated integration account your administrators control, with credentials stored encrypted with AES-256 in your deployment and calls over TLS (Transport Layer Security), version 1.2 or higher. Amounts and dates, such as an instalment or a handover date, are inserted directly from the system record.
Permissions typical for this category
| Permission | Needed for | Default |
|---|---|---|
| Read units, availability and project data | Answering enquiries and unit questions | Granted, limited to the projects in scope |
| Read the customer's lease, payment schedule and service charges | Answering account questions | Granted, after identity checks |
| Create maintenance and snagging requests | Logging defects against the right unit | Granted where in scope |
| Book handover appointments | Handover coordination | Granted where in scope |
| Change prices, payment plans or lease terms | Not needed | Not granted |
The agent can only take actions your team has granted. Anything not granted cannot be invoked. See Permissions.
In practice
Sahel Crest Properties, a Dubai developer, connects its portal enquiries, CRM and property management system.
- An enquiry about a two-bedroom marina-view unit arrives from Property Finder at 9pm on a Friday. The agent replies on WhatsApp, answers the buyer's questions from the project data and books a viewing for Saturday.
- The lead, the qualification answers and the viewing are written to the CRM for the sales team.
- Months later, an owner in the completed tower reports that the balcony door will not lock. The agent confirms his identity, logs a maintenance request against his unit and gives him the reference.
- He then asks for a reduction on his service charge. The agent explains the current charge from the system and hands the request to the customer care team with a brief.
What your team controls
- Which projects, units and records the agent can read.
- Which requests it can create, and which need a person's approval.
- Your qualification questions and payment structures, which the agent follows.
Related
- PropertyIndustry guides
- CRM and ERPIntegrations
- How integrations workIntegrations
- PermissionsIntegrations
- Decision boundariesGovernance and control
Product names and logos are trademarks of their owners. Their mention shows systems Telonic connects to and does not imply partnership or endorsement.