Hosted sites

Every site has a hosted public experience. It is the fastest way to test the visitor journey, share an agent without writing code, and provide a reliable destination for platforms that do not allow JavaScript embeds.

Choose a durable slug#

The slug becomes the public address, normally https://YOUR_SLUG.makeagent.fast. Use a short name visitors recognize. A valid slug must not collide with another tenant or a reserved platform route such as docs, dashboard, or api.

Treat the slug as public information, not a secret. Changing a public address after launch can break saved links, UTM campaigns, QR codes, and provider profiles, so settle on the durable name before distribution.

Change the included subdomain from the site's Domain page. Use lowercase letters, numbers, and hyphens, with no leading or trailing hyphen, up to 40 characters. Saving a new slug makes the old hosted subdomain stop working immediately; the platform does not promise an automatic redirect from the old slug. An already active custom domain is unaffected, but links that still use the hosted address must be updated.

Prepare the visitor experience#

Before publishing, review more than the generated text:

• Site title, description, image, sections, calls to action, contact details, and legal/privacy links.
• Agent name, persona, language, fallback behavior, and knowledge acceptance questions.
• Text, voice-message, and live-call surfaces that your plan enables.
• Mobile navigation, long content, Korean/English text, keyboard focus, contrast, and form errors.
• Lead-capture purpose and the operator who will review Conversations.

Use an owner preview for quick iteration, but perform final acceptance on the public address in a private browser window.

Publish and verify#

1. Open the intended site and confirm its slug.
2. Save the latest agent, knowledge, appearance, and page changes.
3. Select Publish.
4. Open the public URL in a private window.
5. Send an acceptance-test question and complete every important call to action.
6. Check narrow mobile width and any enabled voice permission.
7. Confirm the test thread appears in Conversations and usage is attributed to the expected site.

Publishing exposes the current site state. Later dashboard edits should be treated as a new draft/review cycle; publish again after the changes are ready for visitors.

Search and sharing#

Published sites provide crawlable page metadata and social-sharing information. Use a specific title and description that explain the visitor outcome, plus a representative image you have the right to publish. Test the URL in the sharing channels that matter to you because social crawlers can cache an older preview.

When an active custom domain is attached, it can become the canonical public address and the hosted slug can redirect to it. Select one primary host (www or apex) so search engines and visitors do not treat two hostnames as competing copies.

Connect other surfaces#

The hosted site and an embed can use the same site agent. Messaging connectors also route into that agent but keep channel-scoped conversation identity. Publishing does not automatically install the embed or configure provider webhooks; complete those guides separately.

Use the hosted URL as a normal button/link for Notion, Linktree, email signatures, QR codes, and other surfaces that cannot load arbitrary JavaScript. Add UTM parameters when you need campaign attribution, without putting personal data in the URL.

Update or unpublish#

To update a live site, make the change, test it in the owner flow, publish again, and verify the public URL in a private window. If an edge or social preview appears stale, distinguish the browser page from a third-party cached share card before changing the site again.

Unpublishing removes the public site experience but does not delete the site, knowledge sources, agents, conversation history, custom-domain billing, or external provider configuration. Connected messaging bots may continue answering; disable/remove each connector separately. Remove a custom domain from its Domain page if its add-on should also stop.

Launch checklist#

• Public URL, title, metadata, favicon/image, and primary CTA are correct.
• The agent answers known questions and declines or escalates unknown ones.
• No draft-only, private, or credential-bearing content is visible.
• Mobile, keyboard, form, and voice behavior has been tested.
• Privacy, AI/synthetic-media disclosure, and consent language match the enabled features.
• Conversation owner, usage monitoring, and incident contact are assigned.
• Embed origins, connector provider modes, and custom-domain state are verified independently.

Troubleshooting#