SODAX SDKDigital asset flows you can build and deploy with AI.
Promoted
Meet Estera, the AI receptionist built for real estate, hotels, restaurants, and more. AI agent receptionist that answers every phone call and WhatsApp message in under 5 seconds, qualifies leads, books appointments, and follows up automatically. Built for real estate, hotels, restaurants, dental clinics, and more. Create your own AI agent assistant in under 3 minutes.
Estera
Introducing Estera - the AI receptionist that answers every phone call and WhatsApp message for your business, 24/7.
Service and hospitality businesses - salons, clinics, restaurants, real estate, hotels, dealerships - live and die by response time. But most calls come in while staff are with a customer, and most WhatsApp messages arrive after hours. Every missed one is a booking that quietly walks to a competitor.
❓ The obvious fix is "just add a chatbot." But anyone who's tried it knows how that feels: a robotic bot that answers an FAQ, doesn't know your prices, can't actually book anything, and makes customers ask for a human by the second message.
🤔 Turns out a receptionist is the hard part, not the chat. It has to know your services, policies and pricing, speak your customer's language, handle a real back-and-forth, and write the appointment straight into your calendar - not just talk.
So we built Estera to be exactly that, live in under 3 minutes with zero technical setup:
✅ Answers inbound calls and WhatsApp instantly, 24/7
✅ Trained on your business - services, pricing, policies, FAQs
✅ Books appointments directly into your existing calendar / PMS / CRM
✅ Qualifies leads and follows up automatically on no-shows
✅ Uses your existing phone number & WhatsApp Business number - no new hardware
✅ Speaks 50+ languages
Estera ships as three connected tools: Concierge (inbound WhatsApp), Voice (inbound calls), and Messages (outbound WhatsApp campaigns) - one AI assistant across all of them.
Try the live demo (no signup) or spin up your own agent in a minute at tryestera.com.
We'd love to hear your feedback 🙌
HI @fredyandrei answering your question about trust.. I think our biggest hesitation with voice AI is how it handles noisy backgrounds or heavy accents. Congrats🙌 Upvoted hope you crush it on PH today....
Estera
@priya_kushwaha1 Thanks a lot, really appreciate it 🙏 On accents and noise, totally fair to raise, it's usually the first thing people worry about with voice AI.
@fredyandrei We ran an answering service last year and WhatsApp was the failure point: people send voice notes or photos of a broken part and the bot couldn't triage them. How does Estera handle non-text messages, and when does it hand off to a human instead of looping the caller?
Estera
@artem_fedorovich Right now, our agents can read images, but voice notes go straight to a human. We are working on making this possible too.
Dial
the trust question that'd matter most to me isn't accents or background noise, it's what happens when Estera gets something wrong mid-booking - quotes a price that's since changed, or double-books a slot your calendar already had held. does the business get a heads up to catch that before the customer shows up, or is the first anyone hears of it when the customer's standing at the counter confused? for something handling money and scheduling unsupervised, the failure path matters more than the happy path demo
Estera
Thanks for your comment, @galdayan! Our system doesn't work by catching the mistake after it happens and alerting you. It works by not letting the agent commit to something it isn't sure of in the first place. Pricing comes from a live source, either pulled directly from your site or from a document you keep current. That's not an add on, it's a baseline requirement for the agent to do its job. A wrong price is a sales problem, not a technical footnote.
When there's a gray area, a discrepancy, something it can't confirm with certainty, it doesn't guess. It tells the customer someone will follow up with the exact details and hands the conversation to a real person. So, the customer doesn't end up confused at the counter because the agent never promised something it couldn't back up. The risk isn't removed by monitoring after the fact, it's removed by the agent knowing when not to decide on its own. Hope this answers your question!
ClinicFrame
Fredy, your answer to Gal about the agent knowing when not to decide is the strongest thing in this thread, so I will push on the vertical list instead.
Clinics do not behave like salons or restaurants. A patient calling to book usually says why, and that reason becomes regulated health data the moment it lands in a transcript, a CRM field or a follow up message. In the US that also rules out the channel you lead with, because Meta does not sign a business associate agreement for WhatsApp, so a clinic running patient conversations there is exposed no matter how careful your agent is.
Is a clinic a separate configuration for you, or the same agent with a different script?
Estera
Thanks for your support, @clemente_lopez1! We don't have a US medical client today, so this hasn't come up in practice yet. HIPAA would mean a BAA-covered setup, and WhatsApp doesn't offer that, so clinics there would need a separate channel built around that requirement. It's on our radar for when we go after that market.
Meridian
The live pricing and human handoff approach is practical. How does Estera prevent double-bookings when two customers try to claim the same slot at nearly the same time across calls and WhatsApp?
Estera
@adityaharish2002 Two layers, really. Say someone books a consultation over the weekend, the business can double check it's actually free when they're back Monday, that part's standard no matter the channel, because unpredictable human problems can appear outside Estera system. On top of that Estera holds the slot in real time the moment someone's booking it, so if a second request comes in on the other channel seconds later, it sees it as taken. These types of situations are already rare, but that's the bit that covers it
This is nice. How does it handle callers who specifically demand to speak to a human?
Estera
@dhiraj_patel5 Right now if a caller asks to speak to a human, the agent lets them know someone will call back as soon as possible.
The real estate use case is interesting — I manage rental properties, and the after-hours call problem is real. Tenants call at 10 PM about a leaking pipe, and you're choosing between answering every call or missing something urgent. How does Estera handle triage? Can it distinguish between "my faucet drips a little" and "water is coming through the ceiling" and route those differently? That escalation logic is where most AI receptionists fall flat.
I build on the support side so take the bias into account. Calls and WhatsApp look like one inbox and they are not, and the follow-up promise is where that shows.
On a call the conversation has a beginning and an end. On WhatsApp it has neither. The customer replies four hours later in the same thread expecting you to remember, so it is really a record that never closes. That is a different data model to a call transcript, not a variation on one.
The specific thing I would check is the follow-up. WhatsApp only allows free-form messages inside the service window after the customer's last message. Outside it you are on approved templates. So automatic follow-up either lands inside that window, or it goes out as a template and reads like one, which for a dental clinic chasing a booking is the wrong tone.
The other one is handover. Estera answers at 2am, a human picks the thread up at 9am, and the customer has no idea a shift changed. Whatever was promised overnight has to be sitting in front of that human, or they contradict their own receptionist and the customer just sees a business changing its mind.
Neither is a reason not to build it. They are the two places where one feature behaves differently per channel, and both are cheaper to design for now than to retrofit..