Skip to main content

​
Guest Chat and Registration

Guest chat gives visitors an opportunity to experience your assistant before committing to a full conversation. Registration helps identify people who want to continue engaging with your expertise. The goal is a smooth visitor journey: demonstrate value, explain the next step, and make registration straightforward.
Guest chat availability and the exact registration flow depend on how your Agentsy experience is configured. Use the options visible in your account as the source of truth.

​
Understand the visitor journey

A typical guest-enabled experience has three stages:
  1. Discovery: A visitor arrives at your branded AI Experience website.
  2. Preview: The visitor opens the guest chat and tries the assistant, subject to any configured limits.
  3. Registration: When the visitor wants to continue—or reaches a registration requirement—they are prompted to create an account or sign in.
Some experiences require registration before any chat begins. Others allow a limited guest preview. Guest access and public visibility are separate settings: a publicly accessible landing page does not necessarily mean visitors can chat without signing in.

​
Choose when visitors should register

Consider what you want visitors to experience before you ask for their information.
Do not describe a guest preview as anonymous or private unless you have verified how your deployment handles visitor data, analytics, and session storage.

​
Configure the experience

  1. Sign in to your Agentsy administration workspace.
  2. Open the AI Experience you want to configure.
  3. Review the available access, registration, and guest chat options. The names and locations of these controls may differ by account or product version.
  4. Choose the flow that matches your intended audience and access requirements.
  5. Save your changes, then open the visitor-facing website in a private browsing window to test the result.
If you cannot find a guest chat option, do not assume it is enabled. Check your account’s available features or contact support.

​
Write a clear registration transition

The transition should tell visitors why they are being asked to register and what happens next. Example:
Want to keep exploring? Create an account to continue the conversation with this AI Experience.
Keep the message brief and accurate. Avoid promising that earlier guest messages will be preserved unless you have tested and confirmed that behavior in your deployment.

​
Test the full guest-to-registration flow

Use a private browsing window so an existing login does not affect the test.
  • The main AI Experience landing page loads correctly.
  • The guest-chat call to action opens the expected page.
  • The assistant responds within the intended guest-access limits.
  • The registration or sign-in prompt appears at the expected point.
  • The sign-up and sign-in links lead to the correct tenant or branded domain.
  • After registration, the visitor reaches the expected destination.
  • Guest messages are preserved only if that behavior is supported and confirmed.
  • Clicking the brand logo returns visitors to the intended landing page, rather than unexpectedly redirecting them to sign-in.
  • On mobile, the chat input, registration controls, and navigation remain usable.
  • Private or invite-only content cannot be accessed through the guest flow without authorization.
Repeat the test with three states: a new visitor, an already registered visitor who is signed out, and a visitor who is already signed in.

​
Registration and lead identification

Registration can help associate conversations with a known visitor, supporting more informed follow-up. However, a registration is not automatically a qualified lead. Evaluate expressed intent and context before deciding whether outreach is appropriate. Only request information you genuinely need, and make sure your privacy notices explain how that information is used.

​
Common issues

​
The guest button sends visitors directly to sign-in

Check whether guest access is enabled for that experience and whether the button points to the intended guest route. Test while signed out.

​
The logo redirects visitors to a sign-in error

Check the logo’s destination and any authentication requirements on the landing-page route. The logo should link to the intended public home page if that is your desired behavior.

​
Visitors lose their guest conversation after registering

Do not assume guest and registered sessions are automatically merged. Test the behavior in your current version and set expectations accordingly.

​
An invited visitor cannot access the chat

Confirm that the visitor has the correct authorization and is using the intended account. Guest access should not override invite-only restrictions.
Before publishing this guide as definitive product instructions, verify the exact guest-chat controls, registration prompts, and session-continuity behavior against your live Agentsy interface.