1. What the Chatbot Feature Does #
According to the documentation, the Chatbot feature is one of the core parts of Davix AI Engine. It provides:
- A floating chatbot bubble that appears across your site.
- A chat popup window that opens when the user clicks the bubble.
- A full-page chat experience via the
shortcode. - An optional login-required gate that shows an overlay to guests.
- Integration with OpenAI via a REST endpoint to send and receive chat messages.
- Optional site-search grounding to use posts/pages/products as context.
These pieces work together so that visitors can interact with an AI assistant anywhere on your WordPress site.
image IMAGE PLACEHOLDER: Screenshot of a front-end page showing the floating Davix AI chatbot bubble in the bottom corner and the chat popup open. IMAGE image
2. Where You Configure the Chatbot #
All chatbot settings live under:
- WordPress Admin → Davix AI Engine → Chatbot.
From there, the documentation mentions several tabs, such as:
- General / Style (branding and layout)
- Buttons
- Login Required
- OpenAI Integration
- Shortcode
- Advanced / Custom CSS (depending on build)
Each of these tabs controls a different part of the chatbot experience. Later articles go through them step by step.
3. How the Chatbot Appears to Visitors #
The visitor’s experience follows this flow (based on your docs):
- The floating bubble is rendered by
render_chat_widget_markup()on the front-end. - When a visitor clicks the bubble:
- The chat popup opens and shows:
- The chatbot name and logo.
- The welcome message (if set).
- The chat history for that session.
- The chat popup opens and shows:
- If you’ve created a page with
:- Visiting that page shows a full-page layout rendered by
render_fullpage_layout()andrender_fullpage_chat().
- Visiting that page shows a full-page layout rendered by
- If login_required is enabled:
- Guests see a login/signup overlay instead of the chat interface.
- The overlay texts and buttons come from your Chatbot settings.
4. How the Chatbot Talks to OpenAI #
From the technical section in your docs:
- The plugin registers a REST route:
- Namespace:
davix-ai-engine/v1 - Route:
/chat
- Namespace:
- The route is registered in
register_rest_routes()in the chatbot core class. - A permission callback (
chat_permission_check()) validates:- Nonces.
- Login status, especially when
login_requiredis ON.
- The handler
handle_chat_request():- Reads the user message and current chatbot settings.
- Optionally performs site search (if enabled).
- Sends the request to OpenAI using:
openai_api_keyopenai_modelsystem_prompttemperature
- Returns the AI’s response back to the front-end.
The front-end JavaScript for the chat popup calls this REST endpoint whenever a user sends a message.
5. Free vs Pro in the Chatbot Context #
From a user’s perspective, the chatbot is available in both Free and Pro:
- Free:
- Floating bubble + chat popup.
- Full-page chat via shortcode.
- Base theming and fixed model (
gpt-4o-mini). - Site search grounding for posts/pages (basic).
- Pro:
- Additional theming options such as human message colors.
- Model selection (not just
gpt-4o-mini). - Extended search scopes (like products).
- Telegram human handoff modes (when enabled separately).
image IMAGE PLACEHOLDER: Screenshot of the Chatbot settings main page (tabs visible: General, Buttons, Login Required, OpenAI Integration, Shortcode). IMAGE image

