Integrations
Yardi
How your agents read units and leases in Yardi, log maintenance requests and tell residents where their request has got to.
On this page
If you run your portfolio on Yardi's property management software, your agents can work with the records your team already keeps there: units, leases, residents and maintenance requests. A resident who reports a fault is heard, identified and logged against the right unit in one conversation. When they ask what is happening, the agent reads the request and tells them. The connection is configured during implementation for the Yardi products and records you use.
What the connection lets the agent do
| Action | What it means for you | Example |
|---|---|---|
| Look up unit and lease details | Answers about a resident's own unit and lease come from your records | A tenant asks when their lease ends and hears the date from Yardi |
| Log a maintenance request | Faults and defects are recorded against the right unit, with the details your team needs | A leaking bathroom tap logged against apartment 1204, with a photo from WhatsApp attached |
| Log snagging items after handover | New owners' defect reports are captured in full and tracked, rather than lost in an inbox | Three snagging items from a handover inspection, each logged separately |
| Read request status | Residents hear progress on their request without calling the management office | "A technician is booked for tomorrow between 9am and 12pm" |
How it connects
The agent connects through the interfaces available to your Yardi environment (the documented ways other software exchanges data with Yardi), which depend on the Yardi products your organisation licenses and how they are hosted. The route is agreed with your Yardi administrators during implementation, using a dedicated integration account they create and control.
The credentials are stored encrypted in your deployment, and every call travels over TLS (Transport Layer Security, the standard encryption for data in transit) version 1.2 or higher. The connection runs from your deployment in your chosen region. Which properties, request categories and fields the agent uses is mapped with your team, so requests arrive where your maintenance team already works. See How a system gets connected.
Permissions
| Permission | Needed for | Default |
|---|---|---|
| Read units, residents and leases | Answering questions about a resident's own unit and lease | Only for the properties you name, after the identity check set for your deployment |
| Create maintenance requests | Logging faults, defects and snagging items | Only the categories you choose |
| Read maintenance request status | Telling residents about progress | Granted for requests the agent can read |
| Change leases, rents or charges | Not needed | Not requested |
The agent can only take actions your team has granted. Anything not granted cannot be invoked. Every lookup and request is logged in the audit trail. See Permissions.
In practice
Sahel Crest Properties manages a completed tower in Dubai on Yardi.
- On a Friday evening, Aisha messages on WhatsApp that her air conditioning has stopped cooling.
- The agent confirms who she is and her unit, asks when it started and whether any other room is affected, and asks for a photo of the thermostat.
- It logs a maintenance request in Yardi against her unit, with her description and the photo, and gives her the reference.
- On Saturday, she asks when someone is coming. The agent reads the request and tells her the technician's time slot.
What your team controls
- Which properties and request categories the agent can work with.
- Which requests are urgent enough to go straight to a person, such as a leak or a lift fault.
- What a resident is told about each request status.
Related
- Property integrationsIntegrations
- PropertyIndustry guides
- PermissionsIntegrations
- How a system gets connectedIntegrations
- Commitments and promise trackingCustomer record
Product names and logos are trademarks of their owners. Their mention shows systems Telonic connects to and does not imply partnership or endorsement.