They arrive from Google
A real question in their head. Pricing, fit, timeline, whether you serve their city.
Voice AI sales agent
Ora talks to your visitors, answers from your own material, and books the next step — while your team sleeps.
Tap the orb to talk
Live token counts from the provider. Prices from their published rates.
Built for teams selling considered purchases
Installs on the stack you already have
The problem
Traffic isn't the hard part any more. What happens in the ninety seconds after someone lands is the hard part — and for most sites, what happens is silence.
A real question in their head. Pricing, fit, timeline, whether you serve their city.
Your page is dense and written for everyone. They scan headings and hunt for their answer.
It's buried in a PDF, a help centre, or a page written for a different kind of buyer.
No form, no chat, no trace. You never learn what they wanted, so you can't fix it.
Every one of those visitors would have talked to a salesperson standing in front of them. Nobody was standing there.
"Send us a message."
Answered Monday. Maybe.
"Will it work on a flat roof?"
Answered in nine seconds. At 3am.
The arithmetic
Your numbers, not ours. This is the value sitting in the conversations your site isn't having today — move anything you disagree with.
Recovered every month
0
$0 a year · 0 extra deals a month
An estimate built from the values above — not a forecast, and not a promise. We'll publish real customer results here the day we have them.
The answer
No search box. No help centre. No "submit a ticket and we'll get back to you." The visitor clicks once, asks the thing they actually came for, and hears the answer out loud.
A real exchange, spoken
Not a chatbot
A support bot exists to close tickets. Ora exists to move someone closer to buying — which means asking questions back, hearing the real objection, and proposing the next step before the visitor thinks to.
What your team receives afterwards
How it works
Three steps. No plugin to maintain, no rebuild, no engineering sprint.
A single script tag before the closing body tag. Webflow, Shopify, WordPress, Framer, or your own React app.
Ora crawls your pages and documents to build a starting knowledge base. You review it, fix anything she got wrong, and lock exact wording for pricing, refunds and claims.
Visitors talk to her. You get transcripts, intent scores and captured contacts in your inbox, Slack or CRM — so your team picks up warm.
What changes
A lot of high-intent browsing happens at eleven at night and on Sunday afternoon. Those visitors currently meet a form.
Every conversation is a transcript of what real buyers were confused about. A content roadmap you didn't have to guess at.
Your team opens a conversation that already covered budget, timing and the objection. No discovery call to find out it's a bad fit.
People say far more out loud than they'll type into a box. Longer answers mean better qualification and a clearer picture of intent.
She answers in the visitor's language from one knowledge base. Useful the moment your traffic stops being from one country.
You lock the exact wording for pricing, guarantees and claims. She can't improvise on the things that get companies in trouble.
Where it pays off
Considered purchases, where somebody has to be convinced before they commit. A twenty-dollar t-shirt doesn't need a conversation. A twenty-thousand-dollar install does.
Long consideration, technical objections, a survey to book at the end.
Will it work on a north-facing roof?
Nervous first-timers who want reassurance before they'll pick up the phone.
How much downtime after the treatment?
Availability, floor plans, payment terms, viewings — asked at midnight.
What's still available with three bedrooms?
Fit, integrations, security review, procurement. Long questions, short patience.
Do you support SSO on the mid tier?
Legal, accounting, consulting — where the first question is always "do you handle my situation?"
Do you take cases outside the state?
Entry requirements, funding, start dates, and whether it's worth it.
Can I do this part-time while working?
Fair questions
It would, if she shouted. Ora never auto-plays audio, never opens on load, and never blocks the page. She sits quietly at the bottom of the screen and waits to be clicked. The visitor starts the conversation, every time.
She answers only from the knowledge base you approve, and you can lock exact wording for anything sensitive — pricing, guarantees, refunds, regulated claims. Outside that, she says she'll find out and hands the question to a human. The demo at the top of this page does exactly that if you push it off-topic. Try it.
Some won't — at a desk, on a train, in a shared office. So typing works identically: same brain, same answers. Voice is the invitation, not the requirement. In practice the orb is what makes people stop; whether they then speak or type is up to them.
Then you already know most conversations start after hours and end in "we'll get back to you." Live chat is staffed and reactive; Ora is neither. She runs when nobody's there, and her job is the booking, not the ticket. Plenty of customers keep both and route to a human the moment one is free.
One script tag to install, then an hour or so reviewing what she learned from your site and tightening the wording. After that it's maintenance only — usually adding an answer when you notice a question she couldn't handle, which she flags for you.
Conversations belong to you. Visitors are told up front they're speaking with an AI, retention is yours to configure, and any conversation can be deleted on request. Nothing is used to train a shared model.
These slots are deliberately empty. We'd rather show three honest numbers from a real customer than borrow someone else's statistic — so nothing goes here until it's yours.
"Customer quote goes here — what changed, in their words, with a number attached if they have one."
"Second quote — ideally from a different industry, so the reader can find themselves in one of them."
"Third quote — the sceptic who didn't expect it to work. The most persuasive one you'll ever publish."
FAQ
Any site where you can add a script tag: Webflow, Shopify, WordPress, Squarespace, Framer, Next.js, or a hand-rolled site. There's no plugin to install or keep updated.
Reading your site takes a couple of minutes. Reviewing what she learned and tightening the wording takes most teams under an hour. Same-day launch is normal.
Pricing scales with conversation volume, so we quote it against your actual traffic rather than publishing a number that's wrong for most people. Book a walkthrough and you'll leave with a figure.
The embed loads after your page and renders on the GPU, dropping its own resolution if a device struggles. It pauses entirely when the tab is hidden or she's scrolled out of view. On a device with no WebGL she falls back to a static mark rather than breaking.
Your inbox, your Slack, or your CRM via webhook — HubSpot, Salesforce, Pipedrive and anything that accepts a POST. Each one carries the transcript, an intent score and any contact details from the conversation.
She's a real button: keyboard reachable, focus-visible, labelled for screen readers, and her state is announced as it changes. Typed input covers anyone who can't or won't use voice, and the animation respects reduced-motion settings.
Get started
Twenty minutes. We point Ora at your site live on the call, you ask her your customers' hardest questions, and you decide from there.