MILabs
Integrations

Lead intake assistant for Reapit

How a lead intake assistant can match enquiries to Reapit records, with a person confirming every match before anything is saved.

Updated 2026-01-18

Lead intake assistant with Reapit

Enquiries for a property business rarely arrive in one place. A buyer might answer a listing on a portal, a landlord might use a contact form on the agency website, and a tenant might send a message after hours. Each one has to be matched to a property and a contact in Reapit before anyone can act on it. A lead intake assistant is built to read these messages as they come in, suggest the property and the type of enquiry, and prepare a draft record for a negotiator to check. Nothing is saved to the account until a person confirms it. For a lettings team the same step might pick out a maintenance question and route it to the right coordinator. This page describes how such an assistant could sit alongside Reapit, which routes into the platform are documented in its public API, and where a team should expect manual checking to remain necessary.

How it works

  1. Connect to the Reapit API with a credential that has read access to contacts and properties, and confirm the scopes the account grants before building.

  2. Receive each enquiry from the listing portal or website form and extract the property reference, sender details and enquiry type.

  3. Match the enquiry against existing contact and property records, and propose the best match with a short note explaining the reason.

  4. Hold the proposed record in a review queue so a person can confirm, correct or reject it before any write goes to Reapit.

  5. Write the confirmed contact and enquiry back to the account, and log which person approved each change.

  6. Review match accuracy each week and adjust the rules where duplicate contacts or inconsistent address formats cause errors.

good questions, straight answers

Frequently asked questions

What does a lead intake assistant read from Reapit?
A lead intake assistant reads the contents of an incoming enquiry first, such as the message text, the sender's name and contact details, and any property reference the portal or form includes. To suggest a match, it then needs read access to the Reapit records the account exposes through the API, usually contacts and properties. An administrator decides which fields are visible by granting permissions, so the build starts with a short, sensible list of the fields that matter most.
Is a lead intake assistant safe with Reapit data?
Yes, if the build is limited to what the job needs. Enquiry text often contains personal details, so the team should confirm which data leaves Reapit and which model provider receives it, and read that provider's terms on data use. Access should be a dedicated account with the narrowest scopes possible, and the audit trail should record each suggestion and each approval. Sensitive tenancy or vendor details may need to stay out of the model prompt, a call the business should make with its privacy obligations in mind.
What happens if Reapit changes?
The build depends on the Reapit API and on the model provider's interface, so either can change. A vendor update might alter endpoints, scopes or field names, and a provider might retire a model version. The team should watch the Reapit developer documentation and the provider's deprecation notices, and keep the integration in version control with tests that run the sample enquiries. When something breaks, the assistant should stop writing rather than guess, so staff can work from the review queue while the fix is made.
Who owns a lead intake assistant built around Reapit?
The business that owns the Reapit account owns the data, and should hold the rights to the assistant's code, prompts and review rules. A contractor such as MILabs can design and build it, but the handover should name who receives the source, the credentials and the documentation. Ownership of any third-party model subscription stays with the business that pays for it, so the account and billing sit in its own name.
How does a lead intake assistant hand work to a person in Reapit?
The assistant should never mark an enquiry as handled on its own. It places each proposed match in a review queue that a negotiator or coordinator can open, where they see the original message, the suggested record and the reason for the match. They confirm, edit or reject it, and only then does the approved entry get written to the account. Rejected suggestions feed back into the rules, so the same mistake is less likely to repeat.
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.