Insights · Buying

A chat widget, an answering service, or a workflow layer: how to compare your options

Three categories do three different jobs. Here is what each does well, where each stops, what to ask the vendor, and what it costs you when it stops, counted on your leasing fee.

By Nael Orabi, Founder, ORACA AI ·

A corner apartment building with a ground-floor café at dusk, an illustration built for this site
In briefAsk the same four questions of every category: where does the inquiry go, what does it answer from, who books the viewing, and what happens when it stops.

Related

A Halifax property manager who decides to stop losing inquiries after hours has three categories to choose from. A chat widget on the website. An answering service that takes messages. A workflow layer that runs the whole front desk. They are sold with similar words and they do very different jobs.

No vendor is named here. The point is the category, because the category decides where the inquiry goes when the office is closed, and that is the whole question.

Option one: a chat widget on the website

What it does well: it answers a visitor who is already on your site, at once, at any hour. Set up is quick. The cost is low. For a question like “is parking included” it is a fair answer.

Where it stops: at the edge of the page. A renter who texts your number, emails from a listing site or messages on WhatsApp never meets it. Most widgets answer from a general model or a script, not from your listings and your written policies, so the answer to “is unit 4B still available” is a guess or a form. When the visitor asks for a viewing, the widget hands them a link, or a promise that someone will call. The inquiry lands in an inbox and starts to age.

What it costs when it stops: a widget converts the visitors it sees, and the after-hours renter who called is not one of them. Count the renters who reached voicemail last month, estimate how many would have viewed and signed, and multiply by your leasing fee. That is the gap a widget leaves open.

  • Ask the vendor: what does it answer from, my listings or a general model?
  • Ask: what happens to a text or an email? Does it see them at all?
  • Ask: can it book a viewing into my calendar, or does it send a link?

Option two: an answering service or call centre

What it does well: a person picks up. For a resident reporting a leak at midnight, a human voice matters, and a good service will page your on-call contact. It covers the phone, which is the channel most managers worry about first.

Where it stops: at the message. The agent on the line does not know your buildings, so they take a name and a number and promise a call back. The renter is still waiting for the answer they wanted, which was “is it available and when can I see it”. The message arrives by email or in a portal, separate from your website leads and your texts, and someone on your team has to retype it. Nothing is booked. Nothing is followed up unless your team does it.

What it costs when it stops: the call-back queue. Every message is a task for a person the next morning, and the morning is when the showings are. Count the messages that waited more than a day, and count them at the leasing fee, not at the rent, because rent goes to the owner and the fee is what you actually lose.

  • Ask: does the agent see my listings, or only a script?
  • Ask: where does the message go, and does it join my other inquiries or sit apart?
  • Ask: who follows up, and when? Is it written down?

Option three: a workflow layer

This is the category ORACA sells, so read this part with the appropriate suspicion and check every claim on the platform page, where each capability is marked as running today, needing a person, proposed, or dependent on your systems.

What it does well, and runs today: every inquiry from the website, text, email and WhatsApp lands in one record with its source. The assistant answers in under a minute from your listings and your own written policies, identifies itself as automated, and hands over to a person on request. Viewings go into your real calendar, Google, Microsoft or iCloud, with reminders, reschedules and no-show recovery. Follow-up continues until a viewing is held or the prospect says no, with consent recorded first. A compliance check refuses to send a reply that breaks a rule you set. Reporting prints the denominator on every rate, and a figure without enough data says so instead of showing a zero.

What is not running today, and is marked as such on this site: routing a maintenance request to a named person for approval is in the proposed maintenance desk, built with the first property client, and the approval step waits on named staff logins. ORACA has no live property management client yet. The engine answers, books and follows up for ORACA clients in other service businesses today.

Where it stops: at the decision. It organises an application and never approves one. It reads rent, arrears and occupancy from your property management system where an API or export allows, and never estimates them. It is not a person on the phone at midnight, although a person can be paged.

What it costs when it stops: ORACA writes the consequence next to the pledge. If the system is not live within 21 days of a declared start, the setup fee is refunded in full. Every inquiry is answered within five minutes, around the clock. A full export with a documented handover is available any time you ask, so there is no lock-in to price in.

The same four questions for all three

Put these to every vendor, in writing, and keep the answers.

  • Where does an inquiry go at 9:40 pm, from each channel I publish?
  • What does the answer come from: my listings and policies, a script, or a general model?
  • Who books the viewing, into which calendar, and who chases the no-show?
  • What happens when it fails, and what do you owe me when it does?

What each costs, on the same basis

A widget and an answering service are priced by their vendors. ORACA’s prices are published. Missed-Call Text-Back, the smallest piece sold on its own, is $997 setup, $497 for a limited time, then $297 a month, live on your number in 7 business days. The Leasing Desk is $3,500 setup and $2,000 a month. The Tenant & Leasing Assistant, which adds the always-on assistant across chat, text, WhatsApp and email, is $5,000 setup and $2,800 a month.

Whatever you buy, count the return the same way: at your leasing fee and management percentage, never at the tenant’s rent. Set the monthly beside the fee on one recovered placement. If the first is smaller than the second, the arithmetic is done, on your own numbers.

Fair questionsAnswered in writing, the same way they are answered on a call.

Questions this raises.

Can I start with a chat widget and add the rest later?

Yes, and many do. The cost is the inquiries that arrive by phone, text and email in the meantime, which a widget never sees. Count those at your leasing fee before deciding how long to wait.

Does ORACA replace my answering service?

It answers chat, text, WhatsApp and email itself, books viewings into your real calendar, and pages a person when judgment is needed. A voice add-on is available on request. Whether a human line stays beside it is your call, and the inquiry record is the same either way.

Does a workflow layer decide who gets a unit?

No. It organises an application and your leasing manager decides, against criteria reviewed for human rights compliance. Qualification rules exclude protected grounds.

Is a property management company running ORACA today?

No. The engine answers, books and follows up for ORACA clients in other service businesses today. The property configuration is in build, and every capability on the platform page is marked running, needing a person, proposed or integration-dependent.

Tell us how your properties run today. You get a written map of what runs on day one and what a first pilot looks like.