Change the hosted page handle

What it is

The handle is the part of your hosted page's address that identifies the chatbot: the your-brand in /agent/your-brand.

Every chatbot starts with its numeric id as the handle, so the link works from the moment the chatbot exists. You can replace that with a readable slug at any time.

When you would use it

• Before printing anything — a poster, a card, a QR code.
• Before recording a video or a presentation that shows the URL.
• When the link is going in an email signature or a social bio and /agent/312 looks unfinished.
• After a rebrand, when the old name no longer fits.

Where to find it

Open Dashboard → Chatbots → your chatbot → Integrations → Messaging → Direct link. The handle field sits next to the current public URL.

The rules

Rule	Detail
Length	3 to 40 characters
Characters	Lowercase letters, numbers, and hyphens
Not only digits	A purely numeric slug is rejected, because it would collide with chatbot ids
Unique	Across the whole platform, not just your workspace
Not reserved	Certain words are blocked

The reserved words are the ones that would collide with parts of the hosted page's own address or look like system routes: config, gate, session, chat, lead, history, feedback, queries, admin, api, login, logout, register, auth, widget, dashboard, agent, bot, new, null, undefined.

Uniqueness is platform-wide, so short generic words — support, help, sales — are very likely taken already. A slug that includes your brand is both more available and more useful to the person reading it.

Steps

1. Open Dashboard → Chatbots → your chatbot → Integrations → Messaging → Direct link.
2. Find the handle field. The current public URL is shown beside it.
3. Enter a slug using lowercase letters, numbers, and hyphens. Avoid anything that is only digits.
4. Save.
5. Copy the new /agent/{handle} URL.
6. Replace the old link everywhere you have used it — website buttons, email signatures, social profiles, any iframe src.
7. Open the new URL in a private browsing window to confirm.

The thing to understand before you rename

The old handle stops working. It does not redirect. Anyone who follows a link with the previous slug gets a 404.

This is different from the legacy /bot/{id} addresses, which do redirect permanently to the current handle. Those old links keep working. An old handle does not. See Old /bot links still work.

The practical consequences:

• Rename before you print, not after. A reprint is expensive; a rename is free.
• If you might rebrand, consider printing the numeric-id URL instead. It never changes, and it always resolves to the current handle.
• Audit before you save. Make a list of every place the link appears — website, signature, social bios, partner sites, PDFs, the QR code on the shop door — and update them the same day.
• A freed slug can be taken. Once you release a handle, someone else on the platform can claim it. Do not assume you can change your mind next week.

What you will see

The handle field sits next to the current public URL, so you can see exactly what you are about to change.

After saving, the URL shown updates immediately. The old slug now 404s, and the new one is what you copy and share.

Renaming is purely an addressing change. It does not retrain the chatbot, does not affect its answers, does not touch knowledge, and does not disturb existing conversations.

Choosing a good handle

• Use your brand, not a generic word. acme-support beats support, and it is far more likely to be free.
• Keep it short enough to say out loud. If you will ever read the URL over the phone, that matters more than precision.
• Avoid dates and version numbers. acme-2026 will be wrong in January.
• Avoid hyphens in bulk. acme-customer-service-chat is technically fine and nobody will type it correctly.
• Match it to a name people already know. The handle is a promise about what is behind the link.

Limits and plan notes

• Handles are 3 to 40 characters, lowercase, unique across the platform.
• Custom handles are not plan-gated — the direct link is available on Free, and so is renaming it.
• Every chatbot always resolves by its numeric id as well, whether or not you set a handle.
• Changing the handle does not change access control. A gated page stays gated. See Control who can open the hosted page.
• The handle is a hosted-page concept only. The website widget identifies the chatbot by its own token and is unaffected.

Common problems

The slug I want is rejected.

It is too short, too long, only digits, contains characters that are not allowed, reserved, or already taken by someone else. Try adding your brand.

Printed material still uses the old URL.

Those links 404 now. Nothing can be done except reprint, or set the handle back to the old value if it is still free. This is the argument for using the numeric-id URL on anything permanent.

My iframe broke after the rename.

The src still points at the old handle. Update it.

Can I have two handles for one chatbot?

No. One handle at a time, plus the numeric id which always works.

Someone else took my handle.

Handles are first come, first served across the platform, and a released one is immediately available. Pick a brand-specific variant.

The new URL 404s straight after saving.

Confirm the chatbot is Active — a 404 is far more often about activation than about the handle. Then re-copy the URL from the drawer in case of a typo.