Most enquiries aren't lost to a competitor. They're lost to silence.
Someone reads your page at eleven at night, types a question, and waits. You see it on Tuesday. By then they have booked with whoever replied first. We built RegenticFlow so that the answer arrives at the hour the question was actually asked — out of the documents you have already written.
A website can't answer a question.
Every small business gets the same eight questions, over and over. What do you charge. Do you take my insurance. How far will you travel. What happens if I cancel on the day.
You have already answered all of them. The answers are sitting in a pricing sheet, a refund policy, an onboarding doc, an email you sent last March. They are simply nowhere the person asking can reach at the moment they ask.
So the question goes into an inbox and waits for you. RegenticFlow reads what you have already written and answers from it, with the source attached, at two in the morning if that is when it is needed. When your documents don't cover something, it says so plainly and takes a message. That is the whole idea. Everything else on this page is how.
From your files to their answer
Six steps, and you are only involved in the first one.
- 01 · Capture
Feed it what you already wrote
Pricing sheets, refund policies, service menus, SOPs, the onboarding doc you send every new client. Drop them in, forward them to your private capture address, or pick them out of Drive. Uploads land straight away and process in the background while you get on with something else.
PDFs, images, DOCX, scansForward an email inDrive import, file by file - 02 · Read
It reads the pages, not the titles
Every document is extracted and split into passages, so a question about clause three of your cancellation terms can reach clause three. Dates, amounts and renewal terms are pulled out on the way past. Nothing needs a folder and nothing needs a tag.
Text, tables and scansIndexed passage by passageDates and amounts detected - 03 · Answer
It answers, and shows its working
Two searches run on every question — one for meaning, one for the exact words — and the results are fused, so “do you take Delta?” and “insurance accepted” both land on the same page of your policy. Every answer carries the document it came from. When nothing clears the bar, it says so.
Meaning and exact keywordsSource under every answerRefuses rather than guesses - 04 · Book
It books the meeting
When someone is ready, the assistant reads your real Google Calendar free/busy, holds the slot and emails a confirmation to both of you. The booking itself, on the calendar you already live in. Google Calendar only — no Outlook, no Calendly, no Cal.com.
Real free/busyConfirmation both waysGoogle Calendar only - 05 · Account
Every answer keeps a receipt
Open any conversation and you can see the passages an answer was built from, what each one scored, and the floor it was judged against. Save the questions that matter most and we re-check them whenever your knowledge changes, then email you if the document that used to answer one stops reaching it. That checks retrieval, not correctness — there is no judge model, and we are not going to imply there is.
Answer receiptsSaved retrieval checksEmailed when one breaks - 06 · Escalate
When it can't help, you hear about it
Every question it answered badly is logged and grouped by topic, so you stop guessing at what to add and start reading the list. Ask for a person and it opens a ticket with the full transcript, emailed to you, with a thread you can reply in. Answering a gap turns your reply into knowledge on the spot.
Gap report by topicTicket with transcriptLead captured either way
Everything below is running today
No roadmap items, no asterisks. If something is half-built or missing we put it on the security page instead, where it is easier to find.
Capture anything
PDFs, images, DOCX, screenshots and scans, taken through a background queue so a slow upload never blocks you.
Email it in
Forward a message to your own private capture address and it files itself, attachments and all.
Drive import
Pick files through Google's own Picker. We ask for access to the files you choose, never your whole Drive.
Reads the whole page
Vision and OCR pull text, tables, dates and amounts out of documents that were never machine-readable.
Hybrid retrieval
Meaning and exact keywords are searched separately and fused, so a paraphrase and a policy number both find the same clause.
Cited answers
Every reply names the document behind it, and refuses rather than improvising when nothing clears the floor.
Answer receipts
The passages an answer used, the score each got and the bar they were judged against, kept and viewable per answer.
Saved checks
Re-run whenever your knowledge changes. You get an email when a document stops reaching the answer it used to support.
Public assistants
Publish at your own link, with your greeting, your starters and your branding on Pro.
Website embed
One line of script anywhere on your site. It runs only on the domains you allow.
Browser voice
Visitors can talk to it and hear it answer, in the browser. It does not answer a phone number.
Real booking
Google Calendar free/busy, a held slot, a unique index that refuses a double booking, and a confirmation to both sides.
Leads and tickets
Captured on a deterministic path rather than left to a model deciding whether to save someone's name.
Gap report
Every question it could not answer, clustered by topic, so the FAQ effectively writes itself.
Reads your website
Point it at your site and it crawls the pages into its knowledge, citations and all, so you don't re-upload what's already published.
Meeting types
Different lengths, schedules and buffers per kind of meeting. Guests get a link to reschedule or cancel themselves, and you get a prep brief before it starts.
Verified visitors
Optionally ask for an email and confirm it with a one-time code. Their conversation then follows them across devices, and you see one verified lead per person.
Remembers returning visitors
Built only from what the visitor told it, it expires with your transcripts, and a “Not you?” link ends it.
API connectors
On Power: sync your catalogue or records in from your own API, and let it run read-only lookups like an order's status while it answers. Credentials never reach a browser.
Weekly report
A Monday email with what your assistants were asked, what they could not answer, and the gaps worth filling first.
Proper invoices
Every charge is emailed with an invoice PDF, numbered in sequence, with tax shown when it applies.
Three things we won't trade away
Grounded, or quiet
It answers out of your documents or it declines. The bar an answer has to clear is a number in the code, not a mood — and when nothing clears it, saying so is the correct output.
Accountable afterwards
Anyone can say their AI is accurate. We keep the receipt: which passages an answer used, what they scored, what they were measured against. Checks tell you when a document stops reaching its answer. That is retrieval, not correctness, and we will not dress it up as more.
Yours, and portable
Isolation is enforced inside the database query rather than by an instruction a prompt could argue with. No shared-model training. Export the lot as JSON, or delete the account and watch it cascade.
And it still keeps your own paperwork straight
This started as a memory for personal documents and it never stopped being one. Insurance renewals, licences, vehicle registrations, filings — the assistant answering your customers is the same one that emails you before something expires quietly in a drawer.
Those reminders arrive by email. Not SMS, not WhatsApp, not a push notification — email, which is the only channel we have actually built.