Skip to content

Website Embed

Website Embed adds a small AI Front Desk workflow bubble to your website. Visitors can open it, ask questions, share contact details, and create a clearer handoff for the business owner.

The workflow runs through Tropikal. Your website only loads the bubble. The persona, knowledge, capabilities, conversations, and handoffs stay managed in the dashboard.

What visitors see

  • A floating chat bubble on the website.
  • A short AI disclosure near the message box.
  • Answers based on approved knowledge and persona instructions.
  • Follow-up questions when the workflow needs a name, contact method, service interest, urgency, or preferred time.

The embed should feel like part of the site, but it should not pretend to be a human. Keep the disclosure visible and keep sensitive information out of chat unless it is needed for the request.

What the owner gets

For a front desk workflow, the goal is not just another chat window. The owner should receive a useful next step:

Visitor interactionOwner outcome
Asks a common questionThe visitor gets an immediate answer from approved knowledge.
Shares interest in a serviceThe workflow asks for the details needed to follow up.
Provides contact detailsThe lead includes contact method, interest, timing, and transcript context.
Requests something uncertainThe workflow can say what is missing instead of inventing an answer.
Needs human reviewThe conversation remains available for owner handoff.

Before you embed

Create and test the workflow first:

  1. Create an AI Front Desk workflow with a clear job.
  2. Add approved knowledge, such as FAQs, service descriptions, policies, or site copy.
  3. Test the workflow in the dashboard with real customer questions.
  4. Confirm the workflow asks for lead details before promising a booking or follow-up.
  5. Connect owner handoff channels only after the basic chat works.

If the workflow answers too generally, improve its knowledge before adding it to a live website.

Add the website bubble

In the workflow dashboard:

  1. Open the workflow.
  2. Open the website embed or output channel settings.
  3. Add the websites where the bubble is allowed to appear.
  4. Create or rotate the install code.
  5. Copy the full install snippet shown by the dashboard.
  6. Add the snippet to your website where custom scripts are allowed.
  7. Publish the site and open the live page.
  8. Click the bubble and send a short test message.

The full install code is shown only when it is created or rotated. Keep it private. If it is exposed in the wrong place, rotate it and update the website.

Test after installing

Run a short test before sending traffic to the page:

TestExpected result
Open the websiteThe bubble appears once, usually in the bottom-right corner.
Click the bubbleThe chat opens without leaving the page.
Ask a known FAQThe answer uses approved knowledge.
Ask for a bookingThe workflow asks for the details needed for handoff.
Close and reopenThe widget closes cleanly and reopens normally.
Check mobileThe chat fits the screen and controls are not clipped.

Common issues

IssueFirst check
Bubble does not appearConfirm the install snippet is present on the published page.
Chat says it is unavailableConfirm the install code belongs to the same workflow and the website is allowed.
The workflow gives weak answersAdd or clean up approved knowledge, then test again.
The bubble appears twiceRemove duplicate snippets from the page or theme settings.
The wrong workflow opensReplace the snippet with the one from the correct workflow.
The code was exposedRotate the install code and update the website.

Safety expectations

  • Do not paste passwords, payment details, private operations notes, or credentials into workflow knowledge or visitor chat.
  • Keep owner review for bookings, uncertain answers, sensitive requests, and anything that changes business records.
  • Do not install old permanent keys on public websites. Use the current Website Embed install snippet from the dashboard.
  • Rotate the install code when a contractor, staging site, or old build no longer needs access.

Next: improve the workflow’s knowledge sources or review safe boundaries in Knowledge & Capabilities.