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, at first, like a project that threatens all of that: a redesign, a developer, and a week of testing to make sure nothing broke.
It isn't. Adding Aiva Chat to a WordPress site means pasting one script tag into your footer. There's no plugin to keep updated, no database changes, and no theme work. Everything about what the assistant says and does is set up in the Aiva Chat dashboard, not in WordPress.
What you get is a chat window, with an optional voice mode, that answers visitors' questions from your own business information and books appointments while you're closed. A visitor who lands on your site at 9 PM asking "are you open tomorrow, and can I get a slot at 11?" gets both answers in one conversation instead of an hours page and a promise to call in the morning.
If you're the person who looks after the site, the part you'll care about most is where the snippet goes so a theme update doesn't wipe it, and that's covered in the install steps below.
What is an AI receptionist for a WordPress site?
It's a chat widget, backed by an AI assistant, that sits on your pages and holds real conversations with visitors. It answers from the information you give it, such as services, prices, hours, and policies, and it can book appointments, collect contact details, and hand off to a person.
Unlike a rule-based chatbot plugin, it doesn't need a decision tree. Visitors type or speak naturally, ask follow-up questions, and get specific answers. "Do you take walk-ins, is there parking, and can I bring my kid?" is handled as one conversation.
The Aiva Chat web widget is the same assistant that can answer your phone, book appointments by text once you turn on Booking by text, and suggest replies to other texts for your staff to send, so what you teach it once applies across channels. On a WordPress site, it's added the same way on any theme or page builder.
It suits clinics, salons, consultants, law offices, and local service businesses: anyone with an existing WordPress site who wants questions answered and appointments booked outside office hours, without rebuilding anything.
How adding Aiva Chat to WordPress works
Step 1: Design the widget in the Aiva Chat dashboard
Open the Widget Builder and choose which assistant answers. Set the header title, welcome message, colours, position, font, and theme. A live preview shows desktop and phone views, so you can see how it'll look before it goes anywhere near your site.
Step 2: Add your domain to the allowed list
The widget only loads on websites you list under allowed websites. Add your domain, such as example.com, and use *.example.com if you want every subdomain included. This stops anyone else from copying your snippet onto their site.
Step 3: Copy the script tag
On the Install tab, copy the snippet. It already contains your user and assistant IDs. Each assistant has its own script, so if you switch assistants later, copy it again.
Step 4: Paste it before the closing body tag
Add the script to your theme's footer so it appears on every page. The safest route is a child theme or a code-snippet plugin. WordPress's own documentation explains that child themes let the parent theme update without losing your changes, which edits made directly to a theme file don't survive.
Step 5: Check it's working
Use the "check a website" tool in the dashboard to confirm your page is on the allowed list, then open your site and look for the chat bubble. Ask it a few real questions. The widget setup guide covers troubleshooting if it doesn't appear.
Benefits of an AI receptionist on WordPress
No plugin to maintain
Plugins need updates, can conflict with each other, and sometimes break after a WordPress core release. A script tag doesn't touch WordPress at all, so there's nothing to update, nothing to conflict, and nothing to clean up if you ever remove it.
Visitors get answers at the moment they ask
Most people browse business websites in the evening and at weekends. A static FAQ page can't answer the version of the question someone actually has. Aiva Chat answers specifically, in the visitor's language, and keeps going when they ask a follow-up.
Bookings instead of contact requests
With Google Calendar connected, website text chat checks your calendar's free and busy times, offers real open slots, and writes each booking to your calendar. The visitor leaves with a confirmed time, not a "we'll get back to you."
Updates without touching the site
Change your holiday hours or prices in the Aiva Chat dashboard and every conversation reflects it from then on. Design changes, such as a new colour, appear on your live site on the next page load. You never need to reopen WordPress to change what the assistant says.
Conversations stay out of your WordPress database
Every chat, booking, and handoff is stored on Aiva Chat's side and appears in your dashboard. Your WordPress database doesn't grow, backups don't change, and migrations aren't affected.
WordPress AI receptionist use cases
Four composite examples of the kinds of WordPress sites we see, not real customers:
The salon booking at 10 PM
Problem: A visitor on a salon's WordPress site wants a haircut on Saturday but the salon is closed. How Aiva Chat handles it: The widget answers prices and stylists' specialties, checks Saturday's open times, and books an 11 AM slot. Outcome: The salon starts Saturday with a booking that would otherwise have gone to whoever answered online first.
The clinic visitor with an unusual question
Problem: A patient wants to know if the clinic has wheelchair access and whether a parent can come into the consultation. How Aiva Chat handles it: It answers both from the clinic's notes and offers to book an appointment. Outcome: A question no FAQ page anticipated gets answered without a phone call.
The WooCommerce store with policy questions
Problem: A shopper on a WordPress store wants to know shipping times and the return window before buying. How Aiva Chat handles it: It answers store policies you've taught it. For a specific order's status, which it can't look up on its own, it collects details and hands off, or calls your own system through a custom action if you've set one up. Outcome: Pre-purchase hesitation is resolved, and order questions reach someone who can check them.
The consultant's lead capture
Problem: A consultant's site gets enquiries from people who aren't ready to book a call yet. How Aiva Chat handles it: The pre-chat form collects name and email, and Aiva Chat answers questions about services and pricing, then offers a call slot. Outcome: Every enquiry arrives with context, even when the visitor doesn't book.
Aiva Chat widget vs. chatbot plugins vs. contact forms
| Contact form | Rule-based chatbot plugin | Aiva Chat widget | |
|---|---|---|---|
| Installation | Built into most themes | Plugin install and updates | One script tag, no plugin |
| Answers open-ended questions | No | Only scripted paths | Yes, from your information |
| Books appointments | No | Sometimes, via add-ons | Yes, written to Google Calendar |
| Voice in the browser | No | Rarely | Optional voice mode |
| Data stored in WordPress | Usually | Usually | No, stored on Aiva Chat's side |
| Ongoing cost | Nothing | Free tier, then plugin licence | Included in any Aiva Chat plan; chat AI usage on your OpenAI bill |
A contact form is free, simple, and still the right choice for visitors who want to send a detailed message and wait. It's worth keeping, but it shouldn't be the only option after hours, because many people won't wait for a reply.
A rule-based chatbot plugin can work well for a small, predictable set of questions. Its weakness is anything outside the script, and it lives inside WordPress, so it needs updating like any plugin. For a deeper comparison, see why a chatbot isn't a strategy.
Aiva Chat sits above both for conversations, while staying outside WordPress itself. The trade-off is that it's a paid service and relies on your own OpenAI key for AI usage.
How to set up Aiva Chat on your WordPress site
Aiva Chat's overall setup runs through six guided steps; the website widget slots in alongside them.
Step 1: Decide what the widget should do
Pick the goal: answering questions, booking appointments, collecting leads, or all three. That decides whether you connect a calendar and turn on the pre-chat form.
Step 2: Teach Aiva Chat your business
Add your hours, services, prices, cancellation policy, and common questions. Import your existing WordPress pages, upload PDFs, or type notes. You're telling it what you'd tell a new receptionist on day one.
Step 3: Connect your calendar
Connect Google Calendar so chat bookings land on it. Each assistant writes to one calendar. Text chat checks that calendar's free and busy times before offering a slot; the widget's voice mode and phone calls check Aiva Chat's own appointment book instead, so add bookings you take elsewhere with New appointment in the dashboard.
Step 4: Design and install the widget
Style it to match your site, add your domain to the allowed list, and paste the snippet into your child theme footer or a code-snippet plugin.
Step 5: Test it like a visitor
Open your site on a phone and a laptop. Ask real questions, try to book, ask for a person, and ask something it shouldn't know. Check bookings appear in your calendar.
Step 6: Review conversations and adjust
Read web conversations in the dashboard for the first couple of weeks. Add answers for questions it struggled with, and adjust the auto-open delay if visitors seem to ignore or dismiss it.
Common mistakes when adding a widget to WordPress
Editing the parent theme directly
Pasting the snippet into a parent theme file works until the theme updates and wipes it. Use a child theme or a code-snippet plugin so the widget survives updates.
Forgetting the allowed websites list
If your domain isn't on the list, the widget won't load, and it can look like the snippet is broken. Add every domain and subdomain you use, including staging if you test there.
Popping it open instantly
A chat window that opens the moment someone lands reads as pushy. Use a delay of several seconds, or leave it closed until clicked, and watch whether engagement changes.
Launching with thin information
If you only teach it your hours, it'll say "I'm not sure" to everything else. Spend an hour adding services, prices, policies, and the questions you hear most before you go live.
Best practices for AI receptionists on WordPress
- Install site-wide through the footer so the widget appears on every page.
- Match your brand colours and pick the corner that doesn't cover your own buttons.
- Use the pre-chat form sparingly. Ask only for what you'll actually use.
- Connect your calendar so chats end in bookings, not requests.
- Keep business information current, especially hours around holidays.
- Read conversations weekly at first and fill the gaps.
- Turn on voice mode if your visitors are often on mobile.
Conclusion
For most WordPress site owners, the technical side is the easy part, and that's the main judgement worth carrying away. Ten minutes in a child theme or snippet plugin handles the install. Whether the widget earns its place depends almost entirely on what you teach the assistant afterwards.
The decision to make first is what the widget is for. If it's bookings, connect the calendar before you style anything, and remember that text chat reads your Google Calendar while voice mode works from Aiva Chat's own book. If it's lead capture, decide what the pre-chat form should ask and keep it short. A widget with no clear job ends up as a nicer-looking FAQ page.
The one caveat that catches people: the allowed websites list. If the bubble doesn't appear, check that before assuming anything is broken. For owners without technical help, our walkthrough on adding a web AI assistant without a developer covers the install in plainer steps.
Ready to put an AI receptionist on your site?
Try it on a staging copy first if you have one; add the staging domain to the allowed list and paste the snippet there. Then ask it the three questions your contact form gets most often and see whether the answers would have saved you a reply.
When it's ready for the live site, move the snippet over and keep an eye on the first week of conversations. The widget comes with every plan, Starter included at $49 a month; see plan limits for what changes between tiers.
Start your 14-day free trial with no card required, or book a demo to see the widget on a WordPress site like yours.
Posts from the people building Aiva Chat in Rajkot — how the product works, what we have learned building it, and guides for getting the most out of an AI receptionist.