> ## Documentation Index
> Fetch the complete documentation index at: https://help.agentsy.pro/llms.txt
> Use this file to discover all available pages before exploring further.

# Publish Your AI Experience

> Prepare, publish, and verify your Agentsy AI Experience before inviting visitors.

Publishing is the step that makes your AI Experience available to its intended audience. Before sharing a link, check that the assistant, website, and access settings work together as expected.

> [!NOTE]
>
> The exact controls available in your Agentsy workspace may vary by account or configuration. Use the publishing and visibility options shown in your dashboard; do not assume that saving a change automatically makes an experience public.

## Before you publish

Confirm that you have completed the essential setup:

* **Purpose:** Your AI Experience has a clear audience and a useful outcome.
* **Assistant:** Its system instructions reflect your expertise, tone, and boundaries.
* **Knowledge:** Relevant documents are uploaded, current, and tested.
* **Website:** The headline, images, logo, and calls to action accurately describe the experience.
* **Access:** You have selected the intended public or restricted access model.
* **Human follow-up:** Contact or scheduling links work, if you offer them.
* **Privacy:** Visitors have appropriate notices and are not encouraged to share unnecessary sensitive information.

For a more detailed review, see the [Launch Checklist](/getting-started/launch-checklist).

## Step 1: Review the visitor experience

Open your AI Experience website and review it as a first-time visitor would.

1. Read the headline and supporting description. Do they explain what visitors can accomplish?
2. Check that the primary button leads to the intended action.
3. Start a test conversation using a realistic question.
4. Ask a question that should be answered using your uploaded knowledge.
5. Ask something outside the assistant's scope. It should acknowledge its limits rather than invent an answer.
6. Test a situation where speaking with a person would be the appropriate next step.

> [!TIP]
>
> Test with someone who has not helped build the experience. They are more likely to notice confusing wording or unexpected steps.

## Step 2: Choose who can access it

The right visibility setting depends on your audience.

| Access model | Typical use | What to verify |
| - | - | - |
| **Public** | An experience intended for prospects, customers, or a broad audience | A visitor can reach the intended entry point and follow the expected registration flow |
| **Invite-only or restricted** | A private pilot, selected clients, or internal participants | Only authorized visitors can access the protected experience |

Registration and access restrictions are different concepts. A public experience may still require visitors to register before continuing a conversation. Registration alone does not make an experience private.

Learn more in [Public and Private Access](/create-and-configure/public-and-private-access) and [Guest Chat and Registration](/create-and-configure/guest-chat-and-registration).

> [!WARNING]
>
> Do not use an unpublished or untested access configuration to protect confidential material. Verify restricted access using a separate, unauthorized browser session before inviting participants.

## Step 3: Save and apply your publishing settings

In your Agentsy workspace:

1. Open the AI Experience you want to launch.
2. Review its website and access or visibility settings.
3. Choose the intended access model using the controls available to your account.
4. Save or apply your changes as prompted by the dashboard.
5. Open the experience's visitor-facing URL to confirm the result.

If your workspace provides a separate publishing action, complete that action before testing the live link.

> [!NOTE]
>
> A branded domain is optional for initial testing. If you are connecting your own domain, complete DNS and HTTPS verification before promoting that address. See [Custom Domains](/branding-and-website/custom-domains).

## Step 4: Test the published link

Do not rely only on an authenticated admin session. Open the link in a private or incognito browser window and check the experience from a visitor's perspective.

### Public experience test

* [ ] The URL loads without an unexpected administrator sign-in prompt.
* [ ] The logo and navigation lead to the correct public pages.
* [ ] The primary CTA opens the intended chat or guest entry point.
* [ ] Registration appears at the intended stage, if required.
* [ ] A visitor can submit a question and receive a response.
* [ ] Any scheduling or contact link opens correctly.

### Restricted experience test

* [ ] An unauthorized visitor cannot access protected content.
* [ ] An authorized participant can enter through the intended flow.
* [ ] The assistant does not disclose private material outside its intended audience.
* [ ] The invitation and sign-in instructions are understandable.

### Mobile test

* [ ] The landing page is readable without horizontal scrolling.
* [ ] Buttons are easy to tap.
* [ ] The chat input stays usable while the mobile keyboard is open.
* [ ] Long and streaming responses do not unexpectedly hide the input or jump around.

For a more comprehensive set of tests, see [Testing Your Assistant](/create-and-configure/testing-your-assistant) and [Mobile Experience](/branding-and-website/mobile-experience).

## Step 5: Share with a small initial audience

You do not have to launch to everyone immediately. A small pilot can reveal issues before a wider release.

Consider inviting a few people who represent your intended audience. Ask them:

* Was it immediately clear what the experience could help with?
* Did the assistant answer useful questions?
* Was anything confusing or inaccurate?
* Did the experience make it easier to understand your expertise?
* Was the next step clear when they wanted human assistance?

Use their feedback to improve the website, system instructions, and knowledge base.

## Step 6: Monitor and improve after launch

Publishing is a milestone, not the end of the process. Review the information available in your Agentsy workspace and look for:

* Frequently asked questions that your knowledge base does not yet cover.
* Responses that need clearer instructions or better source material.
* Points where visitors become confused or abandon the experience.
* Requests that indicate a need for direct human assistance.

Treat conversation patterns as useful signals, not definitive proof of purchase intent. Review visitor data in accordance with your privacy commitments.

See [Conversation Insights](/conversations-and-leads/conversation-insights) and [Human Handoff](/conversations-and-leads/human-handoff).

## Common publishing issues

| Issue | What to check |
| - | - |
| The visitor link redirects to sign-in unexpectedly | Confirm public versus restricted access, then test the intended guest and registration flow |
| Changes are not visible | Confirm they were saved or published, then refresh the live page |
| The custom domain does not load | Check DNS configuration, domain verification, and HTTPS status |
| The assistant gives outdated information | Review knowledge documents and retest retrieval |
| The scheduling button does not work | Verify the destination URL and test it outside your admin session |
| The mobile chat is difficult to use | Test on a physical phone and review the mobile usability guide |

If a problem persists, record the page URL, what you expected, what happened, and the steps needed to reproduce it before contacting support.

## Final launch checklist

* [ ] The experience's purpose and audience are clear.
* [ ] The assistant has been tested with realistic questions.
* [ ] Knowledge sources are accurate and current.
* [ ] The website accurately reflects what the assistant can do.
* [ ] Public or restricted access behaves as intended.
* [ ] Registration, chat, and contact flows work.
* [ ] The live URL works on desktop and mobile.
* [ ] Privacy notices and appropriate boundaries are in place.
* [ ] You have a plan to review feedback and improve the experience.

> [!TIP]
>
> Your AI Experience is ready to share when the live visitor journey works reliably for its intended audience—not simply when the configuration has been saved.

## Next steps

* [Share Your AI Website](/share-and-grow/share-your-ai-website)
* [Promote Your Assistant](/share-and-grow/promote-your-assistant)
* [Measure Engagement](/share-and-grow/measure-engagement)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.