From your records, yes. From guesswork, never. If it is not in your system it does not get said.
Published April 9, 2026
Yes, and this is the single most common question a leasing operation receives, so it is worth getting exactly right.
The important qualifier is where the answer comes from. It reads availability and rates from your own system at the moment it is asked. It does not work from a summary somebody pasted in during setup, because that summary is wrong within a week.
Availability is the most volatile thing in your business. Units go under application, applications fall through, rates move with the season, a concession starts on Monday.
Any automation that holds its own copy of that will drift, and the failure is worse than silence. Telling somebody a unit is available when it is not produces a wasted tour, an awkward conversation and a prospect who now doubts everything else you said.
In each of those cases the correct behaviour is to say it will get the exact figure and hand to a person. That is a slightly worse experience in the moment and a much better one over the following week.
A good share of pricing questions are actually questions about total cost, and answering only the headline rent leaves the person to discover the rest later.
Deposits, pet fees, parking, utilities and what is included are all things your policy already defines, and they belong in the answer when somebody asks what it costs. Handling them up front removes most of the friction that otherwise appears at application.
Because the agent answers from your records, the quality of its answers is the quality of your records. That is a feature rather than a limitation, but it has a consequence worth planning for.
If units sit marked available for a week after they are gone, or rates live in a spreadsheet nobody has updated, the agent will confidently repeat that. Spending an hour tidying availability before launch is usually the cheapest improvement in the whole project, and it improves your team's answers too.
Most systems have more than two states, and the ones in between are where wrong answers come from.
Deciding how each of those is described to a caller is a business decision worth making explicitly. Saying a unit under application is simply available produces disappointment. Saying it is unavailable loses somebody who would happily have been the backup if that application falls through, which happens often enough to matter.
The other case worth scripting is the one where the honest answer is no. Nothing in their size, nothing in their timing, nothing in their budget.
Handled badly that is a dead end. Handled well it is an offer to let them know when something matching comes up, and a note in your system so the offer is actually kept. It costs nothing and it turns a wasted inquiry into a lead for next month.
One question worth asking whoever builds this for you: at the moment a caller asks, how old is the data behind the answer.
A live read is the ideal and is not always available, since some systems have rate limits that make reading on every question impractical. A short cache is usually fine. A file exported this morning is a compromise you should know you are making, and one that is acceptable for rates and policy while being genuinely risky for availability in a portfolio that turns over quickly.
On the site
Keep reading