Embeddable Chat Widget | FieldCamp

How FieldCamp delivers an embeddable chat assistant — through the Online Booking widget, with a configurable assistant and a knowledge base you control.

FieldCamp does not ship a standalone "chat widget" product. Instead, the conversational experience you embed on your website is part of the Online Booking widget. The same script renders both the booking flow and a chat-style AI assistant that can answer visitor questions using your own knowledge base. This guide explains where to find these settings and what is actually configurable today.

If you came here looking for instructions to install a chat-only widget, use the Adding the booking widget to your website guide. The booking widget is the host for both booking and assistant interactions.

Where chat-assistant settings live

From the FieldCamp sidebar, open Settings then Online Booking. The settings page is organised as tabs across the top:

Setup — booking page URL, booking types, payment, deploy options, embed code.
Appearance — colours and images.
Content — content overrides.
Flow — booking flow steps.
Assistant — chat assistant name, subtitle, launcher label, and composer placeholder.
Playbooks — assistant playbooks.
Knowledge — knowledge sources used by the assistant (visible to admins).

There is no separate "Chat Widget" page or "Create chat widget" flow. Everything is configured on the single Online Booking widget that is provisioned for your workspace.

What you can configure on the Assistant tab

The Assistant tab controls how the embedded assistant presents itself. The fields are:

Assistant name — the display name the visitor sees.
Subtitle — a short line shown under the name.
Launcher label — the text on the chip used to open the assistant.
Composer placeholder — the placeholder text inside the message input.

A live preview on the page reflects your changes before you save. Other behavioural controls (tone, allowed topics, fallback behaviour) are not exposed as form fields on this tab today.

Training the assistant with knowledge sources

Admins can open the Knowledge tab to feed source material to the assistant. After turning on Enable knowledge base, you can add sources in three ways via the Add menu:

Upload document — accepted file types are .pdf, .doc, .docx, and .txt.
Import website — preview and import a URL with an optional title and content override.
Add text — paste raw text with a title.

Each source appears in a list with a status indicator (ready, processing, queued, or failed) and a chunk count. The row menu lets you Review, Re-index, Activate / Deactivate, or Delete a source. Filter chips at the top of the list let you narrow by All, Document, Website, or Text.

When you open a source for review, the editor includes a Save & Retrain action that re-runs ingestion against the edited content.

Start small. A handful of focused, high-quality sources usually produces better answers than dumping every page on your site into the knowledge base.

The embed snippet is generated on the Setup tab under Deploy options. There are four embed modes, each producing a slightly different snippet:

Inline — renders into a target div you place in the page.
Full page — opens the booking flow on its own page.
Floating — a fixed-position launcher button. Position can be Bottom right or Bottom left. The button text and colour are configurable on the same panel.
Inline button — a button you place anywhere; clicking it opens the widget.

The script is served from your workspace origin and is booking-widget.js. A typical inline embed looks like:

<div id="fieldcamp-booking"></div>
<script async src="https://YOUR-FIELDCAMP-ORIGIN/booking-widget.js" data-token="YOUR_TOKEN" data-mode="inline" data-target="fieldcamp-booking"></script>

The data-token value is generated when your widget is saved; before save, the Setup tab tells you a token has not yet been generated.

The widget script is hosted at /booking-widget.js on your FieldCamp workspace origin, not on a separate domain. Copy the snippet directly from the Setup tab so the origin and token are correct for your account.

What is not in the product today

To keep this guide grounded in the current release, the following are not configurable in the UI as of writing:

No separate "chat widget" menu, page, or "Create chat widget" flow.
No persona / allowed topics / fallback action / lead-capture field selector on the Assistant tab.
No "History" tab listing past assistant conversations inside Settings → Online Booking.
No "Add to knowledge" action surfaced on individual assistant answers.
No file size or content type limits documented in the UI for visitor-side uploads.
No language selector on the Appearance tab.

If any of these arrive in a future release, they will be documented separately.

Troubleshooting

The widget does not appear on my site

Confirm the snippet from the Setup tab is present on the page, hard-refresh, and check the browser console for blocked scripts. Aggressive caches and Content Security Policy rules are the usual culprits.

The assistant gives outdated answers

Open the Knowledge tab, find the source, and use Re-index from the row menu. For text or website sources you have edited, opening the source and using Save & Retrain re-runs ingestion on the new content.

A knowledge source is stuck or failed

Each row shows a status dot. If a source is marked failed, the error is shown in the row metadata. Use Re-index to retry; for documents, re-uploading the file is a clean reset.

FAQs

Is there a separate "chat widget" product? No. The chat-style assistant is part of the Online Booking widget. One embed script handles both booking and assistant interactions.

Where do I change the assistant name visitors see? Settings → Online Booking → Assistant tab, Assistant name field.

Where do I add knowledge for the assistant? Settings → Online Booking → Knowledge tab (admin only). Use the Add menu to upload a document, import a website, or paste text.

What file types can I upload as knowledge? The Knowledge uploader accepts .pdf, .doc, .docx, and .txt.