AI for property managers, across tenants, landlords and rent

A managing agent fields the same questions all day, and the answers sit in different systems: the tenancy in DocuSign, the rent in GoCardless or the ledger, the repair request in an inbox, the inspection in a calendar. Memtro connects to those systems and answers across them, with every figure cited to the payment, email or document it came from, so a question about a property is answered without a search through five tabs.

Start for free Read the docs

7-day free trial · card on file, nothing charged until it ends · cancel any time

Properties, tenants, maintenance, leases and the ledger answered from one memory, with every figure cited to its record.

The systems these questions draw on, connected to one memory. Every connector reads by default; the tools that change something are granted by name, per team.

The problem

What it looks like today

01Whether a tenant has paid is in one system and why they say they have not is in the inbox.
02Repair requests arrive by email and are tracked by memory.
03Tenancy end dates and inspections are in a spreadsheet beside the signed agreements.
04A landlord's question about their property takes a morning to answer well.
05A landlord and a tenant are told two different things about the same repair, a week apart.
06Certificates, deposits and renewal dates live in a spreadsheet that is only as good as the last person to open it.

How it works

What Memtro does about it

One memory in front of the systems you already pay for, reading by default and acting only where an administrator has granted the tool by name.

Connect Outlook or Gmail, the calendar, Xero or QuickBooks Online, GoCardless, DocuSign, Typeform and Twilio, reading by default and acting where you grant it.
Ask about a property or a tenant and the answer joins the tenancy, the payments and the correspondence, each fact cited.
Repair requests, tenants and properties are anchored into memory, so the history of a flat is one question away.
Google Calendar can create or move an inspection, Gmail and Outlook can send the letter, and Xero can raise the invoice, each only when asked and only once granted by name.
Schedule jobs: rent not collected by the fifth, tenancies ending in 60 days, repair requests without a reply in two days, posted to the team's channel.

The stack

System by system

What Memtro reads in each part of the stack, and what it may change there once the tool has been granted.

Mail and attachments

Outlook or Gmail: repair requests, landlord instructions and tenant threads, with the certificate, statement or invoice attached to them read as text.

Diary

Outlook Calendar and Google Calendar: inspections, viewings and contractor visits. An event can be created or moved when you ask and the action has been granted.

Rent and the ledger

GoCardless for mandates and collections, Xero or QuickBooks Online for the ledger, Stripe where cards are taken. Xero can raise a draft invoice or record a payment once granted; the rest read.

Agreements and signature

DocuSign: tenancies, renewals and notices — what was sent, who has signed and how long the other side has had it.

Forms and messaging

Typeform for reported issues and Twilio for the SMS record, so what a tenant was actually told is part of the answer rather than a recollection.

Reputation

Google Business Profile: what tenants and landlords are saying in public, read every morning with everything else rather than found by a prospective landlord first.

There are 144 connectors in all, each with its own tools, its own permissions and a page of its own. Browse every connector →

Who it is for

Who asks what

Property manager

Answers for a block without opening five systems: who has paid, what has been reported, what was promised and what is booked in.

Lettings

Sees which tenancies end when, which have been renewed, and which landlords have given instructions that nobody has acted on.

Client accounting

Chases rent from the ledger and the mandate together, with the tenant's last message attached to every line.

Principal

Watches the portfolio: arrears, repairs outstanding, tenancies ending, and landlords who have not heard from the firm this quarter.

The work that comes round

The tenancy, start to end

01
Let
The agreement is signed in DocuSign, the mandate is set up in GoCardless and the dates are read from the documents themselves, so the diary and the file agree.
02
Rent
A daily job lists what was due and not collected, with the tenant's last message beside it, so the chase starts from what they already said.
03
Repairs
A request arrives by email and is answered from the property's history: what has been reported before, who attended, what it cost and what the landlord agreed to.
04
Renewal or end
Sixty days out, the tenancies ending and the landlords who have not been written to arrive as one list, and the deposit and condition record is read from the documents, not reconstructed.

In practice

Ask it like this

Plain English, from chat, your editor, a scheduled job or your own agent. In agent mode each question also checks the other systems that know about the same people, companies and references, and the answer ends with a line per system consulted.

How agent mode works Watch the tour

Memtro · agent mode

Which tenants at Elm Court have not paid this month, and what have they said about it?

Reading 5 systems…

Outlook Mail
Outlook Calendar
Gmail
Xero
QuickBooks Online

Every figure in the answer cites the record it came from, and the run ends with a line per system consulted.

›Which tenancies end in the next 60 days, and have we written to the landlords?
›What repairs has flat 4B reported this year, and what did we do about each?
›Summarise everything we hold on the landlord of 12 Station Road
›What has flat 12 at Elm Court cost the landlord this year, and on what?
›Which inspections are due in the next month, and which are already booked in?
›Has the tenant at 4B been told about Thursday's contractor visit, and how?
›Which landlords have had no statement or update from us this quarter?

On a schedule

Work that runs itself

A job is a prompt the agent runs on a cron schedule as its owner, with their tools and connections. Say any of these in chat and the job exists; every run's report is kept in a chat you can question.

schedule:Every day 09:00: rent due and not collected, with the tenant's last message
schedule:Every Monday 08:00: tenancies ending in 60 days and inspections due in 14
schedule:Every day 17:00: repair requests received by email with no reply in two working days
schedule:Every Monday 09:00: repairs reported more than 14 days ago with no completion recorded, by property
schedule:First of the month: landlords with no statement or contact in 90 days, with the properties they own

How jobs work

Questions

Questions people ask

Can it take payments or change a tenancy?+

No. GoCardless, the ledger and DocuSign are read; Xero can raise a draft invoice or record a payment only if you grant that action, and the calendar can create an event when asked.

Is tenant data kept private?+

Each fact is classified personal or shared, connections are granted to named teams, and a request to be forgotten removes a person from every store with a receipt.

Does it integrate with property software?+

Not directly yet. The mail, payments, documents, calendar and ledger around a tenancy are covered, and a system with a reporting database is reachable over Postgres, MySQL or SQL Server.

Can it answer a tenant directly?+

Not on its own. Where the mail action is granted it drafts the reply and a person sends it, and the Twilio record of what was texted is read, so what a tenant was told is part of the answer rather than a recollection.

Does it work across several branches?+

Yes. Each branch's mailboxes, calendars and ledgers are connections granted to that branch's team, and a group question is answered across all of them with the branch named on every figure.

Can we see what it has been asked?+

Yes. Usage by person, team, model and day is in the dashboard with a CSV export, every scheduled job keeps the report of each run in a chat you can question, and each answer names the records it used.

The same work, by team

The same connectors and the same memory, described through the job somebody does rather than the business they do it in.

Memtro for property management

Ask it about your own business

Connect the first two systems, ask the question you opened this page with, and see where the answer comes from. About five minutes.

Start for free Pricing