WordPress integration

Add an AI website assistant to WordPress

Train InsertChat on selected WordPress pages, install the website assistant, test answers, capture leads, and hand conversations to your team.

Review gate: this route remains noindex until a live provider test and customer-safe product screenshot are attached.

Channels

Where it works

AI website assistant; the same workspace may also configure a receptionist

Authentication

How access is granted

Public-page ingestion plus the documented WordPress installation or plugin path.

Repository evidence

Review status

Curated page and installation contracts reviewed 2026-08-17

Connection type:
Marketplace plugin and public-source import
Owner:
Product Integrations
Last tested:
Pending live provider verification
Permissions:
Minimum enabled read and write actions listed on this page; exact provider scopes require live verification.

Changelog: 2026-08-17 — Curated page and installation contracts reviewed 2026-08-17

Request integration support

Data access

Reads

What InsertChat reads

  • Selected public WordPress pages, posts, policies, and documents approved as sources
  • Only URLs included during source review and refresh
  • No private wp-admin or authenticated visitor data by default

Writes

What InsertChat writes

  • Website assistant embed configuration through the documented installation path
  • No WordPress post, page, order, or user mutation in the basic website-assistant workflow
  • Lead or booking writes occur only through separately connected tools

Working workflow

One reviewed path from conversation to outcome

  1. 1A visitor opens the assistant on the WordPress site.
  2. 2InsertChat answers from the selected maintained WordPress content.
  3. 3The visitor continues into a configured lead, booking, or support outcome.
  4. 4A person receives the conversation context when handoff is required.

Setup

  1. 1Create a preview from the public WordPress site URL.
  2. 2Review selected pages and remove stale, duplicate, or private sources.
  3. 3Install the documented widget or plugin path and map the intended assistant.
  4. 4Test desktop, mobile, consent, answer quality, lead capture, and human handoff.

Limitations

  • The basic WordPress path does not imply permission to edit site content or WooCommerce records.
  • Theme, cache, consent, optimization, and security plugins can affect widget loading.
  • Source refresh and regression testing are required when important WordPress content changes.

Troubleshooting

  • Confirm the public site URL, selected sources, widget mapping, and published installation.
  • Check cache, consent, optimization, and content-security rules when the widget does not load.
  • Re-test answer sources after a WordPress content or permalink change.