Connect PropServ to MRI Sales & Lettings and let tenants report repairs against the tenancy MRI already knows about. Every report is created as a maintenance action in MRI, and your team looks up MRI tenants and addresses from inside PropServ instead of rekeying them.
into PropServ· into MRI Software· both ways
What it does
For MRI Sales & Lettings agencies who want AI-triaged tenant reporting, a contractor marketplace and automated invoicing, with every report visible in MRI.
When a tenant reports an issue against an MRI tenancy, PropServ creates a maintenance action in MRI with the title, description, date and the tenant's follow-up answers — plus the PropServ report reference.
Browse your MRI tenants inside PropServ and invite them in a click. Their MRI tenancy is linked to their PropServ account, so reports land against the right tenancy.
When your team raises a works request, search MRI by name, email or phone to prefill the property address and client details — no copy-and-paste from MRI.
A tenant with more than one MRI tenancy sees each address when they report, so the issue is filed against the correct property automatically.
Agents see 'This report has been created in MRI' on the report itself, with the action reference, so nobody wonders whether MRI knows.
You create the client credentials in MRI and paste them into PropServ. Tokens refresh automatically and every push is queued and retried.
How it works
The life of one repair once MRI Sales & Lettings and PropServ are connected.
In MRI go to Settings → Integrations → API Framework, add PropServ as a partner, create an OKTA client and grant endpoint access. Note the Client ID, Client Secret and Client Label.
Under Settings → Integrations choose MRI Software and paste the three values. PropServ verifies them with MRI immediately — if they don't work you'll know straight away.
Open the MRI Tenants tab under Team, find the tenant and click Invite to PropServ. Their MRI tenancy IDs travel with the invite, so the link is made the moment they sign up. Tenants who register themselves are matched to MRI by email.
Tenants report by app, web, WhatsApp or a call answered by PropServ VoiceLine, choosing the MRI tenancy address if they have more than one. AI gathers follow-up answers, scores severity and checks photos for mould.
PropServ creates a maintenance action on the tenancy in MRI: 'PropServ: {report title}', the description, the report date and notes carrying the tenant's follow-up answers and the PropServ report reference. If the property isn't in PropServ yet it's created from the MRI tenancy details.
Triage, instruct contractors, approve and invoice in PropServ. MRI holds the maintenance action as the record that the report was raised; PropServ holds the full audit trail of the repair.
What syncs
A precise map of every entity, which way it flows, and what triggers it.
| Data | Direction | When | Notes |
|---|---|---|---|
| Tenants (people) | Into PropServ | On demand | Searched live from MRI to invite tenants and to prefill client details on a works request. Tenancy IDs are linked to the tenant's PropServ account. |
| Tenancies & addresses | Into PropServ | On demand / on report | Tenants see their MRI tenancy addresses when reporting; a PropServ property is created from MRI tenancy details when needed. |
| Maintenance actions | Into MRI Software | Real time | Created in MRI when a tenant report is raised against an MRI tenancy: title, description, date, tenant follow-up answers and the PropServ reference. |
Getting started
If you can create an API client in MRI you can connect PropServ — no developer, no onboarding project.
Settings → Integrations → API Framework → add partner 'PropServ' → Create OKTA Client → Set Endpoint Access → Check All. Note the Client Label.
Settings → Integrations → MRI Software: enter Client ID, Client Secret and Client Label. PropServ verifies the connection with MRI on save.
Open the MRI Tenants tab, invite your tenants, and every report they raise is logged as a maintenance action in MRI.
FAQ
Straight answers on how PropServ and MRI Software work together day to day.
Create an OKTA API client for PropServ in MRI (Settings → Integrations → API Framework), then paste the Client ID, Client Secret and Client Label into PropServ under Settings → Integrations. PropServ tests the connection with MRI as you save.
A maintenance action on the tenancy for each tenant report raised against an MRI tenancy. It carries the report title (prefixed 'PropServ:'), description, date, the tenant's follow-up answers and the PropServ report reference.
Not currently. The action records that the report was raised; quotes, instruction, completion and invoicing are managed and audited in PropServ.
Invite them from the MRI Tenants tab and their tenancy IDs travel with the invite. Tenants who sign up via your generic link are matched to MRI by email address, and agents can adjust tenancy assignments manually at any time.
No bulk import is needed. PropServ reads tenants and tenancies from MRI on demand, and creates a property in PropServ from the MRI tenancy the first time a report needs one.
Not currently. The MRI integration covers tenants, tenancies, addresses and maintenance actions.
More integrations
Every PropServ integration is built and maintained by our own team — pick yours to see exactly what flows where.
Tenant reports become Alto work orders automatically, with status, quotes, works-order PDFs and paid invoices kept up to date in Alto.
How it worksImport Street tenancies in a click; tenant reports auto-create maintenance requests in Street, and works-order and invoice PDFs file against the property.
How it worksSearch Apex27 listings, contacts and tenancies from inside PropServ to prefill works requests and invite tenants and staff — no rekeying.
How it worksSee everything PropServ connects to, what's coming next, and the REST API and webhooks for building your own.