Integrations
MRI Software
How your agents read units and leases in MRI Software, log maintenance requests and tell residents and tenants where their request has got to.
On this page
If you manage residential or commercial property on MRI Software, your agents can work with the records your team already keeps there: units, leases, occupants and maintenance requests. A tenant who reports a problem is identified and the request is 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 MRI 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 tenant's own unit and lease come from your records | A tenant asks which parking bays are included in their lease |
| Log a maintenance request | Faults are recorded against the right unit, with the details your team needs | A broken gate barrier at a compound logged with its location and when it failed |
| Log defects after handover | New owners' defect reports are captured in full and tracked to resolution | A cracked tile and a sticking door logged as two separate items |
| Read request status | Tenants hear progress on their request without calling the management office | "Your request is assigned and a contractor is due on Tuesday" |
How it connects
The agent connects through the interfaces available to your MRI environment (the documented ways other software exchanges data with MRI Software), which depend on the MRI products your organisation licenses and how they are hosted. The route is agreed with your MRI 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. See How a system gets connected.
Permissions
| Permission | Needed for | Default |
|---|---|---|
| Read units, occupants and leases | Answering questions about a tenant's own unit and lease | Only for the properties you name, after the identity check set for your deployment |
| Create maintenance requests | Logging faults and defects | Only the categories you choose |
| Read maintenance request status | Telling tenants 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
A property manager in Riyadh runs its residential compounds on MRI Software.
- Tariq calls at 8am to say the gate barrier at his compound will not open.
- The agent confirms who he is and which compound he lives in, asks which gate and whether residents can get in and out, and logs an urgent request in MRI Software.
- Because residents cannot leave by car, the agent also alerts the duty facilities supervisor, as the manager's escalation rules require.
- At noon, Tariq asks for an update on WhatsApp. The agent reads the request and tells him a contractor is on site.
What your team controls
- Which properties and request categories the agent can work with.
- Which requests go straight to a person as well as being logged.
- What a tenant is told about each request status.
Related
- Property integrationsIntegrations
- PropertyIndustry guides
- PermissionsIntegrations
- How a system gets connectedIntegrations
- Service desk and ticketingIntegrations
Product names and logos are trademarks of their owners. Their mention shows systems Telonic connects to and does not imply partnership or endorsement.