Use direct links and website embeds

Use this guide after you have created and privately tested a public experience in Shared. You will deliver it through a standalone link or website placement, confirm that visitors can use it, and avoid relying on access controls that are not present in the current sharing form.

Before you begin

• Complete the publication checklist in Publish and manage a shared experience.
• Confirm the selected AI employee is Completed and passes its private tests.
• Decide where the experience should appear and who is intended to use it.
• For Iframe or Chat Bubble, identify the person who can update your website and give them access to a safe testing page.
• Plan tests for a private browser window, a phone-sized screen, and a wider screen.
• Record where each link or installation is used so you can update or remove it later.

Steps

1. Open Shared

Open Shared and select the existing experience. Confirm its public name, employee, appearance, voice, lead settings, and connected actions before copying or installing anything.

2. Choose Direct Link, Iframe, or Chat Bubble

Use the method created for the experience:

• Direct Link opens a standalone public conversation page.
• Iframe places the experience inside a page on your website.
• Chat Bubble adds a floating conversation button to a website.

A Presenter employee cannot currently use Chat Bubble. If you need a method that was not selected at creation, create a replacement shared experience; the method cannot be changed later.

3. Copy and test the Direct Link

Copy the current link from Shared and open it in a private browser window. A visitor should be able to open it without signing in to Aivah.

Test the opening message, expected and unexpected questions, voice where enabled, human handoff, lead form, and every permitted connected action. Do not treat possession of the link as verified identity.

4. Give the exact Iframe installation text to the website owner

Copy the installation text provided by Aivah. Send it through your organization's approved channel to the person who manages the website. Do not rewrite it, add private values, or paste it into a normal visitor conversation.

Ask the website owner to install it on a test page first. Check the experience at narrow and wide widths and make sure the surrounding page does not hide the conversation controls or consent wording.

5. Give the exact Chat Bubble installation text to the website owner

For a non-Presenter employee, copy the current Chat Bubble installation text and follow the same test-page process. Check that the floating button is visible without covering important website controls and that opening and closing it works at different screen sizes.

6. Test text, voice, forms, and actions separately

Run at least one controlled test for each enabled path:

1. A text conversation.
2. A voice conversation, when available.
3. A lead submission, when enabled.
4. A human handoff request.
5. Each connected action using non-sensitive test data.

Confirm where each result appears. If a connected action changes outside information, verify the intended confirmation appeared before it ran.

7. Launch and monitor the entry point

After the test page passes, place the experience on its intended page or share the Direct Link with its intended audience. Record the launch date and the pages, messages, or materials that contain the entry point.

Review conversations, leads, connected-action results, and usage after launch. Treat a surprising result as a reason to pause the placement and retest, not as proof that the same result will correct itself.

8. Replace or remove an entry point

When you need a different sharing method, create and test a new shared experience first. Update every link and website placement, confirm the replacement, then remove the old experience from Shared and ask the website owner to remove the old installation text.

Expected result

The Direct Link, Iframe, or Chat Bubble opens the intended shared experience without an Aivah sign-in. The experience remains usable on the screen sizes you tested, displays the intended consent and handoff information, and performs only the connected actions approved for visitors.

Status meanings

Sharing depends on the selected employee's preparation status:

Status shown	Meaning	What to do
Pending or Processing	The employee or a source is still being prepared.	Wait; do not launch the entry point for important work.
Completed	Preparation finished.	Run private and visitor tests before launch.
Failed	Preparation needs attention.	Open the employee in Agents, correct or replace the source, and retry.

The current guide does not define a separate delivery-status label for a link or website installation. Verify delivery by opening and testing the actual visitor entry point.

Usage credit impact

Opening a page is not a reliable measure of usage-credit impact. Visitor conversations, voice, and supported actions may use credits depending on the account and selected features. This article does not publish a fixed rate. Use the current workspace balance and Insights to monitor activity after launch.

Information stored or shared

• A Direct Link can be forwarded, copied, or opened by someone other than the original recipient.
• An Iframe or Chat Bubble is delivered through the website where it is installed; the website owner controls the surrounding page.
• Conversation activity, lead submissions, and supported results may be available to the Aivah account in Insights.
• Connected outside services receive the information required for an approved action. Do not include secret connection values in website installation text or visitor messages.
• Keep your own inventory of the pages and materials that contain each public entry point.

Limits and permanent actions

• The current sharing form does not provide a visitor password, expiry date, or website-domain restriction. Do not claim that an entry point is restricted unless separate controls have been implemented and verified outside Aivah.
• The sharing method cannot be changed after creation. A different method requires a new shared experience.
• A Presenter employee cannot currently use Chat Bubble.
• Removing a shared experience makes its old links and website placements unavailable. Update every known location before removal.
• Deleting information, sending messages, making bookings, or changing records through a connected service can have lasting effects. Use confirmation and human review before those actions run.
• Installation and layout can differ by website. Use the exact installation text from Aivah and test the real page; do not promise compatibility without that test.

Common problems and recovery

A Direct Link does not open. Confirm the share still exists, the employee is Completed, and the copied link is current. Test it in a private browser window.

The Iframe or Chat Bubble does not appear. Ask the website owner to compare the installed text with the current text in Shared. Confirm it was placed on the intended page and that the site update was published.

The placement covers website controls. Move it on the website or adjust the surrounding page with the website owner, then retest at phone and wide widths.

Visitors see the wrong configuration. Open the experience from Shared and confirm the saved employee, appearance, voice, form, and actions. Update what is available and retest every entry point.

A method needs to change. Create a new shared experience with the correct method, test it, replace each old entry point, and only then remove the old experience.

A connected action behaves unexpectedly. Pause promotion or remove the website placement, limit the action, strengthen confirmation instructions, and run a safe private test before relaunching.

Next step

Before collecting visitor information or allowing outside actions, follow Lead capture, consent, and public actions. Use Troubleshoot Aivah if the employee, voice, or website placement remains unavailable after these checks.