Whatever language the visitor speaks,
the agent understands
Visitors ask in their own language and agents read it in their working language; agents reply in theirs and visitors receive it in theirs. Nobody has to handle the step in between.
Keep answering after hours →
7-day free trial, no credit card (1 agent account, 5 conversations). Paid plans include a dedicated domain and 24/7 support.
Two ways to install — pick one
Neither one requires changes to your existing back end. Send a user ID and agents can see exactly who's arrived.
Paste a script
A bubble appears in the bottom-right corner of your site and opens into a chat window. Icon and position are set in the console and apply on the visitor's next reload.
<!-- Place this before </body> -->
<script src="https://chat.jstosecret.com/embed.js"
data-channel="ABC123"
data-uid="{USER_ID}"
defer></script>Send a link
Opens straight into a chat page. Good for in-app browsers, emails and ticket receipts.
# Just open it
https://chat.jstosecret.com/?c=ABC123
# With identity, so the agent knows who arrived
https://chat.jstosecret.com/?c=ABC123
&uid=10001&[email protected]After hours, customers can still reach someone
When you sell across time zones, your customer's daytime is your middle of the night. And the moment a customer asks "is this in stock?" is the moment they most want to buy — reply the next morning and they've already bought elsewhere. Catching those conversations is catching those orders.
- Every agent is offline
- The customer opens the chat window and sees an offline form
- Not many people fill one in, and the ones who do submit and leave
- Reply the next day and they've usually bought elsewhere
- Every agent is offline
- The customer opens the chat window and messages as usual
- Messages forwarded in real time to a duty group or duty mailbox
- Whoever's on duty replies, and the customer gets it right then — and buys right then
Reply right in the Telegram group
Quote the message the bot posted and reply — no need to open the console. Translation still applies: the customer writes in Russian, you type in English, they receive Russian. From seeing the message to the customer having your answer takes seconds.
Email alone works too
If you'd rather not add another tool, a duty mailbox is enough to start. Customer messages arrive by email along with the user ID, address and order notes, and the link in the email opens that customer's chat page so you can reply directly.
DingTalk and WeCom integrations in development
Answer properly from a phone
The link in the notification opens that customer's chat page, built for phones rather than a shrunken console. Images and history are all there — you can close the sale from bed.
Nobody is left hanging without an answer
Whoever's on duty can fall asleep too. After a configurable time with no reply, the system tells the customer "we've got your message — please leave a contact detail"; longer than that and it becomes an offline message, transcript included.
Customers never need to know any of this
What they see is a normal support conversation: no "we're offline" notice, no form to fill in. It's no different from daytime — and a customer who keeps talking is worth far more than one who leaves an email address.
What each side needs
The colour of the left-hand rule says whose side a capability is on: indigo is the visitor, teal is the agent.
Follows the browser language automatically
A Russian-speaking visitor sees Russian options and a Russian interface without hunting for a language switch. With no language pack available it falls back to English, not to Chinese.
Assigned in turn, no scrambling
New visitors are assigned in rotation; if an agent who has helped someone before is online, they go back to that agent first.
Visitors can leave a message when nobody is online
When everyone is off, the chat window switches to an offline form that requires an email or phone number — an offline message with no way to reply is no message at all.
Know who you're talking to from the first message
IP, region, device and referring page, plus any custom fields your system sends — user ID, email, order number.
Send images and files directly
Drag in an order screenshot or an error page; the agent opens it right there.
Admins can step in at any time
Channel administrators see every conversation and can drop a line into someone else's chat, visible to both sides immediately.
Security and reliability, spelled out
Support conversations contain order numbers, phone numbers and addresses — and every minute agents can't be reached is a lost order. Both deserve a straight explanation rather than a line about being "safe and reliable".
Encrypted end to end
Pages, API calls and WebSocket traffic all run over HTTPS/WSS. Uploaded images and files go through the same encrypted channel and never land in a public directory.
Channels are completely isolated
Isolated per channel at the database level; a neighbouring channel can't read your content even with a session ID. Agents are isolated the same way — they see only what's assigned to them.
No messages lost on disconnect
Visitors switching tabs and agents changing networks both reconnect automatically, with any messages from that gap filled in. If an agent drops off, their open conversations move to whoever is still online.
One DNS change brings you back when something breaks
The domain is in your name, so if DNS or routing goes wrong you can switch it yourself at any time instead of queueing behind us. Control of that path stays with you.
A dedicated domain: one customer's outage stays theirs
When everyone shares one chat domain, any single customer getting blocked by some network takes the whole domain down with them. A dedicated domain pulls that path out on its own — its own DNS, its own certificate — so other people's outages never reach you.
Customers keep messaging after hours, forwarded to your duty group
Included when you buy — your own brand, and failures kept apart
HTTPS / WSS transport, data isolated between channels
FAQ
Translation runs on large language models like Claude and ChatGPT, not sentence-by-sentence machine translation. The model carries the context of the conversation, so "it still hasn't arrived" becomes "the order still hasn't arrived" rather than a literal rendering with no context; order numbers, model codes and proper nouns aren't treated as ordinary words. The original is always kept — agents see the source and the translation side by side, and can check the original whenever something looks off. If translation fails, the original is sent through; messages are never silently dropped.
HTTPS/WSS encryption end to end. Every channel's conversations, agents and visitor data are isolated at the database level — a neighbouring channel can't read your content even knowing your session ID. Agents are isolated too: a regular agent sees only the conversations assigned to them, never a colleague's.
No. Translation is two independent switches — "auto-translate incoming messages" and "translate before sending" — and an agent can turn on one, or neither. If you only support in one language, none of this applies and none of it costs anything.
The chat window runs in an iframe, fully isolated from your page's CSS, so neither affects the other. The bubble's position, icon and colour are set in the console, and changes apply on the visitor's next page load — no need to re-paste the code.
Pass your system's user ID at install time and we'll recognise them, with their history and the agent who helped them last still attached. Anonymous visitors are recognised by a local browser identifier, so clearing the cache or switching devices makes them a new visitor.
An offline form is one-way: the customer fills it in and leaves, and by the time you reply the next day they may have already bought elsewhere. Always on is two-way — the customer keeps messaging, it goes straight to your Telegram duty group in real time, whoever is on duty quotes the message and replies, and the customer gets the answer right there, never knowing support had gone home. It's a Flagship feature; once enabled you bind it to a duty group.
There are two levels of fallback, and you set the timing. By default, after 5 minutes with no reply, the system tells the customer "we've got your message — please leave a contact detail"; after 30 minutes it converts the chat to an offline message and closes the session, keeping the transcript so whoever comes online next sees the full context. Without that safety net, "always on" turns into "nobody ever answers", which hurts more than honestly showing as offline.
The chat window and bubble run on a domain of yours, so visitors see your brand in the address bar instead of ours. We handle the certificate; all you do is add one DNS record. One domain on Professional, five on Flagship.
The bigger benefit is isolating risk. When every customer shares one chat domain, it only takes one of them getting blocked — by some network, some ISP, some corporate firewall — for the domain to stop loading for everyone on it. And you'd have no idea why; all you'd see is visitors suddenly unable to connect. On your own domain, someone else's problem never reaches you, and if something does go wrong, changing one DNS record fixes it without waiting on us. Multiple brands or sites can each run their own, fully independent of one another.
Support around the clock on Telegram at @chatcocoaofficial, or just click the bubble in the corner — that's this product running on its own site. For partnerships and quotes, write to [email protected]. Sales and support are separate lines; don't mix them up.
Talk to us
Two separate doors: partnerships go to sales, product problems go to support. Getting it wrong only costs you a round trip.
Sales
[email protected]Enterprise quotes, self-hosted deployments and reseller partnerships. Tell us the background and the scale in your email and we'll come back faster.
Support
Telegram @chatcocoaofficialAvailable 24/7. Installation questions, account questions and troubleshooting all go here — or just click the bubble in the corner.
Start with one channel
Registering gets you a 7-day trial (1 agent account, 5 conversations), no credit card. If it isn't a fit, just leave it — nothing charges automatically.