Frontend Chatbot Setup

The frontend chatbot is the public-facing chatbot that appears on your site for visitors. Setting it up in Aimogen is a configuration process: you decide where it appears, who sees it, and how it behaves. There is no shortcode-only mode by default and no automatic global embed unless you enable it.

This guide covers the exact, real behavior of the frontend chatbot.

---

Prerequisites #

Before setting up a frontend chatbot, you must have:

• at least one chatbot created
• an AI provider configured and working
• a persona defined for the chatbot

If the chatbot itself is not functional, frontend placement will not work.

---

Where Frontend Setup Happens #

Frontend visibility is configured inside the chatbot settings, not globally.

Path:

Aimogen → AI Chatbot → Global Chatbots

---

Enabling Frontend Display #

A chatbot does not appear on the frontend by default.

To show it on the site, you must:

• enable frontend display for that chatbot
• define at least one visibility rule

Without visibility rules, the chatbot remains inactive.

---

Visibility Rules (Core Concept) #

Frontend chatbots are shown based on rules, not assumptions.

Common rule types include:

• site-wide (all frontend pages)
• specific pages
• specific posts
• specific post types
• categories or taxonomies
• user roles
• device types
• languages
• operating systems
• user agents

Rules are evaluated on page load. If the conditions match, the chatbot is rendered.

You can combine multiple rules to fine-tune behavior.

---

Site-Wide Chatbot (Most Common Setup) #

To display a chatbot everywhere on the frontend:

• enable frontend display
• set visibility to “all pages”
• save the chatbot

This is the simplest configuration and ideal for:

• support bots
• general assistants
• onboarding helpers

---

Page- or Section-Specific Chatbots #

You can limit a chatbot to:

• specific pages
• specific posts
• specific post types

This allows you to run:

• a sales chatbot only on product pages
• a documentation bot only on docs pages
• a lead bot only on landing pages

Multiple chatbots can coexist on different sections of the site without conflict.

---

User-Based Visibility #

Frontend chatbots can be shown or hidden based on:

• logged-in vs guest users
• specific user roles

This is useful for:

• showing a support bot only to customers
• hiding chatbots from admins
• running internal bots for logged-in users only

---

Placement and Layout #

Frontend chatbots are rendered as:

• floating widgets
• fixed-position chat windows
• embedded UI elements (depending on configuration)

You can control:

• position (left/right)
• spacing
• open/closed default state
• visual behavior

Placement settings affect only that chatbot.

---

Styling and Branding #

Each frontend chatbot can be styled independently.

You can control:

• colors
• fonts
• avatars
• icons
• button appearance

Styling is separate from persona behavior. Changing visuals does not change how the chatbot responds.

---

GDPR and Consent (Frontend Only) #

If enabled, frontend chatbots can:

• require GDPR or privacy consent before interaction
• block input until consent is given
• display custom consent messages

This applies only to frontend usage. Backend/admin chat is unaffected.

---

Frontend Behavior and Limits #

Frontend chatbot usage:

• respects Aimogen usage limits
• respects provider rate limits
• can be logged (if enabled)
• fails gracefully if limits are reached

If a provider error occurs, the chatbot shows an error message instead of silently failing.

---

Testing the Frontend Chatbot #

After saving settings:

• open a page where the chatbot should appear
• test as a logged-out user
• test as a logged-in user (if relevant)
• test on mobile and desktop

If the chatbot does not appear, check:

• visibility rules
• caching or CDN behavior
• user role conditions

---

Common Frontend Setup Mistakes #

• forgetting to enable frontend display
• adding no visibility rules
• conflicting rules between chatbots
• testing while logged in as admin only
• page caching hiding dynamic elements

Most “chatbot not showing” issues are rule-related.

---

What Frontend Setup Does Not Do #

Frontend setup does not:

• change chatbot behavior or intelligence
• affect backend chat usage
• override persona rules
• auto-collect leads
• enable embeddings automatically

It only controls where and when the chatbot appears.

---

Summary #

Frontend chatbot setup in Aimogen is rule-driven and per-chatbot. You enable frontend display, define visibility conditions, choose placement and styling, and test. There is no global frontend chatbot unless you configure one, and no chatbot appears without explicit rules. This keeps frontend behavior predictable, controlled, and scalable across complex sites.