Ainisa Chatbot vs AI Chatbot & Support Agent

Ainisa AI Chatbot brings the power of AI-driven customer support and sales to your WordPress website. This plugin seamlessly integrates the AiNisa chatbot widget, enabling you to provide 24/7 automated assistance to your visitors. Key Features Easy Integration – Simple setup with just Integration UUID and API Key AI-Powered Conversations – Leverage advanced AI to handle customer inquiries Personalized Experience – Optional user data collection for logged-in WordPress users Secure – HMAC SHA-256 authentication for user data protection Customizable Widget – Configurable button colors, position, and margins Multi-language Support – Built-in language support No Coding Required – User-friendly admin interface How It Works Register for a free account at AiNisa.com Create your AI assistant and configure it Go to ainisa.com/business/integrations and create a new website integration Click the … button on the right of your integration, then click Get Widget Code In the opened page, find the WordPress section Install this plugin and follow the instructions shown Copy Integration UUID and API Key from the widget code page Paste them into AiNisa Chatbot > Settings in your WordPress admin Click Save – the chatbot widget automatically appears on your website Requirements HTTPS Required – Your WordPress site must use HTTPS (SSL certificate) for the chatbot to function properly AiNisa account (free to create at ainisa.com) WordPress 6.0 or higher PHP 7.4 or higher Optional Features User Data Collection – Enable personalized chat experiences by providing your Secret Key. When enabled, the plugin automatically collects: * User ID * First and Last Name * Email Address This data is securely transmitted to AiNisa for personalized responses and conversation context. Links AiNisa Website Documentation Get API Keys Manage Integrations External Services This plugin relies on the AiNisa chatbot service to provide AI-powered customer support and engagement on your website. What is the AiNisa service? AiNisa is a third-party AI chatbot platform that provides automated customer support, sales assistance, and visitor engagement through an AI-powered chat widget. The service is necessary for the core functionality of this plugin. When does this plugin connect to AiNisa? The plugin connects to AiNisa’s external service (chatbot.ainisa.com) in the following situations: On every page load (frontend): The plugin loads the chatbot widget script (https://chatbot.ainisa.com/widget.js) and displays the chat widget iframe on all pages of your website. During chat interactions: When visitors interact with the chatbot, their messages and conversation data are transmitted to AiNisa’s servers for processing and AI response generation. What data is transmitted? Data sent for all visitors: * Page URL where the chat is initiated * Conversation messages and chat interactions * Browser and device information (automatically collected by the widget, examples: cookie, browser type, version etc. ) – to securely manage privacy of chats and messages per visitor Additional data for logged-in WordPress users (optional – only if Secret Key is configured): * User ID (WordPress user ID) * First Name * Last Name * Email Address * User Hash (HMAC SHA-256 authentication token) This optional user data enables personalized chat experiences and allows the AI to provide context-aware responses based on user information. Browser Permissions The chatbot widget requests the following browser permissions to enable advanced features: Microphone access: Used only when a visitor actively chooses to record and send audio messages. The microphone is never accessed without explicit visitor action and browser permission. Audio recording only works when the visitor clicks the record button and explicitly allows their browser to access the microphone. Clipboard write: Allows visitors to copy and paste text into the chat message field when needed. This permission enables the standard copy/paste functionality within the chat interface for visitor convenience. These permissions are requested by the chat widget but require explicit visitor consent through browser permission prompts. No audio or clipboard data is accessed without visitor action and browser approval. Service Provider Information This service is provided by AiNisa: * Service Website: https://ainisa.com * Terms of Use: https://ainisa.com/en/page/12-terms-and-conditions.html * Privacy Policy: https://ainisa.com/en/page/15-privacy-policy.html * Documentation: https://docs.ainisa.com Your Responsibilities By using this plugin, you are responsible for: * Ensuring your use of the AiNisa service complies with applicable laws and regulations * Obtaining necessary user consent for data collection and transmission where required * Reviewing and accepting AiNisa’s Terms of Use and Privacy Policy * Informing your users about the use of this third-party service in your own privacy policy Privacy Policy This plugin connects to the AiNisa service (https://chatbot.ainisa.com) to display the chatbot widget on your website. When the Secret Key is configured, the following user data is transmitted to AiNisa for logged-in users: * User ID * First Name * Last Name * Email Address * User Hash (HMAC SHA-256 of User ID) This data is used to provide personalized chat experiences and is subject to AiNisa’s Privacy Policy. No data is collected or transmitted if the Secret Key is not configured.

You already know the old kind. A visitor asks a real question, the bot replies with a link to your FAQ page, and the visitor leaves. This is the other kind. Ultimo Bots puts a real AI support agent on your WordPress site. It answers from your own content, and then it does the actual work: books the meeting, looks up the order, saves the lead, and pulls you into the conversation when it matters. You describe it. It builds itself. There is no canvas to drag boxes around on. You open the builder and type what should happen, in your own words: “When someone asks about pricing, explain the plans and offer a demo call. If they want one, book it in my Cal.com and send the lead to HubSpot.” That is the entire build step. The agent is configured from that sentence. No code, no flowcharts, no developer, no agency. Changed your mind? Tell it. That is the edit step too. It doesn’t just answer. It acts. Connect the tools you already run, and the agent uses them mid-conversation: Books appointments in Cal.com, including reschedule and cancel, or hands over your Calendly link Takes payments and manages subscriptions through Stripe links. It can list, change, or cancel a subscription. Card details never enter the chat Saves and finds contacts in HubSpot, and subscribes visitors to Mailchimp with proper double opt-in Answers from your product catalog, with prices and stock, so “do you have this in blue” gets a real answer Calls your own API with your own credentials when you need something nobody else offers Captures leads inside the conversation and emails them to you the second they land Before the agent touches anything private, it emails the visitor a six-digit code and waits for it. Verified first, every time. One agent. Every channel. The same agent runs on your WordPress site, on a shareable chat link, in Facebook Messenger, Instagram DMs, Telegram, and Slack. You train it once and it shows up everywhere. Nothing to duplicate, nothing to keep in sync. It knows your business, and it will not invent Point it at your WordPress site and it reads it. Add PDFs, Word files, spreadsheets, Google Drive, OneDrive, Notion. Every answer is built from your material, and one click re-scans your site whenever it changes. When it does not know something, it says so and offers you instead. That one habit is why people trust it on a live site. It detects the language your visitor is writing in and answers in it. You configure nothing. You stay in control Write your rules in plain words and the agent holds them, even when a visitor pushes back. Watch conversations as they happen and jump in yourself with one click. The agent goes quiet the moment you start typing and picks up again when you leave. Get pinged in Slack, Telegram, Teams, or email whenever someone wants a human. Everything is included Every capability above is on every plan. Plans differ in volume, not in what your agent can do. No per-seat pricing, no per-resolution fees, no “contact sales”. Start with a free trial, then from $19 a month. Live in about two minutes Activate the plugin, answer a few questions, and your agent is on your site. That is the whole setup. External services This plugin connects to external services operated by Ultimo Bots to function. The integration is required to register your site securely and render your AI assistant. Below are the services, what they are used for, and what data is transmitted. Policies for all of them: Terms of Service: https://www.ultimo-bots.com/terms – Privacy Policy: https://www.ultimo-bots.com/privacy 1) Ultimo Bots Portal API – site registration What: https://portal.ultimo-bots.com/api/auth/wordpress/save_secret When: On plugin activation (and retried if the first attempt failed). Purpose: Register your WordPress site and exchange a site-specific identifier used for secure operations. Data sent: site_id (random UUID generated in your WordPress site), site_url (your WordPress home URL), site_secret (random secret generated in your WordPress site), and the admin user’s email, first_name, last_name (used only to prefill the onboarding form; transferred server-side, never placed in a URL). Data received: wordpress_secret_id (an internal identifier) and a one-time connect code (valid 15 minutes, single use). 2) Ultimo Bots Portal API – connect code What: https://portal.ultimo-bots.com/api/auth/wordpress/connect_code When: When you click “Connect to Ultimo Bots” in the plugin settings, and right before the one-time onboarding redirect. Purpose: Mint a fresh one-time connect code so the onboarding can be opened without any personal data in the URL. Data sent: site_id, site_secret, and the admin user’s email, first_name, last_name (prefill, server-side only). Data received: a one-time connect code. 3) Ultimo Bots Portal API – assistant lookup What: https://portal.ultimo-bots.com/api/wordpress/my_bot When: On WP-Admin page loads (throttled to once per 5 minutes), on the plugin settings page, and once daily via WP-Cron. Purpose: Fetch the ID of the assistant connected to this site, so the assistant activates automatically after onboarding. Data sent: site_id, site_secret. Data received: bot_id and its creation status. 4) Ultimo Bots Widget Configuration API What: https://portal.ultimo-bots.com/api/widget_configuration/{bot_id} When: On public page views where the assistant is displayed, and on activation to check whether an existing Bot ID is active. Purpose: Retrieve the widget configuration for your Bot ID (colors, sizes, welcome messages). Data sent: bot_id (path parameter); optionally host_url when provided by the widget for basic operational analytics. Data received: widget configuration JSON. 5) Ultimo Bots Widget Script Host – static asset What: https://robert-kloepsch.github.io/ultimo-bots-widget/dist/bundle.js When: On public page views where the assistant is displayed. Purpose: Load the widget client code. Data sent: standard CDN/HTTP request metadata (IP, user agent) as with any static asset request. Important: This plugin does not accept or store arbitrary HTML/JS/CSS from users. It only stores a Bot ID and generates safe markup internally. The widget script is properly enqueued via WordPress functions. Privacy This plugin communicates with Ultimo Bots services as described in External services. Please review: – Terms of Service: https://www.ultimo-bots.com/terms – Privacy Policy: https://www.ultimo-bots.com/privacy