Pages

Pages gives an existing chat agent its own hosted or embedded conversation page. Each Page belongs to one agent. To publish another agent, configure that agent's own Page.

For a guided example with screenshots, follow Publish a branded support Page.

Configure and publishCopy Anchor Link

1. Open your agent’s Publish screen and choose Pages. Overview shows the assigned agent and whether its chat channel and Pages hosting are configured.
2. Choose Appearance to set the display name, theme and colors. Upload a logo or favicon, or supply an HTTPS image URL. Uploads must be PNG, JPEG, GIF or WebP under 500 KB. Branding images are publicly accessible, so use assets intended for public display.
3. Use Chat experience for welcome text, starter prompts, the composer and attachment settings. Knowledge, tools and agent behavior stay on the agent.
4. Set Access to public or sign-in required. For an iframe, add each allowed website origin, including https://. Origins are exact, without a path.
5. Save draft, then Publish saved draft to apply your changes to the live Page. Publishing checks the agent's active chat channel and hosting readiness. Unpublish stops visitors accessing the Page.

The style preview uses the actual Page interface with a sample conversation. Use its desktop/mobile controls to check the layout, and switch between Welcome and Conversation. The preview shows draft styling with sample messages. Open the published Page to test real conversations and sign-in.

Choose an addressCopy Anchor Link

• Managed address: edit the slug in Overview, for example acme-support.chatbyte.page. Save and publish to apply it.
• Custom domain: enter a hostname such as help.acme.com in Domains and keep Path as /. Add the displayed DNS and ownership records, then check the domain. Select Make primary once verified.
• Customer subpath: enter acme.com and /support. Your website must run a server-side connection for this address. Give your developer the subpath setup guide, then verify ownership and the connection in Chatbyte before making the address primary.

Install displays the full address, including a subpath, and uses the published access policy. Save and publish draft access changes before copying updated code. A custom domain and a subpath use the same Page and agent. Removing a connection revokes its routing; replacing a proxy key requires updating your server and verifying again.

Embed a public PageCopy Anchor Link

Copy the iframe from Install and put it in your site. Add your site's origin under Access. Adjust the iframe's width and height to fit your layout. A public Page needs no authentication SDK.

Private PagesCopy Anchor Link

Choose sign-in required under Access when the Page should be available only to authenticated users. Agree with your team who should have access, which account they belong to, and whether particular roles are required.

Your developer connects your existing sign-in system and supplies the verification settings for Access. Share the private Page sign-in guide with them.

For a hosted Page, visitors sign in through your configured sign-in screen. For an embedded Page, your website supplies the signed-in identity through the Pages integration. Complete this connection before publishing with private access.

Save and publish the access settings, then test a signed-in user, a signed-out user, an account switch, and someone who should not have access. Use the published Page address or embed for these sign-in checks.