Ruby answers for your business. A listing needs a number that answers for a property.
Ruby is a live receptionist service, and it is good at what it was built for: a small business with one main number, one set of callers, and a person who wants those calls handled warmly. A leasing assignment is a different shape, and the difference is not about quality.
A brokerage is not one business with one phone. It is a portfolio of assignments, each with its own property, its own suites, its own asking rate, and its own list of what the owner will and will not sign. The receptionist model puts one script in front of every caller. The listing model needs a different script per property, changed the week the anchor tenant signs.
What a live receptionist does well
A person picks up. They are pleasant, they take a message, and they can handle a caller who goes off script in a way no automated system matches. If most of your inbound is people trying to reach you personally, that is the right product and this page is not an argument against it.
Live services are also genuinely flexible. Tell them a new rule and it is in the binder. The tradeoff is that a human reading a binder is being asked to hold five properties in their head at once, and the person answering at 4pm is not the person who took the briefing.
Where it stops on a leasing call
Three things tend to come apart on a listing:
- Property knowledge. A caller asks whether the suite next to the nail salon is the 1,450 or the 2,800. A receptionist taking messages for forty clients cannot answer that, so the call becomes a callback request instead of a qualified lead.
- Pricing shape. Receptionist plans are sold per business, in blocks of minutes or calls. A listing that gets nine calls in March and forty in April does not map cleanly onto that, and neither does adding a line for one vacancy and dropping it when the space leases.
- The vendor problem. Every call gets a message taken, including the SEO pitch and the drone photographer. A message is still an interruption. Screening means deciding not to forward something, and that is a judgment a general receptionist has no basis to make on your behalf.
What the listing version looks like instead
One number per property, loaded with that property: suites, sizes, the rate if you want it quoted, timing, and the uses you will not take. It answers, asks the five things that decide whether a caller is worth your afternoon, and files the ones that are not. The lead reaches you as a text before the caller has left the parking lot, with a transcript and a recording behind it.
When the space leases, the number goes away. You are not carrying a receptionist plan for a property you no longer represent.
Check Ruby's current plans yourself before comparing cost. The point here is not that one is cheaper. It is that one is priced per business and the other is priced per vacancy, and a vacancy is the unit a broker actually manages.
$99/mo per listing. Cancel when it leases.
Questions brokers ask
Is Ruby a good fit for a commercial real estate broker?
It depends what your inbound actually is. Ruby is built for a small business with one main number and one set of callers, and a live person handles a caller who goes off script better than any automated system. If most people calling you are trying to reach you personally, it is the right product.
Where does a live receptionist service stop on a leasing call?
At the property. A brokerage is a portfolio of assignments, each with its own suites, its own asking rate, and its own rules about what the owner will disclose. A receptionist reading a binder is holding five properties at once, so a caller asking whether the suite next to the salon is the 1,450 or the 2,800 gets a callback promise instead of an answer.
Can a live receptionist answer questions about one specific vacancy?
Only as well as the binder allows, and the binder covers everything you represent. It is answering for your business rather than for one property. That is the design, not a defect.