Install and troubleshoot the Pivra WordPress plugin

Current release status

Pivra AI Chatbot 1.0.1 is live in the official WordPress.org plugin directory. The directory listing and WordPress.org-generated download were verified after publication.

The direct Pivra package remains available as a manual-install fallback:

• Install Pivra AI Chatbot from WordPress.org
• Download the reviewed Pivra 1.0.1 ZIP fallback
• Requires WordPress 6.2 or later and PHP 7.4 or later
• Tested up to WordPress 7.1
• Direct Pivra ZIP SHA-256: 20da07eeb6e7ba79cd0f158bb45e47b2c86577af73342c38b12c53f41d424970

The release passed Pivra's compatibility checks and the official Plugin Check rules with zero warnings. WordPress.org repackages directory downloads, so its generated ZIP has different archive bytes while containing the same reviewed plugin files.

Before you install

You need:

1. A WordPress administrator account that can install plugins.
2. A Pivra account with a chatbot already created and Active/Published.
3. At least one trained knowledge source.

The plugin never asks for your Pivra password, a private account API key, Stripe details, or a WordPress administrator password.

Install version 1.0.1

1. In WordPress, open Plugins → Add New Plugin.
2. Search for Pivra AI Chatbot.
3. Select Install Now, then Activate.
4. Open Settings → Pivra AI Chatbot.

For manual installation, download the reviewed Pivra AI Chatbot ZIP, open Plugins → Add New Plugin → Upload Plugin, choose pivra-ai-chatbot.zip, then install and activate it.

If WordPress reports that the plugin already exists, use the normal replace-current-with-uploaded flow when offered. Do not unzip the package into a second plugin folder.

Connect your chatbot

1. In Pivra, select the chatbot you want on the site.
2. Open Chatbot → Install → WordPress.
3. Confirm the chatbot is Active/Published.
4. Select Generate setup code and copy the code while it is visible.
5. Return to WordPress → Settings → Pivra AI Chatbot.
6. Paste the code and select Connect Pivra.

The setup code expires after 30 minutes and works once. Pivra stores a one-way hash rather than the raw code. WordPress receives a site-scoped credential for connection health and disconnect operations; it cannot be used to sign in to Pivra.

Verify the live installation

After connection:

1. Open the public website in a private browser window.
2. Confirm the chat button appears once.
3. Ask a business-specific question and verify the answer comes from your trained material.
4. Submit a synthetic test lead with clearly non-customer details if lead capture is enabled.
5. Return to Pivra → Install and confirm the domain and WordPress installation show as healthy.

WordPress sends a lightweight health check approximately hourly. Check connection now runs the same check immediately.

Caches and optimisation plugins

If the plugin connects but the chat button does not appear:

• Purge the WordPress page cache, CDN cache, and host-level cache.
• Clear JavaScript optimisation or minification caches.
• Confirm https://embed.pivra.ai/popup.js is not blocked by a content-security policy.
• Temporarily exclude the Pivra script from delay-JavaScript settings, then test again.
• Confirm the chatbot is still Active/Published in Pivra.

The release matrix includes a representative caching plugin, but every theme, host, CDN, and optimisation combination can behave differently.

Duplicate chat buttons

A duplicate usually means the site still has a manual Pivra embed snippet in a theme, tag manager, script-injection plugin, or page builder.

Keep only one installation method:

• Prefer the Pivra WordPress plugin for a standard WordPress site.
• Remove the old manual snippet after confirming the plugin connection works.
• Clear all caches and reload in a private window.

Connection errors

Setup code is invalid or expired

Generate a new code in Pivra. Do not reuse a code that was already exchanged, revoked, or created more than 30 minutes ago. Five failed attempts trigger a 15-minute connection lockout.

WordPress cannot reach Pivra

The WordPress server must allow outbound HTTPS requests to https://api.pivra.ai. Ask the host to check firewall, DNS, TLS, and loopback restrictions. The plugin does not accept a custom or non-HTTPS API host.

The wrong chatbot or domain is connected

Disconnect the current installation and generate a new setup code for the intended chatbot. Site credentials are domain-bound and should not be copied between staging and production.

Remote disable, disconnect, and uninstall

• Remote disable: Disable the WordPress installation from Pivra. The plugin stops rendering after its next health check, or after Check connection now.
• Disconnect: Use Disconnect in WordPress to revoke the site connection and remove its local configuration.
• Uninstall: Deleting the plugin removes its WordPress options and scheduled health event. Pivra may retain a disabled installation record for security and operational history as described in the Privacy Policy.

Visitor conversations are handled by Pivra's hosted service and are not stored in the WordPress database by this plugin.

Still stuck?

Include the WordPress version, PHP version, plugin version, host name, connection status, and exact on-screen error when contacting Pivra support. Never send passwords, setup codes, or site-scoped credentials.