Inquiry Management

The enquiry is the asset. Portals pass the same one to three competitors, so the only thing that separates you is how fast somebody replies.

From$799

Open the preview Request a quote

Function: 22
User types: 3
Platform: iOS & Android

React Native
TypeScript
PostgreSQL
Expo

Inside the app

What it does out of the box

22 connected functions on one schema across 3 user types. Everything below is in the template before a line of customisation.

Queue
Oldest first, because an enquiry ageing is the only thing wrong with it. Sorting by anything else is how enquiries go cold.
One-step conversion
Enquiry to viewing without retyping anything. Friction here is measured in lost instructions.
Templates
For the answers you give forty times a week, still sent by a person who read the question.
Response time
Median and distribution per agent against the branch. The number that predicts conversion, made visible.
Routing
By area, property type or agent, with reassignment when somebody is away. An enquiry sitting in an absent agent’s queue is a lost enquiry.
Landlord visibility
A landlord sees the enquiries on their property and how fast each was answered. It is the single most persuasive thing at a re-instruction conversation.

User types

Three apps, one enquiry.

The agent works one queue, the branch works all of them, and the landlord watches whether their property is being handled. That third view is uncomfortable and it is the reason the first two improve.

Owner
1 of 5 screens
The landlord
Sees the enquiries on their own properties and how quickly they were answered, which is the thing landlords most often suspect and cannot check.
Preview as the owner
- Enquiries on your properties only
- How fast each was answered
- Viewings that came out of them
- Where enquiries are coming from
- No sight of the agency’s other clients
Agent
2 of 5 screens
The agent
Works their own queue, converts enquiries into viewings, and is measured on the number that actually predicts conversion.
Preview as the agent
- Your queue, oldest first
- Convert to a viewing in one step
- Templates for the repeated answers
- Your median response time
- Nothing older than an hour, unanswered
Staff
2 of 5 screens
The branch
Covers the whole branch queue: routes what arrives, reassigns when somebody is out, and watches for anything about to breach.
Preview as the staff
- The whole branch queue
- Route by area, type or agent
- Reassign when somebody is away
- Breach warnings before they happen
- Source and volume by day

The limits

What this is not.

The same list we give for every app in the catalogue, because the fastest way to a bad project is a promise made in a meeting that nobody wrote down.

It is not a portal and carries no audience
Listings appear where you publish them. Most agencies keep portal listings for reach and use this to own the enquiry.
It is not legal, valuation or agency advice
Contracts, disclosures, tenancy rules and licensing where you operate remain yours. We build to the process you confirm.
It will not answer enquiries for you
Templates help; automation does not. An auto-reply that reads like an auto-reply is worse than a slow human one.
It is not a CRM for the whole agency
Vendor and applicant management at depth is Pipeline CRM or Recruitment Agency CRM territory. This is the enquiry layer.

Questions

Questions, answered plainly.

If yours is not here, ask it on the call rather than guessing from a pricing page.

Not covered here?

Ask a consultant directly. No form to fill in first, and no follow-up sequence.

Book a consultant All questions

Why is response time the headline metric?

Because a portal sends the same enquiry to several agencies and the first credible reply usually wins the viewing. It is the one number under your control that reliably moves conversion.

Should landlords really see how fast we replied?

It is optional, and agencies that switch it on tend to keep it on. It is uncomfortable for a fortnight and then it is the strongest thing you can show at renewal.

Can it capture enquiries from portals?

Portal email and API feeds are a standard integration in a fitted build, so enquiries land in the queue rather than in an inbox somebody checks between viewings.

Does it auto-reply?

It can acknowledge receipt, and we would advise nothing more. An automated answer that pretends to be personal is worse than a slower real one.

Do I get the source code?

Yes. All three apps, API, schema, migrations and deployment configuration transfer on delivery.