What it is
The Hosted Page is a complete, branded chat experience that lives at its own web address. There is no widget to install and no site to modify, you activate the Web Chat channel and share the link. It opens full-screen, streams replies from your assistant in real time, and remembers a returning visitor's history.
Your Hosted Page link
https://{your-subdomain}.drusy.ai/chatHosted Page vs. embedded widget
Both are powered by the same Web Chat channel and share one configuration. They differ only in how visitors reach the chat.
| Hosted Page | Embedded widget | |
|---|---|---|
| Where it lives | Its own dedicated URL you share | Embedded on your site via a snippet |
| Installation | None, just share the link | Paste a <script> tag into your site |
| Layout | Fills the whole browser window | Floating card, capped at 380×600px |
| Close button | None, nothing to close | × control to minimize the card |
| Allowed origins | Not applicable, first-party visit | Restricts where the snippet may load |
| Session handoff | Page mints its own session on load | Parent page hands off via postMessage |
Quick setup
Three short steps and your link is live. Since the Hosted Page and widget are the same channel, configuring one configures the other.
Open the Web Chat channel
1 minuteThe Hosted Page shares one configuration with the embeddable widget, they are the same channel. Open it to configure both at once.
- Web Chat channel open
- Title, greeting, and theme color reviewed
Test, then activate
1 minuteRun a quick test to confirm the assistant responds, then activate the channel. The link goes live immediately, there is nothing to deploy.
- Test conversation succeeded
- Channel status shows Active
Copy your link and share it
1 minuteCopy the Hosted Page link from the channel page using the copy button, then share it anywhere, a bio, a QR code, an email, or a direct message.
- Link copied
- Opened in a browser to confirm it loads
Configuration & customization
The Hosted Page uses the same fields as the widget snippet, because it is the same channel. Set them once and both surfaces update.
| Field | Limit | Notes |
|---|---|---|
| Widget title | 60 characters | Shown as the page header and the browser tab title, handy if visitors bookmark it. |
| Greeting message | 300 characters | The first assistant message shown to a brand-new visitor. |
| Theme color | 6-digit hex, e.g. #4f46e5 | Colors the header and the visitor's own message bubbles across the whole page. |
Live preview
Adjust the title, greeting, and theme color to see how your Hosted Page looks and feels. Send a message to watch the streaming reply and typing indicator, or flip the channel to Inactive to see the friendly unavailable state.
Try the settings
Illustrative preview. Live replies come from your assistant once the channel is active.
How it works
Under the hood, the Hosted Page runs on the same backend as the widget, the same session and messaging, just visited directly instead of loaded inside an iframe.
Same assistant, same streaming
Live AI and staff replies stream in in real time, including the typing indicator, identical to the embedded widget.
Self-minted sessions
With no parent page to hand off a session, the page mints its own on load. Everything it needs is baked into the page itself.
Always fresh, never cached
The page is served with no-store caching, so every visit reflects the current state of your channel and business, deactivate it and visitors see the change right away.
Persistent visitor history
An anonymous visitor ID is stored in the browser, so conversation history persists across visits on the same device, the last 50 messages load back in on return.
Visitor experience
Because it is a standalone page, the experience is simpler than the widget, no sizing constraints, no floating card, no separate mobile mode.
- Full-page layout, the chat fills the whole browser window naturally, with none of the widget's card-sizing constraints.
- No separate mobile mode, it is already full screen by design, so there is no mobile breakpoint to worry about.
- No close button, there is nothing to close on a standalone page, so the × control is never rendered.
- History persists per browser via an anonymous visitor ID, loading the last 50 messages on return, with a fresh greeting when there is no history.
- A 24-hour session with silent refresh keeps returning visitors connected without re-onboarding.
- Up to 4,000 characters per message, and up to 20 messages per 60 seconds per visitor.
- Enter to send, Shift+Enter for a newline, identical to the widget.
States & lifecycle
If the channel isn't live
Unlike the widget, which simply doesn't render a bubble, the Hosted Page is a page someone navigated to directly, so it shows an explicit, friendly state instead of looking broken:
“Chat is currently unavailable.”
with the message box hidden
This covers a channel that is not active, an inactive business, or a deleted channel. No raw errors are ever shown to a visitor.
Deactivating or changing the channel
- Deactivating stops new sends immediately, including in an already-open tab, the visitor's next send attempt fails.
- On the next load or refresh, visitors see the "unavailable" state right away, with no stale-cache delay, because the page is never cached.
- Title, greeting, and color changes apply on the next session mint, effectively immediately, since the page always mints fresh on load.
Where to use it
Because it's just a link, the Hosted Page goes anywhere you can put a URL or a QR code.
Social bio links
Instagram, TikTok, or LinkedIn bio, turn profile visitors into conversations.
QR codes
On a storefront, receipt, or printed flyer so customers can chat on the spot.
Marketing emails
A "Chat with us" button or link in a campaign or email signature.
Direct messages
Text or DM the link straight to a customer who needs help.
No-script fallback
For businesses that can't add a <script> tag to their site at all.
Support handoffs
Share the link from any channel to continue in a full-screen chat.
Example: link it from an email signature
<a href="https://yourbrand.drusy.ai/chat">Chat with us</a>Best practices
Write a specific title
It doubles as the browser tab title and shows on bookmarks, "Acme Support" beats "Chat."
Lead with a helpful greeting
Set expectations in the first message: what you can help with and how fast you respond.
Match your brand color
Use your exact 6-digit hex so the header and message bubbles feel on-brand.
Test before you share
Open the link yourself and send a message to confirm the assistant responds as expected.
Use a QR code for print
Turn the link into a QR code for flyers, receipts, and storefront signage.
Deactivate intentionally
Remember that deactivating takes effect immediately for everyone, including open tabs.
Troubleshooting & FAQ
Common questions about setup, availability, and behavior. Search to jump to a topic.
Setup & availability
No. The Hosted Page is a standalone, branded page at its own URL. There is nothing to embed, paste, or deploy, you activate the Web Chat channel and share the link.
Allowed origins only restricts where the embeddable snippet may load from on third-party sites. The Hosted Page is a direct, first-party page visit, there is no cross-site origin to check, so it works regardless of what is in that list.
Effectively immediately. Because the page is never cached and always mints a fresh session on load, title, greeting, and color changes apply on the next visit or refresh, and deactivating the channel is reflected right away.
The Hosted Page is served on your workspace subdomain by default. Contact support if you have a specific domain requirement for your setup.
Behavior & limits
A friendly "Chat is currently unavailable." message with the message box hidden, never a raw error. This covers an inactive channel, an inactive business, or a deleted channel.
Yes, the same limits as the widget: up to 4,000 characters per message, and up to 20 messages per 60 seconds per visitor.
Press Enter to send and Shift+Enter to add a newline, identical to the embedded widget.
Not automatically. The visitor ID is stored per browser origin, and the Hosted Page and your embedded widget are different origins from the browser's point of view. A visitor's Hosted-Page chat and widget chat are separate threads unless they are on the exact same page and origin.
Deactivating stops new sends immediately, so their next send attempt fails even in an already-open tab. On their next load or refresh they see the "unavailable" state, with no stale-cache delay, since the page is never cached.