Everyone is out at viewings and the phone keeps ringing
In short. Sales, lettings and repairs all arrive on the same line, and the branch is thinnest on the days it rings most. Enquiry 360 is an AI receptionist for estate and letting agents. It answers on your own number, day and night, in 66 languages. It asks the questions you configure, so a viewing request, a market appraisal and a tenant with no heating go down different paths from the first answer, and each lands as a structured record in your own Microsoft Dataverse. From £99 + VAT a month. You can ring 01905 918444 and hear it answer.
An applicant who has just seen a listing rings three agents. The one who picks up gets the viewing.
One line, three different jobs
Applicants ring about a property they found ten minutes ago and want to know whether it has gone. Vendors ring for a market appraisal, usually having already tried two other agents that morning. Landlords chase rent, statements and the contractor who was meant to attend on Tuesday. Tenants ring because the boiler has packed in.
Those calls want different people and different urgency, and they all come in on one number. Saturday is the worst of it. The negotiators are out, the phone is busiest, and the enquiry that turns into an instruction is the one nobody was there to take.
Urgent, routine, and who gets it
You set the criteria. Water coming through a ceiling and a dripping tap are separated by the answers the tenant gives, and they go to different places: the property manager who looks after the block, the maintenance inbox, or whoever is on call that weekend. Where you have configured a number, an urgent caller is put through to a person.
The on-call rota is configuration and the enquiries are Dataverse rows, so changing who picks up a Friday night leak is an edit in the app rather than a round of texts about who is covering.
What it takes down, and what it checks
Property or tenancy reference, the address and postcode, what the caller wants, when they are free, and a number to ring back. It reads the details back where you ask it to, so a transposed postcode gets corrected while the caller is still on the phone. A value is checked against the rule the form declares, and an answer it cannot make sense of is asked again rather than guessed at.
Callers are told at the start that they are speaking to an automated assistant. Most of them carry on, because they get to the point of the call faster than any queue would let them.
Where the enquiry lands
Every call becomes a row in your own Microsoft Dataverse, inside your own Microsoft tenant, under your sign-in and your access rules. A few things follow from that, and they are worth spelling out.
Reporting works because an enquiry is an ordinary table. Power BI, Excel and the built-in views and charts read it, so counting appraisal requests by branch, or repairs by property, or how long a landlord chase took to answer, is a chart rather than a project.
Power Automate reaches over a thousand connectors, so the same record can go to a shared inbox, post into a Teams channel, or be written into a job system, an accounting package or anything else with an API. The app runs on phone and tablet, which matters for people who spend the day in a car. Dataverse auditing applies, and the transcript of the conversation is held against the session. It installs into the same Dataverse that Dynamics 365 runs on, so it sits alongside that where you have it and stands on its own where you do not.
What stays with your people
Judgement. It captures the request, and whoever decides sees the whole record: what was asked, what was said, and when. The appraisal is booked by your valuer. An offer is put to the vendor by the negotiator who knows the chain. The rent figure comes from you.
Where the diary or the property system sits outside Dataverse, it captures the request and your team confirms the slot. That is the call an applicant expects to get, and it is a short one when the details are already down.
The same intake when a negotiator picks up
The same process runs on screen for whoever is in the branch: same questions, same order, same record at the end. Some agencies start there, get intake consistent across sales and lettings, then add the phone once they trust what it captures.
You can take the app on its own from Microsoft AppSource and add the voice agent later, or not at all.
Frequently asked
Can it tell an applicant whether a property is still available?
It asks which property they mean and what they want to do about it, then puts that in front of the negotiator handling it. Availability usually lives in your property software, so the pattern that works is to capture the request against the property reference and let the person who knows the position ring back. They can do that from the record on their phone, which is usually sooner than the applicant expected.
What happens when a tenant rings on a Friday night with no heating?
It answers, asks your urgency questions, and acts on the answers. Where you have configured a number, it puts the tenant through to whoever is on call. Where you would rather it took the report, the report is filed and sent wherever you say, with the address, the tenancy and what has failed. Three in the morning works the same as three in the afternoon and costs the same, so a lettings repairs line can be covered every night of the week.
Will it book a viewing straight into our diary?
It captures the request with the property, the applicant and when they are free. Getting that into a diary depends on where the diary lives. Power Automate reaches over a thousand connectors, so a system with an API can be written to, and where the diary sits somewhere it cannot reach, a negotiator confirms the slot. Applicants expect that call anyway, and it is a much shorter one when the details are already down.
How does it keep sales, lettings and repairs apart?
You configure the questions and the branching, so the caller's first answer sends the call down a different path. A market appraisal and a broken lock have almost nothing in common after that point: different questions, different urgency, different team. Each arrives as its own record with the fields you asked for filled in.
Will it give a vendor a valuation figure?
It takes the appraisal request: the address, the property, when they are free and how to reach them, then gets it to your valuer. Pricing a house is a judgement your people are paid for, and a figure invented on the phone is one you would spend the rest of the instruction arguing with. Rent works the same way. It captures what the landlord is asking and leaves the advice to you.
Where do the enquiries end up, and can we report on them?
They land in your own Microsoft Dataverse, in your own Microsoft tenant, under Entra ID sign-in and your access rules. Because each enquiry is a Dataverse row, Power BI and Excel read it like any other table, so appraisal requests by branch, repairs by property or how long a chase took to answer are ordinary charts. Power Automate can push the same record into a shared inbox, a Teams channel or a job system. The app runs on a phone, which is where most of your negotiators are.
Can we hear it before committing?
Ring 01905 918444. It is a live line rather than a recording and takes about a minute. The voice agent starts at £99 + VAT a month, with free setup.
Could it replace our switchboard?
Yes. Where a switchboard sorts callers into departments, this asks what they are ringing about and deals with the enquiry itself where it can: a viewing, a repair, a question about whether something is still available. Anything that genuinely needs a negotiator goes through to one, with what the caller already said attached.
Hear it handle one. Ring 01905 918444. It is a live line, not a recording, and it takes about a minute.
From £99 + VAT a month. Free setup, cancel anytime. Or read where your call data lives and how it compares to an answering service.