The normal way to install live chat is a script tag. It works everywhere you control the HTML of a page, which covers your own website and almost nothing else. The moment you want chat somewhere you are a guest rather than the owner, the script stops being an option.
The list of those places is longer than most teams realise. Email signatures render in a mail client that strips scripts as a matter of basic safety. Marketplace listings allow a narrow subset of HTML and reject the rest. Forum and community posts, partner directories, help-centre platforms you do not host, and the description field of almost every third-party profile all behave the same way. You can usually leave a link. You cannot leave a program.
That constraint is not a bug to be worked around with a cleverer snippet. It is a deliberate security boundary, and any vendor promising to run JavaScript inside your email signature is describing something you should not want.
What the no-JavaScript link actually is
MyLiveChat generates a plain anchor for exactly this case. You will find it in the dashboard under Developer Tools → No-JavaScript Link. The screen has two inputs and a code box.
- Link Text is what people read. It defaults to Click to chat.
- Link Title becomes the tooltip, and is optional.
- The code box gives you the finished HTML, with a copy button and a preview underneath so you can see the link before you paste it anywhere.
What comes out is an ordinary anchor tag pointing at a chat endpoint with your account id attached, carrying your link text, your tooltip and a target that opens a new tab. There is no script in it, which is the entire point. Anywhere a link survives, this survives.
Because it is generated rather than hand-written, do not retype it from memory into the next listing. Copy it each time. The account id is the part that connects a click to your workspace, and a transposed character produces a link that looks right and goes nowhere useful.
What happens when somebody clicks it
The link does not open a widget in place. It sends the visitor to your chat window, and it does two useful things on the way.
First, it opens in a new tab. The listing, forum thread or email the person was reading stays where it was, which matters more than it sounds: the reason people hesitate to click a support link is the fear of losing their place, and here they do not.
Second, it passes along the page the click came from. The agent picking up the conversation can see the referring page rather than a bare chat request with no context. Somebody arriving from a specific product listing is a different conversation from somebody arriving from your email footer, and the agent gets to know which is which before typing a word.
From there it behaves like your chat window normally does, including when nobody is available. Whatever you have configured for offline handling is what these visitors meet, so it is worth checking that screen before you scatter the link across a dozen places.
Everything the widget does that feels automatic comes from JavaScript running on the page. Take the script away and those things go with it. Be clear-eyed about the list:
- No proactive invitations. Nothing can watch the visitor and offer help, because nothing of yours is running there.
- No visitor monitoring on that page. You do not see people browsing the listing; you see them once they click.
- No page-based targeting. Rules that show or hide chat by URL have nothing to act on.
- No embedded window. The conversation happens in a tab of its own rather than in the corner of the host page.
What remains is the part that matters most: a person who wants to talk to you can, from a surface where previously they could not. Treat it as reach, not as a reduced-price version of the widget. On your own site, keep using the full chat widget, which loses none of this.
Point it at your own domain first
The screen carries a note that is easy to skim past: it asks you to set a custom chat URL before you rely on the link. That is the white-label setup, and it changes which domain the chat window opens under.
Without it, somebody clicking your email signature is taken to a chat window on a domain that is not yours. Nothing breaks, but the visual handover is abrupt, and in a marketplace or partner context an unfamiliar domain is precisely the moment a cautious person closes the tab. With it, the window opens under your own address, which is the experience people expect after clicking a link that carried your brand.
It is a one-off configuration rather than a per-link step, so do it once before you start distributing links rather than reissuing them later.
Write the link text for somebody who cannot see whether you are online
The generated anchor is text. It does not show a live online or offline indicator, and it cannot, because showing one would require code running where code is not allowed.
That has a direct consequence for wording. We are online now is a claim your link cannot keep, and it will be false at some point on the same day you write it. Anything that stays true at three in the morning works: Chat with us, Message our support team, Ask a question about this listing. Keep the promise in the link modest and let the chat window handle the honest answer about availability.
The same reasoning applies to the tooltip. It is a good place to set the expectation you actually meet, such as naming the hours your team is normally around, rather than repeating the link text in slightly different words.
Where it earns its place
A few surfaces are worth the effort, and they are the ones where somebody is already thinking about a purchase or a problem.
- Email signatures. Every reply your team sends becomes a route back to a live conversation, which is the cheapest distribution you will ever get.
- Marketplace listings. Buyers with a question about a specific item are the highest-intent audience you have; there is a dedicated walkthrough for adding live chat to an eBay listing that uses this exact link.
- Community and forum posts. Useful where your team answers publicly and occasionally needs to take something private.
- Documents and newsletters. Anywhere a reader is offline from your site but online in general.
One caution worth stating plainly: whether you may place a contact link at all is the host platform's decision, not ours. Several marketplaces restrict off-platform contact, and the rule changes without warning. Read the policy of the place you are posting into before you scale this up.
Availability of the feature itself also depends on your plan. The screen states its own status, showing either that your package includes it or that an upgrade is required, so you will know before you build a workflow around it.
What to measure
The link is easy to scatter and easy to forget, so give yourself a way to tell whether it did anything.
- Chats that arrive with a referring page you recognise. This is the direct signal that a placement is working, and it is visible to the agent at the moment of the conversation.
- Which placements produce conversations at all. Expect a wide spread. Email signatures tend to be steady and low volume; a listing on a busy marketplace can be the opposite.
- What those conversations are about. If listing links generate the same three questions, the listing itself is missing an answer, and fixing the copy is worth more than the chat.
- When they arrive. These visitors are not constrained by your website traffic pattern, and a link in an email footer will find your quiet hours.