Skip to main content
Once your AI Experience website’s design and content are ready, configure the additional settings that help visitors identify your business, contact you, understand your terms, and interact with your experience. This guide focuses on website information and integrations. For writing website copy, choosing templates, uploading images, and selecting brand colors, see Customize Your AI Website and Logo and Brand Colors.

​
1. Upload your Terms & Conditions

Terms & Conditions are an important part of launching your AI Experience. End users must accept your Terms & Conditions when registering, and the document is also available from the footer of your main website. Prepare a document that accurately describes your service and the rules that apply to its use. Depending on your business, consider addressing the educational or informational nature of the experience, appropriate use, limitations, and how visitors’ information is handled.
Agentsy provides the ability to display and require acceptance of your Terms & Conditions, but you are responsible for the document’s content and suitability for your business and applicable laws. Consider obtaining legal advice when appropriate.
Before publishing: upload the file, confirm that it opens from the website footer, and test that registration requires acceptance.

​
2. Add your business and assistant information

You can provide the following information to help visitors recognize who is behind the experience. The Complementary Website URL is visible in the navbar of the onboarding page, giving visitors a way to discover your main website.
Use the same naming and branding across your Agentsy experience and your main website so visitors can easily recognize the connection.
Agentsy can display useful next steps inside the conversation, making it easier for interested visitors to connect with you when they’re ready. Add only the links relevant to your business. Check that each link opens the intended destination, particularly on mobile devices.
These are platform-provided conversation links. They are different from the website’s built-in CTA labels, which are controlled by Agentsy and can be displayed in the supported CTA languages.

​
4. Connect your social media profiles

You can add your business’s social media links. The configured profiles are displayed in the footer of your AI Experience website. Supported platforms:
  • Facebook
  • Instagram
  • X
  • LinkedIn
  • TikTok
Use direct links to the relevant public profiles and verify that they work.

​
5. Configure basic SEO

Agentsy provides two fields for search engine metadata: Write the Meta Description for a prospective visitor: explain what they can explore or learn through your experience. Keep it specific, natural, and consistent with the website content.
Search engines may generate their own snippets. Meta Keywords are supported as a setting, but major search engines generally do not use them as a ranking factor. Focus primarily on a clear description and useful page content.

​
6. Set up analytics and advertising tracking

If you use analytics or advertising measurement tools, you can configure:
  • Google Tag ID — the identifier for your Google tracking setup.
  • Google Tag Type — select the Google tag type corresponding to your identifier.
  • Meta Pixel ID — the identifier for your Meta Pixel.
Copy the identifiers from the relevant provider account and enter them into the corresponding Agentsy fields. Ensure that the Google Tag Type matches the identifier you are using.
Tracking technologies can be subject to privacy and consent requirements. Make sure your setup, disclosures, and consent practices comply with the laws that apply to your visitors. Do not assume that displaying a cookie banner alone automatically makes every tracking configuration compliant.
You can enable a cookie consent banner for your AI Experience website and customize its text and buttons. When configuring the banner:
  1. Decide whether the banner should be enabled for your website.
  2. Write clear, understandable text explaining the use of cookies or tracking technologies.
  3. Configure the available button labels to match the choices offered.
  4. Preview the banner on desktop and mobile.
  5. Check that its behavior matches your tracking and consent requirements.
Keep the wording short and accessible. If you use analytics or advertising tags, ensure that the banner and your privacy documentation accurately describe their use.

​
8. Create a webhook for events

Webhooks allow Agentsy to send event notifications to an external URL that you control, such as an automation platform, CRM integration, or your own application. To configure a webhook, provide:
  1. Name — a descriptive name so you can identify the integration.
  2. Webhook URL — the destination endpoint that will receive event notifications.
  3. Events to subscribe to — select the events relevant to your integration.
Available events:
Webhook events may contain information about users or conversations. Send them only to trusted endpoints, protect the receiving system, and handle the data according to your privacy obligations. Confirm the exact payload format through a test event before building downstream automation.
Event names are shown exactly as they appear in the subscription options. Select only the events you need; a webhook does not require subscribing to all three.

​
9. Review everything before launch

Use this checklist to make sure your website settings are ready:
  • Terms & Conditions uploaded in an accepted format, under 2 MB.
  • Terms & Conditions open from the footer and are required during registration.
  • Assistant Name and Company Name are correct.
  • Complementary Website URL works from the onboarding navbar, if provided.
  • Booking / Meeting, WhatsApp Business, and Shop / Store links work where configured.
  • Social profile links open correctly from the footer.
  • Meta Description and Meta Keywords are reviewed.
  • Google Tag ID, Google Tag Type, and Meta Pixel ID are correct, if used.
  • Cookie consent banner text, buttons, and behavior have been reviewed, if enabled.
  • Webhook name, URL, and selected events have been tested, if configured.
  • Website and conversation experience have been checked on mobile and desktop.