Direct Link

Send a chat page link directly to your customers. They can open it and start a conversation immediately without any website deployment.

Common Use Cases

• Email signatures - add the chat link to support emails
• In-app webviews - open the chat page inside an app
• Website iframes - embed the hosted chat page into an existing website
• Social profiles - place the link in bios or menus
• QR codes - convert the link into a QR code for offline scanning

Basic Link

https://page1.visitor-chat.com/direct/{YOUR_APP_ID}

Open a Specific Workspace

wcode is an optional workspace identifier issued by the customer-service workspace list. Add it after the App ID when the direct page should use that workspace's branding and visitor configuration:

https://page1.visitor-chat.com/direct/{YOUR_APP_ID}_{YOUR_WCODE}

The value is generated by the backend. Pass it through unchanged; do not generate or locally validate it. Omitting wcode keeps the default-workspace behavior. An invalid, deleted, disabled, or cross-project value is treated as an unavailable site and is not silently mapped to the default workspace.

Embed the Chat Page in a Website (iframe)

Use the hosted Direct Link as the src of an iframe when you want the chat page to appear inside an existing website. Replace {YOUR_APP_ID} with your project App ID:

<iframe
  src="https://page1.visitor-chat.com/direct/{YOUR_APP_ID}"
  title="TWT Chat"
  width="100%"
  height="720"
  style="border: 0"
  allow="microphone; camera; autoplay; fullscreen"
></iframe>

Set the iframe height to match your page layout. You can append the supported URL parameters documented below, including lang and customer information parameters.

The browser and the visitor still control access to camera, microphone, and other capabilities declared in allow. If your integration uses clipboard or screen-sharing features, append clipboard-read; clipboard-write or display-capture as needed. Only request the permissions your integration needs.

iframe Demo

Open the iframe chat demo. For the complete copy-ready source, see Iframe Direct Chat Demo.

Open a Chat Detail by Direct Link

In Standalone mode, you can use URL parameters to let visitors enter a specific chat session detail directly.

Link Format

https://page1.visitor-chat.com/direct/{YOUR_APP_ID}?direct=1&chatid={SESSION_ID}

Parameters

Parameter	Required	Description
direct	Yes	Must be fixed to 1. This is the explicit direct-detail intent flag and prevents unexpected navigation when regular visits accidentally include chatid.
chatid/chat_id	Yes	Target chat session ID (Session ID).

Example

If the customer service appid is demo_app and the target session ID is session-abc-123:

https://page1.visitor-chat.com/direct/demo_app?direct=1&chatid=session-abc-123

Language Parameter

The chat page detects the browser language automatically. If the browser language is unsupported, the page falls back to en. You can also append ?lang= to set the page language explicitly:

https://page1.visitor-chat.com/direct/{YOUR_APP_ID}?lang=en

Supported language codes:

Code	Language
zh-cn	简体中文
zh-tw	繁體中文
en	English
ja	日本語
ko	한국어
de	Deutsch
fr	Français
pt	Português
ru	Русский

Portuguese browser variants such as pt-PT and pt-BR are normalized to pt.

Customer Information Parameters

Pass internal customer information to the chat page so agents can identify the visitor in the workspace.

Parameter	Type	Description
sbs	string/number	Unique customer identifier
sbs_mm	string	Customer signature
ranstr	string	Random string, recommended to be at least 16 characters
name	string	Customer full name
nickname	string	Customer nickname
email	string	Customer email
phone	string	Customer phone number
customer_remark	string	Customer remark; must be provided together with the customer identifier

sbs_mm Generation Rule

sbs_mm = md5( md5(sbs + '_' + AppSecret) + '_' + ranstr )

• MD5 output must be lower-case 32 characters
• AppSecret is required to generate sbs_mm. Create it in Developer Settings and keep it private

Full Example

https://page1.visitor-chat.com/direct/{YOUR_APP_ID}?sbs={sbs}&sbs_mm={sbs_mm}&ranstr={ranstr}&name={name}&nickname={nickname}&email={email}&phone={phone}&customer_remark={customer_remark}

danger

Generate the sbs_mm signature on the server side only. Never expose AppSecret in frontend code or URLs.