When a customer is logged in to your website and opens the chat, your team should not have to ask for their name and e-mail. Talkmio can identify logged-in users: the website passes the visitor’s name and e-mail to the chat, and your Inbox shows who is writing. The integration pages describe this as an option in the WordPress plugin and in the modules for PrestaShop, OpenCart, Magento, Joomla, Drupal, TYPO3 and Odoo, as a few lines of code for Shopify, Vue and React, and as a package feature in Laravel. This guide explains what the feature does, why it saves time, how to set it up on the most common platforms, how to protect your visitors’ privacy and how to test that it works and does not leak.
The facts come from the integration pages and documentation on talkmio.com. The option names and code lines are quoted from there in simple form, and you should copy the current version from the integration page for your platform before you use it.
What It Means to Identify Logged-In Users
Normally, a visitor to a website is anonymous. The Talkmio Inbox shows what it knows from the visit itself: the country, city, page, device, browser and source, according to the documentation. That is useful, but it does not tell you who the person is. When you identify logged-in users, your website adds the name and e-mail address that the person already gave you when they created their account. The chat then carries these details into the Inbox, so your team sees a name and an e-mail instead of an anonymous visitor.
The WooCommerce integration page describes the purpose well: the customer’s name and e-mail are passed on, so that Mio and your team see who is asking about an order. For businesses with customer accounts, such as shops, membership sites and software services, that is a real saving: the first question of every chat, “who are you and what is your e-mail?”, disappears.
Where You Can Identify Logged-In Users
The feature is available in different forms, depending on the platform. The table summarises what the integration pages describe.
| Platform | How it works | Notes from the integration page |
|---|---|---|
| WordPress and WooCommerce | An option in the plugin settings | Passes name and e-mail of logged-in users to the Inbox; a second option hides the chat for logged-in administrators |
| PrestaShop | Option in the module | Identifies logged-in customers; multi-shop is configured per shop |
| OpenCart, Joomla, Drupal, TYPO3, Odoo | Built into the extension or module | Identifies logged-in customers, users or portal users |
| Magento 2 | Option in the module | Uses the customer session and is described as safe with the full-page cache |
| Shopify | A few lines in theme.liquid, optional | Shown only when a customer is logged in |
| Vue and Nuxt | A variable set before the script | For signed-in users, optional |
| React and Next.js | The user property of the component | Pass name and e-mail of the current user |
| Laravel | Built into the package | Can be turned off with a setting |
On platforms that are not on this list, the same idea works with a plain snippet, as long as your page can write the name and e-mail of the logged-in user into a variable before the Talkmio script loads, and only for logged-in users.
Why It Helps Your Team and Your Customers
- Faster answers. Nobody has to ask for the name or the e-mail, so the conversation starts at the real question.
- Better context. With the e-mail address, you can find the customer’s account, orders or subscription in your own system in seconds.
- Returning customers. Contacts keeps everyone who ever wrote to you, with their conversation history, so a name and an e-mail make it easy to recognise the same person next time.
- Safer hand-offs. When Mio hands over an order question, the agent already knows who is asking.
- Less friction. You can think about keeping the pre-chat form lighter for people who are already known.
Our guide to live chat contact history explains how to use past conversations, and the guide to where-is-my-order chats shows why knowing the customer matters for order questions.
A Short Example From a Shop
A customer logs in to an online shop, opens the chat and writes that a parcel has not arrived. Without identification, the conversation starts with questions: what is your name, what is your e-mail, what is the order number? With identification, the Inbox already shows the name and the e-mail, and the agent opens the order system, finds the customer by e-mail, sees the parcel and answers in a minute. Mio, which hands specific order questions to a person, has already passed the chat on with the history. The customer did not repeat anything. Over a month with hundreds of chats from logged-in customers, the minutes saved add up to real hours, and the customer’s impression of the shop is better.
The same pattern works for a software service: the agent sees which customer is writing about billing or a login problem. And for a membership site: the agent sees who the member is and can answer about their access. In each case the benefit comes from one rule, which is that a person who has already told you who they are should not be asked again.
Set It Up on WordPress and WooCommerce
The official Talkmio WordPress plugin, described as working with WooCommerce, has two options in its settings. One is to identify logged-in users, which passes the name and e-mail to the Inbox. The other is to hide the chat for logged-in administrators, which keeps your own visits out of the visitor list. For a shop, switch on the first option and consider the second, so that your own team does not appear as visitors. After you save, log in as a test customer, open the chat and write a message, then check the Inbox. Our guide to live chat for WooCommerce goes through the rest of a shop setup.
Set It Up on Shopify
Shopify needs no plugin. The integration page describes adding the Talkmio line to the theme file theme.liquid before the closing body tag. To identify logged-in users, the page adds an optional block above the widget line: a conditional that checks whether a customer is logged in and, only then, writes the customer’s name and e-mail into a variable that the chat reads. Copy the exact block from the Shopify integration page, paste it above the widget line and save. Because the block runs only when a customer exists, anonymous visitors remain anonymous. Our guide to adding live chat to a Shopify store covers the whole install.
Set It Up in Code: Vue, React and Laravel
For a site that you build yourself, the pattern is the same. In a Vue or Nuxt project, set a global variable with the name and e-mail of the signed-in user before the script loads, for example window.__TALKMIO_USER__ = { name, email }, and only when a user is signed in. In a React or Next.js project, the component accepts a user property, so you pass the current user’s name and e-mail to it. In Laravel, the package identifies the authenticated user by default, and a setting in the environment file turns the identification off if you do not want it. Whatever the framework, the rule is to send only logged-in users and only the two fields that the Inbox needs.
Privacy First: Pass Only What You Need
A name and an e-mail address are personal data. Passing them to a chat is a decision, not a technicality. Four habits keep it responsible.
- Pass only the name and the e-mail. Do not add phone numbers, addresses, order contents or anything sensitive.
- Say so in your privacy policy. Explain that when a customer is logged in and uses the chat, the name and e-mail are shared with the chat service. The documentation says that data is stored in the EU (Germany), and that only the conversation text and relevant knowledge base excerpts are sent to the AI model provider.
- Limit who can see it. Give Inbox access to the people who need it and use the Agent and Admin roles with care.
- Keep and delete deliberately. Decide how long you keep conversations. The documentation says you can export or delete your data at any time by writing to support.
Whether you need consent or can rely on another legal basis depends on your country and your situation, so ask your adviser. Our guide to GDPR and live chat gives the general picture, and the guide on legitimate interest and live chat explains one common basis.
Test That It Works, and That It Does Not Leak
A short test protects you from two kinds of mistake: the feature not working, and the feature working for the wrong person.
- Log in as a test customer with a test name and an e-mail address that you own.
- Open the chat and write a message. In the Talkmio Inbox, check that the conversation shows the test name and e-mail.
- Log out, open a private window and write a message as an anonymous visitor. The conversation must show no name and e-mail.
- Log in as a second test customer on the same device and check that the second name appears, not the first.
- If your platform uses a page cache, repeat the test with the cache on.
The last two steps matter most. If a page that contains one customer’s name is stored in a cache and served to another visitor, the second visitor could appear in the chat under the first customer’s name. The Magento page says its module is safe with the full-page cache, because it uses the customer session. If you add the variable by hand, make sure the personalised part is never stored in a shared cache. A cache stores pages to serve them quickly, and personalised data does not belong in it.
Pre-Chat Forms and Known Visitors
The widget settings let you choose a pre-chat form that can be none, optional or required. When a visitor is identified, asking again for the name and e-mail is redundant. The documentation does not say how the form behaves for identified users, so test it: log in, open the chat and see whether the form appears. If it does and you do not need it, consider setting it to none for the whole site, since anonymous visitors may still reach your team without a form. Remember that when your whole team is offline, visitors are asked for an e-mail address before the first message, and an identified visitor already has one.
Frequently Asked Questions
What does it mean to identify logged-in users in Talkmio?
Your website passes the name and e-mail of a logged-in visitor to the chat, so your Inbox shows who is writing instead of an anonymous visitor. The integration pages describe it for WordPress, WooCommerce, PrestaShop, Magento, Shopify, Laravel, React and more.
Is it switched on automatically?
It depends on the platform. The WordPress plugin has an option for it. On Shopify and Vue it is an optional piece of code. In Laravel the package identifies the authenticated user and has a setting to turn it off. Check your platform’s integration page.
What data is passed to the chat?
The integration pages describe the name and e-mail of the logged-in user. Pass only those two fields and only for logged-in users. Do not add phone numbers, addresses or order contents, and mention the sharing in your privacy policy.
Can it show the wrong name to a visitor?
It can if personalised page output is stored in a shared cache and served to others. The Magento module is described as safe with the full-page cache. If you add the code by hand, keep the personalised part out of shared caches, and test with two accounts.
Can I hide the chat from my own team?
Yes, on WordPress. The plugin has an option to hide the chat for logged-in administrators, which keeps your own visits out of the visitor list. On other platforms, check the integration page or use your own condition in the code.
Do I need consent?
It depends on your country and your situation. The data is personal data, so decide your legal basis with your adviser, state the sharing in your privacy policy and keep to the minimum needed. The documentation says data is stored in the EU and can be exported or deleted.
The Bottom Line
When you identify logged-in users, your team stops asking who is writing and starts answering what they want. Use the plugin option, the module setting or a few lines of code, pass only the name and the e-mail and tell your customers in your privacy policy. Then test with two accounts and with the cache on. Start free with Talkmio, install the chat and switch on identification for your logged-in customers once you have checked the privacy side.
