Most small business websites are already built. They've been live for a couple of years, the theme is fine, the plugins do what they need to, and nobody wants to touch it more than necessary. "Add an AI receptionist" sounds, on first hearing, like a project that threatens all of that — a redesign, a developer, a week of testing to make sure nothing else broke. It isn't any of those things.
What actually changes on the site
Adding AIVA to a WordPress site means one script snippet, placed once, before the closing body tag — three lines of code. If you'd rather not open a theme file directly, any code-snippet plugin will do the same job. Either way, it's a single addition, not a rebuild, and it doesn't touch your theme, your page builder, or anything else already running.
That's also, deliberately, all it touches. AIVA doesn't need admin access to your WordPress install, doesn't install its own plugin that has to be kept updated against the next core WordPress release, and doesn't add a database table you have to think about during a migration. It's a script tag rendering a widget — the same category of thing as a chat tool or an analytics snippet, familiar territory for anyone who's added either of those before.
What the widget does once it's live
The widget itself is a chat window your visitors can open — but what's behind it is the actual work. Tell AIVA about your business — services, hours, prices, policies — and it answers those questions directly, in the visitor's own language if that matters to your customers. Connect a calendar and it books appointments the same way, checking real availability instead of just collecting a request. Anything it shouldn't handle alone, it hands off.
That's the part a static FAQ page can't do. A visitor landing on your site at 9 PM asking "are you open tomorrow, and can I get a slot at 11?" gets both halves answered in one conversation — the hours, and an actual booking — instead of finding the hours page and then having to call in the morning to book, by which point they may have already found someone else.
It also holds up for the questions that don't map cleanly onto a page at all. "Do you take walk-ins or is it appointment only," "is there parking nearby," "can I bring my kid along" — the kind of thing a real receptionist fields constantly and no FAQ page anticipates every version of. AIVA answers those from whatever you've told it about the business, not just from a rigid list of pre-written questions.
What AIVA needs to know about your business
Configuring the widget isn't a content-writing project. You're not drafting FAQ copy for a page — you're telling AIVA the same things you'd tell a new receptionist on their first day: hours, services and prices, cancellation policy, what makes the business different, anything customers ask often enough to be predictable. That happens in the dashboard, in plain language, and updates take effect immediately — change your holiday hours once and every conversation from that point on reflects it, without touching the WordPress site at all.
If your customers ask in different languages, that's covered without separate setup — AIVA answers in whichever of its 12 Indian languages a visitor uses, detected from how they write, alongside English.
It matches your site, not the other way around
The widget is styleable — color, position, when it should proactively greet a visitor versus stay quiet until clicked. It's meant to look like it belongs on your site, not like a third-party tool bolted onto it. What businesses actually change tends to be smaller than people expect going in — usually just a color to match the site and a corner to sit in, not a redesign.
Where visitors actually see it
When the widget appears matters almost as much as what it says once opened. A chat bubble that pops up the second someone lands on the homepage reads as pushy; one that never appears at all just goes unused. AIVA supports triggers based on behavior — time on page, which page someone's looking at, whether they've scrolled past the pricing section — so it shows up closer to the moment someone actually has a question, rather than the moment they arrive.
If your WordPress site is also a store
Running WooCommerce on top of WordPress adds order-status questions to the mix — AIVA can answer those from live order data too. That's covered separately in the WooCommerce integration if that's your setup, including how it handles the split between "questions about the site" and "questions about a specific order" inside the same conversation.
Where the conversation data goes
Worth knowing, since the widget sits on your site but isn't part of it. Conversations happen inside the widget, but nothing is stored in your WordPress database — no new table, no plugin data to back up or migrate. Every conversation, booking, and hand-off is stored on AIVA's side and shows up in your dashboard, the same as it would for any other channel the web widget runs on.
That also means removing the widget later, if you ever needed to, is just deleting the snippet. There's no data cleanup on the WordPress side, because none of it lived there to begin with.
Common questions about adding it to WordPress
A few things that come up before setup. Page builders and caching plugins don't need any special configuration — the widget is a standard script tag, and caching a page doesn't cache away a live chat widget any more than it would a support-chat tool from any other vendor. Multisite networks connect each site separately, since each one likely has different hours, services, or an entirely different business behind it. And because the snippet is small and loads asynchronously, it isn't the kind of addition that shows up as a page-speed regression the way a heavier embedded tool might.
Setup
Grab your workspace ID from the AIVA dashboard, paste the snippet, and the widget is live. Configuring what it knows and does — services, hours, calendar connection — happens in the dashboard afterward, not in code, so future updates don't mean touching the WordPress site again either.
Who this is for
Clinics, salons, consultants, local service businesses — anyone with an existing WordPress site who wants a receptionist answering after hours and on weekends, without a rebuild to get there. If the honest answer to "when did you last update the site" is "a while ago," that's fine — this doesn't require touching anything else on it. It's also a reasonable starting point for a business without a developer on staff at all; see how to add it without hiring one if that's the situation you're in.
See the full setup on the web widget page, how the embed itself was built in three lines of code, current usage rates on pricing, or start free and try it on your own site. The rest of what AIVA connects to is on the integrations page, with full details in the docs.