- What the Aimogen Chatbot Is
- Where the Chatbot Can Run
- Chatbot Personas
- Multiple Chatbots, One Site
- Conversations and Persistence
- Real-Time and Voice Chat
- Provider and Model Control
- Context and Knowledge
- Rules, Triggers, and Workflows
- GDPR and Privacy Controls
- Lead Collection
- Styling and Appearance
- Logging, Limits, and Safety
- What the Aimogen Chatbot Is Not
- Typical Use Cases
- Summary
The Aimogen Chatbot is a fully integrated AI chatbot system for WordPress that can run on the front end, back end, or both. It is not a demo widget or a single-use chat box. It is a configurable, extensible chatbot platform designed to work with multiple AI providers, multiple models, and multiple use cases at the same time.
The chatbot is tightly integrated with Aimogen’s AI engine, limits system, logs, and provider handling.
What the Aimogen Chatbot Is #
The Aimogen Chatbot allows visitors or users to interact with AI through a conversational interface embedded in your site.
It can:
- answer questions
- provide support-style responses
- act as a sales or lead assistant
- work as a knowledge base interface
- behave as a persona-driven assistant
- operate in real time (text and voice)
The chatbot is not hardcoded. Almost every aspect of its behavior is configurable.
Where the Chatbot Can Run #
The chatbot can be deployed in multiple contexts:
- Front-end (public-facing pages)
- Back-end (admin / playground usage)
- Globally across the site
- Conditionally (based on rules)
It does not require a single global placement. You can control where and when it appears.
Chatbot Personas #
A core concept of the Aimogen Chatbot is the persona.
A persona defines:
- name
- role
- behavior
- system prompt
- avatar
- tone and attitude
Each chatbot instance can use a different persona. This allows you to run:
- a support bot
- a sales bot
- a technical assistant
- an educational tutor
on the same site, without overlap.
Multiple Chatbots, One Site #
Aimogen supports multiple chatbot instances.
Each chatbot can have:
- its own provider and model
- its own persona
- its own rules
- its own appearance
- its own workflow logic
Chatbots are isolated from each other. One chatbot failing or changing does not affect the others.
Conversations and Persistence #
The chatbot supports:
- persistent conversations
- conversation switching
- conversation history
Users can:
- continue previous conversations
- start new conversations
- return later and resume
This works similarly to modern AI chat interfaces and is optional depending on configuration.
Real-Time and Voice Chat #
Aimogen supports real-time chat modes.
Depending on configuration and provider:
- users can type messages
- users can speak to the chatbot
- the chatbot can respond with voice output
Real-time mode prioritizes low-latency models and streaming responses.
Provider and Model Control #
The chatbot uses the same provider system as the rest of Aimogen.
You can:
- choose a provider per chatbot
- choose a model per chatbot
- switch models without rebuilding the chatbot
- mix providers across different bots
Fast models are typically used for chat, but this is fully configurable.
Context and Knowledge #
The chatbot can be enhanced using:
- embeddings
- uploaded documents
- site-specific knowledge
- predefined system instructions
This allows the chatbot to:
- answer questions about your business
- reference internal documentation
- stay on-topic
- avoid hallucinating unrelated content
Knowledge enrichment is optional and configurable.
Rules, Triggers, and Workflows #
The chatbot supports rule-based behavior.
You can define:
- triggers based on user actions
- conditional responses
- scripted message flows
- actions taken when certain messages are detected
This allows combining AI responses with deterministic logic, such as:
- showing predefined messages
- collecting user data
- ending conversations
- modifying AI behavior dynamically
GDPR and Privacy Controls #
The chatbot includes GDPR-aware features.
You can:
- require consent before chatting
- block usage until privacy notice is accepted
- control data retention
- restrict logging
These features are optional but important for compliance-focused sites.
Lead Collection #
The chatbot can be instructed to collect:
- email addresses
- names
- phone numbers
- other structured data
Collection behavior is controlled via prompts and rules, not hidden logic.
Nothing is collected silently.
Styling and Appearance #
The chatbot is fully stylable.
You can control:
- colors
- layout
- position
- icons and avatars
- iframe or native embed mode
Styling is independent per chatbot instance.
Logging, Limits, and Safety #
Chatbot interactions:
- respect Aimogen usage limits
- are logged (if enabled)
- follow provider rate limits
- fail gracefully if limits are reached
If a provider fails, the chatbot reports the issue instead of silently switching behavior unless explicitly configured otherwise.
What the Aimogen Chatbot Is Not #
The chatbot is not:
- a fixed demo widget
- a single global bot
- a black-box SaaS embed
- limited to one AI provider
- automatically trained on your site without consent
It is a configurable AI interface, not an autonomous system.
Typical Use Cases #
Common chatbot deployments include:
- customer support assistants
- sales pre-qualification bots
- onboarding helpers
- documentation search interfaces
- educational tutors
- internal admin assistants
The same site can use multiple bots for different roles.
Summary #
The Aimogen Chatbot is a flexible, multi-provider, persona-driven AI chat system built directly into WordPress. It supports multiple chatbots, persistent conversations, real-time interaction, rules, workflows, and knowledge enrichment, all while respecting WordPress permissions, limits, and privacy controls. It is designed to be configured intentionally, not enabled blindly, giving you full control over how AI conversations behave on your site.
