Most chatbot tools assume one bot per site. You write one system prompt, point it at one set of data, and that bot runs everywhere. The reality of a WordPress site is that pages have radically different contexts. A docs page wants a bot that quotes documentation precisely. A pricing page wants a sales bot that qualifies leads. A blog post wants a content-aware bot that answers questions about that specific post. A WooCommerce product page wants a product expert. A logged-in member area wants a bot that respects member tier. Running one bot for all of these means compromising every single context.

SleekAI does multibot. You define as many chatbots as you want, each with its own system prompt, data mapping, model choice, and routing rules. Routing uses display conditions: post type, taxonomy term, page template, URL pattern (with wildcards), user role, login state, and custom logic via filter hooks. When a visitor lands on a page, SleekAI evaluates the conditions and loads the first matching bot. The page gets the bot whose system prompt fits the context, with no manual setup per page.

The routing layer is the part that turns 'AI chatbot' into 'AI presence everywhere on the site'. A docs section can run a docs bot that quotes the current page and related articles. The same site's blog can run a blog bot that handles questions per post. The shop runs a product bot that reads the current WooCommerce product. The member area runs a member bot that recognizes tier. Five bots, five system prompts, one plugin, automatic routing. No JavaScript to maintain, no condition trees in a dashboard.

Most chatbot products were designed for landing pages and ecommerce checkouts. They assumed a relatively narrow set of conversations per site and built around 'one bot, one prompt' as the model. WordPress sites don't fit that mold.

A real WordPress install has marketing pages, a blog, docs, a shop, a member area, and a handful of niche sections, each with completely different conversation needs. Trying to write one system prompt that works for all of them produces vague, mediocre responses everywhere. SleekAI's multibot with CMS-aware routing fixes this without making the configuration burdensome.

The routing UI uses WordPress's own primitives: post types, taxonomies, templates, URLs, user roles, login state. Anyone who knows their site can set up routing in minutes. There's no separate condition language to learn, no JavaScript to write, no per-page meta box configuration.

Each bot is independent in every meaningful way. Its system prompt, model, API key, temperature, data mapping, presets, and visual style are all separate. You can run a fast cheap model on the high-volume docs bot and a slow expensive model on the low-volume sales bot, optimizing cost and quality per context.

You can use OpenAI for one bot and Anthropic for another. You can put different teams in charge of different bots through WordPress role-based permissions on the SleekAI admin pages. The economic model amplifies the routing's value.

SleekAI doesn't charge per bot, so the marginal cost of adding a fifth or tenth bot is your time. Most sites grow into 4-6 bots over the first year as they realize each context deserves its own tuned conversation. The result is genuinely better chat across the whole site, instead of one mediocre bot pretending to handle everything.