MILabs
Integrations

Tenant portal with Reapit for property managers

How a tenant portal can sit beside Reapit records, so requests, status updates and notices reach staff and residents with less repeat work.

Updated 2026-05-31

Tenant portal with Reapit

Reapit holds the property, tenancy and contact records that a lettings team relies on, but tenants usually reach the business by email, phone or a listing site rather than through the platform itself. A tenant portal gives residents one place to log a maintenance request, check its status and read notices, and gives staff a single queue to work from. Linking the two means each request can be matched to the right property and tenancy without someone retyping details. The portal would keep Reapit as the system of record. Staff would still confirm tenancy details, approve any reply that touches rent or legal notices, and decide on repairs. Whether the link can read and write the fields you need depends on the access your administrator grants through Reapit's API, so that check comes first. Where it works, the portal can reduce repeated questions about inspection dates and job progress, and each request stays linked to its tenancy.

How it works

  1. Confirm which Reapit objects the portal needs to read, such as properties, tenancies and contacts, and which it may write to, using the API scopes your administrator sets.

  2. Build the tenant login and maintenance request form, then match each submission to a property and tenancy record in Reapit before it reaches staff.

  3. Route each new request into a staff queue that shows the tenancy history alongside the photos and urgency field.

  4. Let a model suggest a reply from your approved answer library, and keep a person responsible for approving it before the tenant sees it.

  5. Write status changes and notices back to the matching Reapit record only where the access allows, and keep a log of each change for the team.

good questions, straight answers

Frequently asked questions

What does a tenant portal not do with Reapit?
A tenant portal does not replace Reapit as the system of record, and it does not make decisions about rent, legal notices, valuations or repairs. Those stay with qualified staff who check the Reapit record before they act. The portal also cannot change anything your account does not expose to it, so write access depends on the permissions your administrator sets.
Which tools sit between a tenant portal and Reapit?
The link is usually a small integration layer. Zapier, Make, n8n and Power Automate can each move data between a web form and an API, and a custom build can call Reapit's API directly. A model such as Claude could draft replies for staff, while Supabase could store portal accounts and request history.
Is a tenant portal right for a small Reapit team?
Yes, when the team handles enough repeated requests that a shared queue would save time. A very small team with few tenancies may find that a shared inbox and a clear answer library cover most of the need, and the portal can wait. Ask whether the requests arrive often enough to justify the setup and ongoing upkeep, and whether staff have time to review what the portal sends. The answer depends on your own volume, which only your records can show.
Does a tenant portal change how my team uses Reapit?
Some habits would shift. Requests that once arrived by email or phone would land in the portal first, so staff would check that queue and then confirm the matching tenancy in Reapit. Notices and status updates would be written back to the record instead of sent from a separate inbox. Training would cover the new queue and the approval step, and the team would need agreed rules for who answers what.
How do I measure a tenant portal on Reapit?
Start with a baseline before launch. Record the repeated enquiries, the time to first staff response and the calls about job status. Repeat the same counts afterwards and compare. Also track how many portal requests need correcting in Reapit, since that shows whether the matching rules are working. Choose measures that matter to your team, and set no targets until the baseline is clear.
let's make something happen

Custom development: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.