Website Assistant Install

What This Does

The Website Assistant install flow puts a Bombyx assistant on a customer’s site.

Most WordPress sites should use the plugin. Custom sites can use the script tag.

Before You Start

In Bombyx, the assistant should be turned on and have a widget key.

The widget key is different from a tool connector token. It is safe to use in website install code, but it should still belong only to the site it was created for.

WordPress Install

In Bombyx, open Website Assistant, then Installation.
Download the Bombyx WordPress plugin ZIP.
In WordPress, open Plugins, then Add Plugin.
Choose Upload Plugin and select the ZIP.
Activate the plugin.
Open Settings, then Bombyx Assistant.
Paste the widget key.

The WordPress plugin can also keep public WordPress pages and posts current for training. It does not include drafts, private content, password-protected content, revisions, comments, media files, or admin-only data.

Direct Script Install

Use this path for non-WordPress sites or custom installs.

<script
  async
  src="https://bombyxlabs.com/widget/widget_key_here.js"
  data-launcher-label="Ask us">
</script>

The launcher label comes from Website Assistant settings unless data-launcher-label overrides it.

Assistant Presence

Published Assistants can show a stream of short, reviewed messages before a visitor starts a conversation. Bombyx calls these Assistant Moments. They use the Assistant’s current approved knowledge and settings, and displaying them does not make a new AI request.

Website owners control whether Presence is enabled, how often it appears, what broad topics it emphasizes, optional plain-language guidance, page-history matching, mobile behavior, and excluded paths in Bombyx. The current reviewed messages can also be shown or hidden individually, or replaced with a fresh reviewed set. WordPress uses the same server-managed settings and does not add separate controls. Any visitor interaction with the launcher, card, composer, attachment controls, or open conversation stops Presence for that browser session. If reviewed content is missing, stale, or malformed, nothing is shown.

On-Page Openers

After install, either of these opens the assistant:

<a href="#bombyx-assistant">Ask a question</a>

<button data-bombyx-open-assistant>Ask a question</button>

Property Assistant Pages

Normal Website Assistant installation does not expose Property Assistant behavior. Organizations remain in Website Assistant mode unless a Bombyx system admin enables Property Assistant mode for that organization.

After system-admin enablement, Bombyx can host an address-specific Property Assistant page for an organization. Owners configure the address, lifecycle, knowledge sources, and readiness from Assistant Settings. The public page uses the same managed assistant runtime, so it does not require a separate script installation. A property profile by itself does not enable the page or property behavior.

Property Assistant answers always distinguish owner-shared records from other context. When public-web research is enabled for that Property Assistant, it may check clearly labeled public sources when the owner records do not answer the question. Each public source includes its domain and retrieval date. Generic web research does not cover every county record system or paid database.

Authorized organization members can review Property Assistant conversations for their organization. The managed widget response reports shared_with_organization; third-party integrations should not attempt to construct Property Assistant frame tokens or source URLs. Those values are signed and issued by Bombyx.

If the AI providers are temporarily unavailable, or the property’s reviewed knowledge generation is still compiling, the managed assistant shows a separate retry status. It does not create an assistant message, a feedbackable answer, or a fake records-unavailable response.

Property source links may be temporary signed URLs. Integrations should use the returned URL unchanged and handle an expired, withdrawn, private, stale, or otherwise ineligible source as unavailable.

Common Mistakes

Using a tool connector token instead of the widget key.
Installing both the WordPress plugin and direct script on the same page.
Expecting private WordPress content to be scanned. It is intentionally skipped.