An AI web call is a voice conversation that a visitor starts within a page using their device's microphone and speakers. In this flow, they do not need to dial a number. The agent listens to the inquiry and responds within its configured scope. For a real estate business, it can be a way to answer a question while a buyer is viewing a development.
The value is not in adding sound to a website. It is in helping someone understand something and leaving a useful next step: exploring a unit type, requesting information or asking an advisor to continue. A pleasant conversation that loses track of the project of interest still leaves unfinished work for the sales team.
Not all “Call” buttons do the same thing
Agree on the journey before comparing providers. A button can open the phone app, request a callback or start audio in the browser. The expression click to call is used for several of these implementations; the name alone does not describe what the visitor receives.
| Journey | What the visitor does | What must work |
|---|---|---|
| Telephone link | Opens the dialer or app associated with a number. | Line, hours and availability of the receiving person. |
| Callback | Leaves their details and requests later contact. | Owner, response deadline and permission to contact. |
| Web call | Speak in the browser with authorized microphone access. | Audio, connection, agent and an exit when it is not possible to continue. |
In a pure web call, the initial connection does not use the visitor’s phone number. This does not mean the session is free for the business: platform, voice processing, model and operating charges may apply. If a phone call is requested afterward, that second interaction has its own terms. Our guide to the total cost of an AI agent helps separate those concepts.
How to try FARO's voice demo
On the homepage you will find Talk to FARO, the real estate voice demo. Open the panel using “Start voice conversation.” The session control lets you continue, and the browser requests microphone access when needed. Try a question about a business need; you do not need to share a real buyer's data to evaluate the experience.
- Prepare a specific question: “I want to handle apartment inquiries when my team is busy.”
- Check whether you understand the answer and can interrupt or correct an idea.
- Test a boundary: “My calendar isn't connected yet; can you confirm a viewing?”
- Watch whether it distinguishes a proposed capability from an available connection.
- End the session and close the panel. If you cannot use audio, choose the scheduling alternative.
The demo is designed to explore real estate inquiries. It does not verify a property’s availability or activate an agent for your company. When you start a conversation, it is processed in FARO CRM to handle your inquiry, as stated in the notice on the homepage. You can consult the privacy policy before using it.
FARO also keeps a visual demonstration of FARO 0.5 covering inventory, the website and clients. These are different experiences. The visual demo helps explain how information is organized; the web call lets you explore the voice conversation. Seeing both does not establish that another business's calendar, inventory or CRM is connected.
What information should accompany the conversation
Imagine a project page with three unit types. A visitor compares the two-bedroom option and asks whether there are alternatives with a balcony. If the agent starts by asking which company she means, it loses the context on her screen. An implementation designed for that page can pass along the project and unit-type identifiers, language and inquiry source. That connection must be built and tested: a widget does not automatically know everything the person sees.
Page context is a clue, not the buyer’s decision. A person may switch unit types or ask about another project. The agent must allow that correction and retain the final interest. Nor should every parameter received from the browser be treated as a commercial fact: price and availability must come from the authorized source.
For a real estate pilot, prepare a short brief for each development: name, location, unit types, approved materials, update date and person responsible. Separate questions that can be answered from that brief from those requiring an inventory check. If availability is not connected, a useful response is to record the preference and request confirmation from the agent, without claiming the unit is still available.
After the conversation, the team needs a clear record: expressed interest, outstanding information, contact details provided and the next action. ‘They liked the apartment’ is not enough to organize the work. A summary that distinguishes a stated budget from approved financing prevents an agent's interpretation from becoming a fact in the CRM. We explore this flow further in Voice AI for real estate.
Human handoff must be designed for the channel
Transferring a telephone call and continuing a browser conversation are different operations. The HighLevel documentation consulted on November 11, 2026 states that its voice widget does not support call transfers while in beta. A web call should therefore not promise to connect someone immediately to an advisor by phone.
A workable outcome may be to prepare a contact request, offer the calendar or show an alternative channel. Whichever option is chosen needs an owner and an honest status: ‘request received’ if no one has confirmed it. If you require a live transfer, it must be explicitly verified with the chosen solution and configuration; it cannot be inferred from how well the agent speaks.
What to test in a web call before publishing it
Microphone permission is part of the experience. Browsers require a secure context and user authorization to access audio. A person may deny permission, have no microphone or open the page inside another app. The flow must remain understandable in those cases and offer a written or contact alternative.
Alongside an ideal conversation, prepare this acceptance matrix. You do not need to simulate a hundred situations initially, but you do need to cover failures that would leave someone stranded or generate a false promise.
- Permission denied: the page explains how to continue and lets people leave without repeated pop-ups.
- Connection interrupted: the status no longer indicates an active conversation; it does not present an unconfirmed request as saved.
- Unknown information: the agent recognizes the limit and offers a defined next step.
- Change of interest: the final summary retains the corrected unit type or service.
- Misheard details: the visitor can confirm or correct the required details.
- Session end: the user can end the conversation and understand what happens next.
- Mobile and keyboard: controls are reachable, readable and do not obscure the main information.
Test with the devices and conditions your visitors use: a phone with headphones, an office computer and a mobile connection. Record the browser and test date. Success on one device does not establish universal compatibility. Include people who prefer not to speak: voice, text and scheduling can coexist without requiring everyone to use a microphone.
How to connect a web call to a developer's website
In a websites for promoters and developers, the conversation can be placed after the buyer finds the project or compares unit types. The chosen point should address a real question. Adding a floating button to every screen does not guarantee usefulness and may compete with filters, floor plans or mobile navigation.
Before implementation, write one sentence describing the agent's job on that page: “Help compare these models and prepare the inquiry for the sales office.” That sentence helps determine what information it needs, what it should not answer and how the handoff to the advisor will work. If the scope varies by project, review each project's information source and avoid mixing inventories or terms.
What to measure after starting the pilot
Separate page visits, panel openings, connected sessions, conversations with a complete request and confirmed follow-up actions. Opening the panel is not the same as speaking; speaking is not the same as requesting a viewing. The relevant conversion depends on the task: for one project, it may be an inquiry the advisor accepts for follow-up; for another, an appointment confirmed by the calendar.
Review drop-offs together with their causes. A denied permission, a disconnection and someone who received the answer they needed are not the same problem. When comparing with the existing form, use similar periods and traffic sources; a different campaign can change the quality of inquiries even when the agent stays the same.
Cost per useful request divides the expenditure attributable to the pilot by the requests that meet the agreed criteria. Include supervision in operating expenditure and show implementation separately, or amortized over a stated period. If the denominator is zero, the result is not zero cost: there are not yet any useful requests against which to calculate it. Reviewing failed conversations may contribute more to the decision than average duration.
To start, bring to the conversation with FARO a specific page, five frequently asked questions and the name of the person receiving inquiries. With that foundation, a scope can be proposed for voice for your operation and a test that ends in a decision: keep, correct or expand.
Sources and scope of this guide
Technical sources consulted on November 11, 2026. The pilot criteria and real estate example are FARO’s editorial proposals, not results from an experiment with clients.
- HighLevel: Voice AI Chat Widget, documented channel scope and restrictions.
- Retell: browser-based calls, differences from telephony and session events.
- MDN: microphone access through getUserMedia, browser permissions and conditions.
Keep exploring
- AI voice agents for real estate: from inquiry to viewing
- AI receptionist, IVR or chatbot: how to choose
- What is an AI voice agent and how can you use one in your business?
FARO's editorial judgment. Illustrative examples explain how to evaluate an operation; they do not substantiate client results.