What the card knows before the visitor types
A visitor opens with hi, is this compatible with our setup? and you have no idea which product they mean. The answer is usually already on your screen: they were reading a specific page thirty seconds ago, and they got to it from somewhere.
The visitor card on the right rail of your console collects that. Collapsed, it is a small pill showing a flag, a status dot, and a city. Click it and it opens into the full reading: email if they have given one, location, IP address, browser and platform, the page they are on, the referrer that sent them, the trail of pages they walked, and how long the session has been alive.
Everything on it is a live read of the session already in your browser. The card makes no server call of its own, stores nothing, and disappears when the chat does. It is a different instrument from the visitor history that survives across visits — that one remembers people, this one describes the session in front of you right now.
The trail is distinct pages, not page views
The Visited pages list is the most useful part of the card and the part most often misread. It shows the route newest-first, numbered, with the current page at the top, and it opens up to twenty rows.
The important detail: the list is deduplicated by URL. A visitor who bounced between your pricing page and a feature page six times before messaging you shows two rows, not twelve. The step numbers count distinct pages, so they are a map of where someone went, not a measure of how much time or how many loops they spent getting there.
That makes the trail excellent for one question and useless for another. It answers what were they trying to work out? very well — three feature pages then pricing then back to a feature page is a person building a comparison. It cannot answer how hard did they have to look?, because repeat visits collapse into one row.
The list only appears when there is more than one distinct page. A visitor who landed and immediately opened the chat gets no trail section at all, which is itself information: they did not browse, they arrived and asked.
Where they came from, and what a referrer is worth
The From row is the referrer the browser reported when the visitor first reached you, shortened to its domain so it stays glanceable. It is the single highest-value field on the card for the first thirty seconds of a conversation, because it tells you which conversation the visitor thinks they are continuing.
Someone arriving from a comparison article has been reading about your competitors. Someone arriving from a partner site has been told you are the recommended option. Someone arriving from an ad clicked a specific promise, which is on the landing page in the trail below. In each case the referrer changes the right opening reply, and none of it requires you to ask.
Treat it as a hint rather than a fact. Referrers go missing routinely: a link from an encrypted page to a different site, a browser privacy setting, an app that opens links in its own web view, or a visitor who typed your address directly will all produce no referrer at all. An empty From row means the browser did not say, not that the visitor came from nowhere.
Both the page link and the referrer link open in a new tab, and both are checked before they are turned into links. The visitor controls those strings, so anything that is not an ordinary web address is rendered as plain text instead of something clickable.
Geography is a guess, and the flag is a lookup
The location line reads city and country, with a flag when one can be worked out. Two things are worth knowing about it.
The first is that it is derived from the network address, which is a reasonable guess and not a fact. Corporate networks, mobile carriers and VPNs routinely place a visitor in a city they have never been to. Reading the location back to a visitor as though you know where they are sitting is a good way to sound wrong and slightly creepy at the same time. Use it to pick a plausible timezone or a currency, not to make claims.
The dashboard's visitor map is a separate lookup with its own, coarser rules, which is why the same person can appear with a city on this card and as a country-level pin on the map. Why your visitor map pins people in the middle of a country explains where those coordinates come from.
The second is smaller and easy to misread. The flag comes from a lookup table of common English country names — about sixty of them. A country outside that list still shows its name in full, just without a flag, and the collapsed pill will show the city on its own rather than the usual city-and-country-code form. A missing flag says the name was not in the table. It does not mean the location is unknown.
The row beneath it, browser and platform and culture, is worth a glance when someone reports something not working. The culture code in particular is the visitor’s own language preference, which occasionally explains a confusing message better than anything they have typed.
Copy summary takes everything on the card and writes it to your clipboard as a small formatted block: name, email, location, IP address, browser, current page, referrer, session age, and up to ten pages of the trail. It exists so that handing a conversation to a colleague, or attaching context to a ticket, does not mean retyping nine fields.
Notice what is in that block. It contains an IP address and a browsing history, which is to say it contains personal data, and the moment you paste it somewhere it inherits that system’s retention and access rules rather than the chat’s. Pasting it into a ticket on the account it belongs to is ordinary. Pasting it into a general team channel is a copy of someone’s location and browsing trail sitting in a searchable archive that nobody will ever prune.
If your retention policy has a defensible answer for chat transcripts, it needs the same answer for the places this button ends up. That is worth ten minutes of thought once, rather than a decision made per paste.
One practical note: the confirmation on the button fires when the copy is requested, not when the browser confirms it landed. If a paste comes out empty, the click was fine and the browser declined — click it again with the console window focused.
Reading intent without interrogating anyone
The habit worth building is to read the card once, before your first reply, and then leave it alone.
The trail plus the referrer usually gives you the visitor’s actual question before they have finished phrasing it. Someone who came from a search result, read two documentation pages, and then opened the chat on the pricing page is not asking about pricing — they are asking whether the thing they just read is available on the plan they can afford. Opening with that, rather than with how can I help?, saves two exchanges.
The discipline is to use it silently. Nothing about the card is hidden from the visitor in principle — it is their own browser reporting where they are — but reciting it back (I see you have been on the pricing page four minutes) reliably makes people uncomfortable. Let it shape the reply rather than becoming the reply.
There is also a small live signal in the pill: the status dot pulses while the visitor is typing. When you are holding several chats, that is a better cue than the transcript for knowing whether to wait a beat before sending your own message and cutting across theirs.
How MyLiveChat fits
The visitor card is part of the agent console and needs no setup. Open a chat, click the pill on the right rail, and it fills in from whatever the session already carries. Click the pill again to collapse it, and the collapsed or expanded choice is remembered per visitor for as long as the chat is open.
How much it shows depends on what reached us. Location and browser details come from the connection; email and name appear if the visitor gave them, in a pre-chat form or through your own page code. A card that looks thin is usually reporting an anonymous visitor accurately rather than failing.
For where the wider traffic picture lives, and how to think about arriving-from-somewhere-else visitors as a group rather than one at a time, the referral traffic guide is the companion to this one.