Short answers to the questions people ask when they are working out whether software like this is worth having. Each page says what the thing does, how it works, and what it cannot do — including where our own product falls short. They are written to be useful even if you end up buying from someone else.
An AI front desk answers customer questions from a business's own documents, books appointments into a real calendar, and takes a message when it cannot help. It handles first contact on a website — not on a phone line, which is what separates it from an answering service.
Yes. With an OAuth connection to your calendar, an assistant can read your real free/busy, offer only slots you are genuinely free for, write the event, and email a confirmation to both sides. The important detail is whether it writes the booking or merely links to a booking page.
Ground it: retrieve passages from your own documents and answer only from those, require every answer to cite its source, and set a relevance floor so that when nothing clears it the assistant says it does not know instead of generating something plausible.
A chatbot's job ends when it replies. A front desk's job ends when the customer's task is done: the appointment booked on a real calendar, the enquiry captured as a record you own, or the conversation handed to a person with the transcript attached.
You almost certainly want retrieval, not training. The model stays as it is, and at question time the system searches your documents and puts the relevant passages in front of it. Updating your knowledge is then a file upload rather than a retraining run.
Put the answers you have already written where a customer can reach them unaided. An assistant trained on your pricing, policies and service list answers at the moment the question is asked, cites which document it used, and takes a message when your documents fall short.
It depends on the vendor, and there are two questions rather than one: whether the product you signed up to trains on your content, and whether the model provider behind it does. A vendor can answer no to the first while the second is still true.
Some do; many do not, and the word “voice” hides the difference. Answering a telephone needs a phone number and SIP telephony. Browser voice means a visitor speaks to an assistant on your website. Both are called voice, and only one rings.
Partly so people find us. There is no point pretending otherwise — these pages exist because someone typing “can an AI book appointments on my calendar” is exactly the person we would like to reach.
The rest of the reason is that the honest answer to most of these questions is more qualified than the marketing in this category suggests, and the qualifications are the useful part. Whether an assistant answers a telephone or only a browser, whether “trained on your documents” means training or retrieval, whether a no-training promise covers the model provider as well as the vendor — those distinctions decide whether the software works for you, and almost nobody writes them down.
Upload your own documents on the free plan and ask it something you already know the answer to. That tells you more than any of these pages will.