A practical guide to Intercom secure mode in 2025

Kenneth Pangan
Written by

Kenneth Pangan

Stanley Nicholas
Reviewed by

Stanley Nicholas

Last edited October 24, 2025

Expert Verified

Let's be honest, we all have a million things on our to-do list, and tweaking security settings can easily fall to the bottom. But when it comes to customer data, some settings aren't just checkboxes; they're the entire foundation of trust. You're using Intercom's Messenger to build great relationships, but are you positive those chats are private? A simple misconfiguration can leave the door wide open for someone to impersonate a user, and suddenly, all their sensitive conversations are exposed.

Forgetting to enable Intercom secure mode is one of the most common, and frankly, dangerous, oversights a team can make. It’s the digital version of leaving your front door unlocked with a welcome mat out. This guide will walk you through what Intercom secure mode is, why it's not something you can afford to ignore, and how to get it set up to protect your customers and your reputation.

What is Intercom secure mode?

In a nutshell, Intercom secure mode is a security feature that double-checks the identity of your logged-in users. Its main job is to make sure the person using the Messenger is who they say they are. This stops a fraudster from pretending to be someone else and getting a free pass to their entire chat history.

Think of it this way: without secure mode, anyone who knows a customer's email address could potentially pop open the chat widget and see all of their past support tickets. That’s a massive privacy disaster just waiting to happen.

You'll probably come across two methods for this:

  1. Identity Verification (The Old Way): This approach used a "user_hash" to verify users. It’s now outdated, and Intercom really wants you to move away from it. If you’re still using this method, it's definitely time for an upgrade. Intercom has a helpful guide on migrating from Identity Verification to JWTs to get you started.

  2. JSON Web Tokens (JWTs) - The Right Way): This is the modern standard everyone should be using. A JWT is like a secure digital passport for your users. Your server creates it, signs it with a secret key, and hands it to Intercom to prove the user is legit.

The main takeaway here is that turning on secure mode is what separates a trustworthy chat experience from a vulnerable one.

Why Intercom secure mode is critical for your business

It’s easy to wave off security settings as a job for the engineers, but the risks of skipping Intercom secure mode are too big to ignore. This isn't about following some vague "best practices"; it's about protecting your business from some very real headaches.

Prevent unauthorized access and user impersonation

This is the big one. Without secure mode, an attacker could load up the Intercom Messenger with a customer's or even an employee's email and get full access to their conversation history. Security researchers have highlighted this as a surprisingly common and damaging misconfiguration.

Just picture it: someone with bad intentions impersonates one of your most important customers. They could easily trick your support team into sharing sensitive account info, making changes they shouldn't, or even helping them take over the account. The hit to your customer relationship and the potential for fraud is huge.

Stop session leakage and protect user privacy

Here's another issue that often gets missed: what happens when a user logs out? If you don't tell Intercom their session is over, their chat can stay active in the browser.

Imagine this: a customer uses a shared computer at a library to chat with your support team. They log out of your app, but you haven't configured Intercom to shut down correctly. A few minutes later, another person sits down, logs into their own account on your app, and is greeted by the previous user's entire private conversation history.

That's a major privacy breach that can destroy trust in an instant. Secure mode, combined with the right logout steps, makes sure one user's data never spills over into another's.

Maintain compliance and avoid legal risks

These days, data privacy is the law, not a suggestion. Regulations like GDPR in Europe and CCPA in California have strict rules about protecting personal information. Customer conversations often contain names, emails, order details, and other private data, and exposing them can land you in hot water.

Leaving your chat widget unsecured isn't just a technical slip-up; it's a compliance problem that can lead to big fines and a damaged reputation. Enabling Intercom secure mode is a basic step toward meeting your legal duties and showing customers you actually care about their privacy.

How to implement Intercom secure mode with JWTs

Okay, so we're all agreed that secure mode is a must. How does it actually work? While your engineers will handle the code, the concept itself is pretty simple. Here’s a quick look at the process and what you’ll need.

The basic workflow for JWT authentication

The whole thing happens behind the scenes in a split second whenever a user logs in:

  1. User Logs In: Your customer successfully logs into your website.

  2. Server Generates JWT: Your backend creates a unique, temporary JSON Web Token for that user. This token contains their user ID and is digitally signed using your secret Intercom API key.

  3. JWT is Sent to the Browser: Your server passes this secure token down to the user's browser.

  4. Intercom Initializes: The Intercom Messenger code on your site starts up and sends the JWT along with its first request.

  5. Intercom Verifies: Intercom's servers get the token, check the signature against the secret key they have, and confirm the user's identity. If everything lines up, the secure chat session loads. If not, access is denied.

This quick handshake ensures that only users who have been authenticated by your system can get into their Intercom conversations.

Key components you'll need

To get this going, your development team will need a couple of things:

  • Your Intercom Secret Key: You can find this in your Intercom settings under Messenger Security.

    Pro Tip
    Treat this key like gold. It should never, ever be visible in your frontend JavaScript code or sitting in a public code repository. It needs to live safely on your backend server.

  • Backend Logic: The JWT has to be created on your server. Just about any backend language (Node.js, Ruby, Python, etc.) has to have libraries to handle creating and signing JWTs.

  • The "Intercom('shutdown')" Command: This part is just as important as the login. You have to call this JavaScript function whenever a user logs out. It tells Intercom to clear the current session and any related cookies, preventing the session leakage we talked about earlier.

The limitations of a manual setup

While setting up JWTs is the right call, let's be realistic: it’s not a five-minute job. It takes developer time to write the server-side logic, test the whole flow, and make sure the "shutdown" function is called every single time a user logs out. It also needs some upkeep, like rotating your secret keys now and then.

Securing the channel is a huge first step, but it doesn't do anything to lower the number of conversations your team has to juggle.

This is where a tool like eesel AI can step in. It’s built to plug directly into the secure setup you already have. With a one-click Intercom integration, eesel AI works within your security framework while adding a powerful automation layer. Instead of just securing the conversation, you can start automating it in minutes, without a long development project.

Beyond Intercom secure mode: Automating support with an AI layer

You've done the work to lock down your Intercom Messenger. Your customer data is safe, and you've patched a major security hole. What’s next? The root of the problem is still there: your support team is manually answering the same questions day in and day out.

This is your chance to go from playing defense to playing offense. By adding an AI layer, you can turn your support from a simple cost center into an efficiency machine. An AI support agent works inside your helpdesk to give instant answers to common questions, which frees up your human agents to handle the really tricky issues.

Here's how a dedicated AI platform like eesel AI builds on your secure Intercom setup:

FeatureIntercom (with Secure Mode)eesel AI (Integrated with Intercom)
User Authentication✅ (Needs manual JWT setup)✅ (Uses the secure setup you already built)
Frontline Support❌ (All handled by human agents)✅ (AI agent answers common questions on its own)
Knowledge SourceLimited to Intercom ArticlesPulls info from past tickets, Confluence, Google Docs, and more
Setup SpeedCan take hours or days of dev workGo live in minutes from a simple dashboard
Testing & ConfidenceYou have to test it manuallySee how the AI would have performed on old tickets
Proactive ImprovementManual ticket analysisSpots knowledge gaps and suggests new help articles

With eesel AI, you get abilities that go way beyond what Intercom offers out of the box. The power to train on your past tickets means the AI already knows your brand voice and common problems. You can run simulations on thousands of old conversations to see exactly how the AI will perform before you flip the switch for customers. Best of all, it unifies knowledge from all your company sources, not just your help center, so answers are always accurate.

Use Intercom secure mode, then automate the conversation

If you remember one thing from this guide, make it this: Intercom secure mode isn't optional. It’s a basic requirement for any business that cares about customer trust and data privacy. Using the modern JWT method is the standard for making sure every user is who they say they are, shielding your customers from impersonation and your business from compliance headaches.

But security is the starting line, not the finish line. Once you've locked the door, the next move is to make your home run more efficiently. Real improvement comes from smart automation. Don't just secure your conversations; automate them.

Adding a powerful, secure, and fully integrated AI agent to your Intercom workspace is the quickest way to cut down on ticket volume, make customers happier, and let your support team focus on what they do best.

Ready to upgrade your Intercom support?

Securing your Messenger is the first step. The next is automating it. With eesel AI, you can deploy an AI agent that learns from your past tickets and resolves customer issues in minutes.

Try eesel AI for free or Book a demo to see it in action.

Frequently asked questions

Intercom secure mode is a crucial security feature designed to verify the identity of your logged-in users. It prevents unauthorized individuals from impersonating your customers and accessing their private chat histories, which is vital for maintaining trust and protecting sensitive data.

Intercom secure mode uses JSON Web Tokens (JWTs) to authenticate users. When a user logs into your site, your server generates a unique, signed JWT that Intercom verifies, ensuring that only authenticated users can access their specific conversation history.

Without Intercom secure mode, your platform is vulnerable to user impersonation, allowing attackers to view or manipulate customer conversations. It also increases the risk of session leakage on shared devices and can lead to severe data privacy breaches and non-compliance with regulations like GDPR or CCPA.

Historically, identity verification with "user_hash" was used, but this method is now outdated. The recommended and modern approach to enable Intercom secure mode is by using JSON Web Tokens (JWTs), which offer a more robust and secure way to authenticate users.

To implement Intercom secure mode with JWTs, your development team will need your Intercom Secret Key (kept securely on your backend), backend logic to generate and sign JWTs, and the "Intercom('shutdown')" command to be called on user logout to clear sessions.

Yes, when combined with the "Intercom('shutdown')" command, Intercom secure mode significantly helps prevent session leakage. This ensures that when a user logs out, their Intercom chat session is properly cleared, preventing subsequent users on a shared computer from viewing past conversations.

While the initial setup of Intercom secure mode with JWTs requires development time to implement backend logic and the logout command, it also involves some ongoing maintenance. This includes tasks like rotating your secret keys periodically to maintain optimal security.

Share this post

Kenneth undefined

Article by

Kenneth Pangan

Writer and marketer for over ten years, Kenneth Pangan splits his time between history, politics, and art with plenty of interruptions from his dogs demanding attention.