Tampa Forge

Chatbots on WordPress

Is a chatbot worth it on your WordPress site?

Often, no. If your site gets thirty visitors a day, a clear FAQ page and a working contact form will beat a chatbot every time. When one does earn its keep — high enquiry volume, repetitive questions — build it as a WordPress plugin trained on your own content, not a rented widget that guesses.

The Two Columns

When a chatbot helps — and when it's a mistake

Two honest cases for, two honest cases against. Most businesses fall clearly on one side once they read all four.

Worth it if…

Leads arrive when you're closed

If people browse your site at night and on weekends — and your competitor's phone rings at 8am before yours — an assistant that answers questions and takes a name, number, and job description at 9pm is doing real work. For trades, clinics, and services where the first responder wins the job, after-hours capture alone can justify the cost.

Worth it if…

The same questions eat your day

Do you take my insurance? Do you service my zip code? How much is a typical kitchen? If your phone time is mostly the same ten questions — and they have real, stable answers — a bot trained on those answers frees your humans for the calls that need one. Booking triage counts too: sorting "new bathroom remodel" from "my sink is leaking right now" before anyone picks up.

A mistake if…

It's hiding thin content or the phone number

If the honest answer to "why add a chatbot" is that the website doesn't answer anything itself, fix the website — putting a chat wall in front of missing content just makes visitors work for the disappointment. And if your customers are the kind who want to call — many are — a bot that buries the number costs you the exact people readiest to pay.

A mistake if…

It's generic and knows nothing about you

The bots that made everyone hate bots are the ones that know nothing: they greet warmly, understand little, and end every exchange with "please call during business hours." A chatbot that can't answer your customers' actual questions isn't a smaller version of a good one — it's an apology generator, and every conversation it fumbles is a customer who tried to reach you and got a machine shrug.

The Two Routes

DIY widget or custom-trained assistant, honestly

We build the custom kind, so weigh this accordingly — but here's both routes with real numbers in typical-range terms, including the route where you don't hire us.

Route one — DIY

Off-the-shelf chat widgets

Tidio, Chatbase, and similar tools: paste a script tag, point the bot at your site or upload documents, and you're live in an afternoon. Typical range runs from free tiers to roughly $20–$150 a month depending on features and volume. Genuinely fine for simple FAQ duty.

Route one's limits

Where widgets hit the rail

The bot only knows what your pages say, follow-up on captured leads is manual, and connecting it to your scheduler or CRM ranges from clunky to impossible. Quality varies with the plan — the cheap tiers are often exactly the generic bots that annoy people.

Route two — Custom

An assistant trained on your business

Built on the same models behind ChatGPT and Claude, grounded in your real information — services, pricing policies, service area, the answers you'd give on the phone — and wired into your actual tools, so a captured lead lands in your CRM or booking calendar, not just an email. This is part of our AI integration services — see what adding ChatGPT or Claude to your website actually involves — scoped and quoted fixed.

Route two's price

Typical custom costs, stated plainly

Typically a one-time build in the low-to-mid four figures depending on integrations, plus modest monthly usage costs — usually tens of dollars, not hundreds. The honest math: if it captures a handful of jobs a year you'd otherwise have missed, it's paid for itself. If it wouldn't, we'll tell you to skip it.

How this reaches your site

On WordPress, this is plugin work

Every AI feature worth having on a business website ends up as code running on your site. On WordPress that means a custom plugin — which is how you keep your API keys server-side, your costs capped, and your data yours.

Control

Your keys stay on your server

A plugin holds credentials server-side. Pasting a third-party script into your theme hands your traffic and your data to someone else.

Cost

Caps and caching you set

Custom code lets you cache answers and cap spend. Subscription AI plugins bill per seat or per message whether or not anyone uses it.

Fit

Trained on your content

A custom plugin can feed the model your actual pages, products, and policies — not a generic web scrape.

Own

No subscription dependency

Built once, yours to keep. When the vendor raises prices or shuts down, your site doesn't care.

Wondering whether a chatbot is worth it?

Tell us your enquiry volume and the questions you answer most. We'll tell you honestly whether it's worth building — and scope it if it is.

No ransom required. First consultation is free.