Loading Guide…

Guide Cross-Device PoC
detecting…
Session
Visitor ID …
Contact ID waiting for chat…
Hostname …
GET →
Response includes "customFields":[{"ident":"page_hostname","value":"…"},…]
Cross-Device Session Transfer

Start a chat on this device, then use the link or QR code below to continue the same conversation on a different device. The receiving device plants the same localStorage keys, and NICE reconnects to the open thread automatically.

Status: No active session
Scan on other device
setCustomerId Test (undocumented behaviour)

NICE provides setCustomerId but does not document whether it enables cross-device session lookup on their backend. Enter any identifier (account number, email, etc.) here, use the same value on the second device, and observe whether NICE automatically reconnects. Results either way are useful — this is the experiment.

Value is persisted in localStorage (wowAccountId) and included in transfer links as ?wowAccountId=.

Cross-subdomain navigation (same device). Also tests that the transfer mechanism works — the same URL params that power cross-device power this too.

Cross-TLD navigation. Switch to the other top-level domain (nisesomi.com ↔ carlrhoades.com) while preserving full session transfer state. Use this to demonstrate cross-domain behavior across completely different TLDs.

API Token
No token
Inject Message into Chat Thread
Waiting for active chat thread…
POST →
Custom Fields (pre-launch via SDK)
PUT custom fields →
Body: [{"ident":"page_hostname","value":"…"},{"ident":"page_url","value":"…"}]
Serviceability Check

Push address data into the Contact record as custom fields and inject a visible note into the chat thread. If submitted before the chat starts, it will push automatically the moment a Contact ID is established.

Session params are passed cross-device via URL (?wowVid=, ?wowThread=, etc.) and planted into localStorage synchronously before the NICE SDK loads.
Params are stripped from the address bar after planting so the agent sees the clean URL.