The hosted page is 404

What it is

Your chatbot's hosted page lives at /agent/{handle}. It returns a not-found page in exactly three situations:

1. The handle does not match any chatbot. A typo, or a handle that was renamed — the old one stops working the moment you change it.
2. The chatbot is not Active. A paused chatbot is unreachable, and the page looks identical to one that never existed.
3. The owner's account is scheduled for deletion. During that window, every hosted page belonging to that owner goes dark. Signing back in cancels the deletion and brings them all back.

That is the complete list. Anything else you might suspect is not a cause.

Deliberately not causes

There is no "hosted page disabled" switch. If you are hunting for a toggle you accidentally flipped, there isn't one.

Access control does not produce a not-found. If you protected the page with an access key, a password, or a sign-in requirement, visitors get a gate screen asking for credentials — a sign-in prompt, a password box, or a request for the access key. That is a locked door, not a missing page. See Hosted page access control.

Untrained does not 404 either. An Active but untrained chatbot loads the page normally and tells visitors it is not ready yet. See Untrained hosted page.

Being out of credits does not 404. The page loads and the chatbot says it is temporarily unavailable — see We are out of credits.

The reason the not-found page is deliberately uninformative is that it should not be possible to probe the URL space and discover which chatbots exist. An unknown handle and a paused chatbot produce identical responses on purpose.

When you would use it

When a QR code, an email link, an iframe, or a "chat with us" button opens a not-found page. Especially just after a rename, or just after somebody paused something to "tidy up".

Where to find it

Dashboard → Chatbots → your chatbot → Playground for status, and the chatbot's channel settings for its current handle and direct link.

Steps

1. Open the failing URL and copy the handle — everything after /agent/.
2. Open Dashboard → Chatbots. If no chatbot matches that handle, either it was renamed or you are in the wrong workspace. Check the account switcher — see Switch accounts.
3. Open the chatbot and check its status on Playground. Set it to Active and save if it is not — see Activate or pause a chatbot.
4. Find the current handle and compare it character by character with the URL. See Hosted page handle.
5. Open the link in a private window. A cached not-found in your own browser will otherwise fool you into thinking nothing changed.
6. If it now loads, go and update every place the old link is published: QR codes, email signatures, buttons, iframes, printed material.

Renaming the handle breaks the old link

Worth its own warning, because it is the cause people find hardest to spot.

When you change a chatbot's handle, the old address stops resolving straight away. There is no redirect from the previous one. Anything already published against it — a printed QR code, a scheduled email, a partner's website — breaks silently.

If a link is already out in the world, either leave the handle alone or plan the change: update everything you control on the same day, and accept that you cannot update what you do not control.

Legacy links

Older /bot/{id} links redirect to the current /agent/{handle} form. After the redirect the same three rules apply, so a legacy link pointing at a paused chatbot still ends at a not-found. See Legacy bot URLs.

Pausing a public URL is a bad idea

If a chatbot's link is on a live campaign, in an email, or on a printed card, pausing it turns every one of those into a dead link — and search engines that visit while it is paused will treat the page as gone.

If you need a chatbot to stop being useful for a while without breaking its URL, better options are to leave it Active and change its messages, or to put an access gate in front of it. Both keep the address alive.

Limits and plan notes

The hosted page works on every plan, including free. It is the website widget and the messaging channels that need a paid plan, which makes the public link the reliable fallback while you sort an embed out. See Share a hosted link.

The not-found page is identical for unknown and paused. That is deliberate.

The widget behaves differently. An inactive chatbot's widget is refused rather than returning a not-found — see The widget is blocked.

Handles are per chatbot and unique. You cannot point two chatbots at the same address.

If nothing here works

Write to support with:

• the full URL that fails, exactly as published,
• the chatbot name and the account owner's email,
• the handle currently shown in the chatbot's settings,
• confirmation that the chatbot reads Active on its Playground tab,
• whether the handle was renamed recently, and when,
• the time you last tested, with your timezone.

See Contact Support.

Common problems

I activated it and still see a not-found.

Your browser cached the failure. Try a private window, and confirm the handle in the URL matches the one in settings exactly.

The link works for me and not for a customer.

You have an access gate on the page and you are signed in. To them it is a locked door, not a missing page — check Hosted page access control.

My iframe is blank instead of showing a not-found.

Some site builders hide error pages inside frames. Open the frame's source URL in a new tab to see the real response.

Everything 404s across all my chatbots at once.

Check whether the account owner has scheduled the account for deletion. Signing back in cancels it and restores every hosted page — see Delete your account.

Can I get a redirect from my old handle?

No. Renaming leaves no forwarding address, which is why it is worth deciding on a handle before you publish it anywhere.