When the chatbot is the product, the chatbot is the page
SleekAI’s fullscreen mode renders the chatbot as an immersive, full-page surface (think ChatGPT, not a corner bubble) backed by your WordPress data through wp_posts and wp_postmeta, with your OpenAI, Anthropic, Google, or OpenRouter key.
Some chat experiences need to be the whole interface
Most chatbot placements are accessories: a bubble in the corner, an embed inside an article, a modal triggered on exit. They live next to other content because the chat is a helper, not the main act. Some experiences invert that. An AI search page on a publisher site is the chat.
An internal assistant for a logged-in team is the chat. A custom AI app built on top of your data, where the user opens a URL to talk to it, is the chat. For those, an accessory placement gets in the way; the chat has to be the page.
SleekAI’s fullscreen mode renders the chat as a dedicated full-page surface, the shape users now recognize from ChatGPT and Claude. The visitor’s role, login state, and any user variables flow into the chat, and conversations are logged into the same WordPress tables every other SleekAI bot uses.
Fullscreen is what you reach for when the chat is the destination, not the helper. Build an AI-search page at /ask scoped to all published posts. Build a member-only assistant at /assistant available only to logged-in customers with their account data mapped in.
Features
Page-as-chat
Visitors land on a dedicated URL (for example /ask or /assistant) and the chat is the entire experience, not a corner overlay.
Answers from your data
Map post titles, content, post meta, taxonomies or a WP_Query into the instruction, and the bot answers from what your site actually publishes.
Your model, your key
Use OpenAI, Anthropic, Google, OpenRouter or a compatible endpoint with your own API key. The provider bills you directly.
Where a fullscreen chatbot belongs
Internal team assistants
A logged-in-only /assistant page for staff. Maps in user data, internal SOPs, and private CPTs. The fullscreen layout suits long sessions and multi-step research better than a bubble.
Repeat questions
Answer the questions visitors ask every day from the pages and posts where you already answer them.
The next step
Put your booking page, contact form or pricing page in the instruction so the bot links visitors there when they are ready.
How a fullscreen chat page comes together
Pick a URL
Decide where the chat lives: /ask, /assistant, /tools/onboarding, or any other URL.
Set display conditions
Decide which pages, post types, roles or logged-in states show the chatbot.
Map your data
Choose the posts, fields, taxonomies or users the bot should know and reference them in the instruction.
Gate as needed
Use Display conditions to restrict access.
Why the chatbot sometimes deserves the whole page
Chat placements are a spectrum from accessory to destination. Bubbles, embeds, and popups are accessories: they help a visitor who came for something else. A fullscreen chat is a destination: the visitor came for the chat itself.
The two are not better or worse than each other; they fit different needs. The mistake is using the wrong shape for the need. A floating bubble on an AI-search page is an admission that the chat is not actually the point.
A fullscreen chat on a marketing site is a UX dead end where every visitor lands on a screen with no way out.
SleekAI ships fullscreen mode because some legitimate use cases need it and the alternative (rebuilding a chat app outside the WordPress site) is much more expensive than rendering a template. AI search pages, internal staff assistants, gated member tools, and small AI apps all benefit from owning the viewport.
Frequently asked questions
Does the fullscreen page have conversation history?
Yes. Anonymous visitors have a session-scoped history that disappears when the session ends.
What about presets and quick-start prompts?
For an AI search page, the presets might suggest popular queries; for an internal assistant, common tasks.
Is the fullscreen page mobile friendly?
Yes. The input area stays anchored at the bottom of the viewport so typing works the way users expect on phones.
How does this compare with hosted ChatGPT-style apps?
A hosted app is a separate product with separate auth, separate data, and a separate billing relationship. A SleekAI fullscreen page is part of your WordPress site: same domain, same users, same database, same backups. You keep the data, the logs, and the integration story on your own server, and the brand stays the brand of the site.
Which AI providers does it support?
OpenAI, Anthropic, Google and OpenRouter, plus custom OpenAI-compatible endpoints. You bring your own API key and the provider bills you directly.
Where does the chatbot get its answers?
From the WordPress data you map into its instruction: post titles and content, post meta, ACF and Meta Box fields, taxonomies, terms, users and user meta, or a WP_Query. Values resolve on every request.
Can it act on a visitor’s behalf?
No. A chatbot answers questions.
Can I control where the chatbot appears?
Yes. Display conditions cover post type, post, post status, post template, taxonomy, term, user role, logged-in state and WordPress conditional tags such as front page, archive, search and 404.
Pricing
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
…or get the Bundle Deal
and save €250
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
SleekAI
SleekByte
SleekMotion
SleekPixel
SleekView
SleekRank
SleekTrack