Put it where the question gets asked.
A page at your own link, a bubble on your website, or a voice in the browser. Same documents, same answers, the same calendar behind all three.
It quotes your policy. It doesn't paraphrase the gist.
Every reply is retrieved out of the documents you uploaded, with the file it came from shown underneath. Two searches run on each question — one for meaning, one for the exact words — so a question about clause three can actually reach clause three.
- Retrieval over your documents, not the open web
- The source file, under every answer
- Scoped to exactly the documents you choose
<script src="https://www.regenticflow.com/widget.js"
data-bot="YOUR_ASSISTANT_ID" async></script>One assistant. Three doors.
Publish it at your own link, drop one line of script onto your website for a chat bubble, or let people talk to it out loud. Each page keeps its own branding and greeting, and the embed runs only on the domains you allow.
- A public page at your own handle
- One line of script on any website
- An origin allowlist keeps it yours
The parts that finish the job
Answering is the easy half. These are the six that decide whether the conversation ends in a booking, a name you can call back, or nothing.
It books, rather than linking
It reads your real Google Calendar free/busy, holds the slot and emails a confirmation to both sides. Each meeting type gets its own length, hours and buffers; guests reschedule or cancel from their own link, and you get a prep brief and a reminder before it starts. Google Calendar only.
The lead is written down
Name, need, and a way to reach them — asked one at a time, with consent, on a deterministic path rather than a model deciding whether this exchange was worth saving. It lands in a record you own and in your inbox.
Nobody hits a dead end
When it cannot answer, or a visitor asks for a person, it opens a ticket carrying the whole transcript and emails it to you with a thread you can reply in. The visitor is told a human is coming rather than being left with an apology.
It sounds like you, and stops where you say
Tone, length, formality, emoji and language, plus an explicit list of things it must never promise. Those controls change how it actually replies. Push it on something from that list and it declines and offers to fetch you.
Voice, in a browser
Visitors can speak to it and hear it answer on your site, in a synthesised voice, with no per-minute cost. It does not answer a phone number, and we are not going to call it a receptionist.
It knows who it's talking to
Turn on verification and visitors confirm their email with a one-time code before chatting, or skip it if you allow that. A verified visitor's conversation follows them across devices, and it recognises them next time from what they told it.
It can check your own systems
On Power, connect your API: sync a catalogue or records into its knowledge, and let it run read-only lookups you approve, like an order's status, while it answers. Your credentials stay on our server and never reach a visitor's browser.
You find out what it missed
Messages, visitors, answer rate, leads and top topics — and the list of questions it could not answer, grouped by topic. That list is the most useful thing on the page: it is your next four FAQ entries, written by your customers.
Live in three steps
Add your knowledge
Upload the pricing sheet, the policy, the onboarding doc, forward them to your private capture address, or give it your website to read. It reads the pages, not just the titles.
Shape how it answers
Tone, starter questions, booking hours, what it collects, and the things it must never promise. All of it without code.
Publish it
Share the page, paste one line of script onto your site, or turn on voice. Change your mind later and the same assistant follows.