Viber and Intercom Integration: The Complete Guide

If a customer messages you on Viber while your support team is sitting in Intercom, it creates a gap in your process. Your team has to shuffle through tools to get every message, and if the voluome is high enough, many conversations will just get dropped.

In this guide, we show you how to fix this disconnect. We’ll walk you through how Viber's business messaging works, whether you need Viber Bots or Viber Business Messaging, and how to get those conversations in your Intercom inbox.

Why connect Viber to Intercom

Because in a specific set of markets, Viber is the channel your customers use every day. Viber intercom integration matters because Viber's coverage sits above 90% in Bulgaria, Greece, and Ukraine, and well above 50% in Hungary, Iraq, and the Philippines.

In the Balkans, parts of Central and Eastern Europe, Southeast Asia, and the Middle East, Viber operates like a default communication app, the same way WhatsApp does everywhere else.

That has a direct, practical consequence for you. If you sell into Ukraine, Serbia, Greece, Vietnam, or the Philippines, Viber business messaging isn't optional. Your customers will message you where they already message everyone else, and if you're not there, you're invisible to your customer base.

Here's where it gets frustrating for support teams. Most support tooling, including most native integrations, gets built around WhatsApp first because it has the bigger global user base. Viber ends up as an afterthought, which pushes teams supporting Viber-first markets into manual workarounds:

• Someone logs into a separate Viber app and checks it manually a few times a day
• Anything urgent gets copied into a spreadsheet or Slack message for the rest of the team
• Nobody has a clean view of who's actually handling which conversation

You already know what that costs you:

• A separate app your team has to remember to check
• No shared history with the rest of your multi-channel support setup
• No reporting on response times or volume
• No clear ownership over conversations

That's the exact problem Viber customer support runs into when it stays siloed, and it's exactly what connecting Viber to Intercom fixes.

Viber Bots vs. Viber Business Messages

Viber runs two completely separate business products, and picking the wrong one means rebuilding your setup later.

Before you touch anything in Intercom, you need to know which one you're actually integrating, because Viber Bots and Viber Business Messages (VBM) differ in setup path, pricing, identity model, and what you're even allowed to send.

Viber Bots

A Viber bot connects through the Viber Bot API, a REST API you can also build against using Viber's NodeJS or Python libraries. Here's what defines it:

• Subscriber-based: the user has to message you first and subscribe before you can message them back. You cannot cold-initiate a conversation, ever.
• Identified by Viber ID, not phone number. Flag this now, because it directly shapes how you'll handle contact matching once conversations hit Intercom (more on that in the identity section below).
• Rich media is fully supported: text, pictures, video, files, location, stickers, contact cards, carousels, URL buttons, and custom keyboards.
• One free welcome message goes out the moment a user opens the chat, before they've subscribed. It's not billed.
• Verified bots get a badge, which builds trust the same way a verified WhatsApp Business account does.
• Setup isn't self-serve anymore. Since February 2024, you apply either through one of Viber's official partners or directly with Viber, and every application goes through manual review and a signed commercial contract.

Viber Business Messages (VBM)

VBM is Viber's enterprise messaging product, and it works completely differently:

• Runs on phone numbers, not Viber IDs, so you can message people already in your customer database, not just people who found you on Viber first.
• Partner-only, no direct application path with Viber at all.
• Built for broadcast and templated messaging at volume.
• More restrictive on content: transactional messages are text-only, no rich media allowed.
• No promotional content in your first message to a customer, full stop.
• Message templates only apply in Russia, Belarus, and Ukraine, and businesses based in those markets need separate accounts for in-region and out-of-region customers.
• Traffic is classified as regulated or non-regulated (gambling and microcredit fall under regulated, most standard industries don't), and that classification changes your pricing.
• Domestic and international rates differ, and if you operate across borders, you can get billed both.
• SMS failover kicks in if a message doesn't land on Viber.

Viber Bots vs. Viber Business Messages: the comparison

Which one do you need?

If you're starting from scratch and your goal is customers messaging you and your team replying, you want a Viber bot. It's built for exactly that kind of viber customer support conversation, and it's the product this guide assumes from here on out.

If you already have a customer phone number database and need to reach people proactively, or send at real volume, you need VBM instead, and that path runs through Viber's official partners rather than the setup steps in this guide.

The 24-hour session, and what it costs you

If you've ever worked with WhatsApp's messaging window, Viber's session model will feel instantly familiar. The moment a subscriber sends your bot a message, a 24-hour session opens, and every message inside that window is treated the same way WhatsApp treats a conversation inside its own session: unlimited and free.

Here's how the mechanics actually work:

• The session opens the moment a subscriber messages your bot
• It renews every time the subscriber sends another message, restarting the 24-hour clock
• Messages exchanged inside an active session are unlimited and not billed by Rakuten Viber
• Messages sent outside a session are classified as chatbot-initiated messages, and those are charged individually
• If a subscriber replies to one of your chatbot-initiated messages, that reply reopens a session, so everything that follows in that window goes back to being free
• The one welcome message you're allowed to send before someone subscribes doesn't count as chatbot-initiated, so it's never billed either

What this actually means for how you build your workflows

Your cost profile comes down to one simple question: are you responding, or are you reaching out first?

Reactive Viber customer support, meaning a customer messages you and your team replies within that 24-hour window, is effectively free at the Viber layer, no matter how many messages go back and forth.

Proactive outreach is where cost shows up: a shipping update, a re-engagement nudge, anything you send after the session has already closed gets billed as a chatbot-initiated message.

If your use case is support, structure things so agents reply promptly and keep the session alive rather than letting it lapse and having to pay to reopen it.

If you're planning proactive campaigns on top of support, budget for those separately, since chatbot-initiated pricing varies by market and by partner and isn't something you can pin to a flat number here. Your Viber partner will give you the actual rate card for your region.

How to connect Viber to Intercom with Octopods

Octopods is an integration platform that connects messaging channels like Viber, WhatsApp, Telegram, and SMS directly into your CRM, so this section walks you through connecting Viber to Intercom specifically using it.

What you need before you start

• A Viber account on the mobile app, with a verified phone number
• A Viber Business account, created through the Viber Admin Panel using that same number
• A bot created inside the Admin Panel, along with the auth token it issues you
• An Intercom workspace, plus admin access to Octopods

Steps to connecting Viber to Intercom

1. Create the bot in the Viber Admin Panel. You'll set a name, a category and subcategory for Viber's public directory, and a description. Once you confirm creation, Viber shows you the auth token on the confirmation screen. Save it, you'll need it in the next step.

2. Connect it to Octopods. The auth token goes into Octopods, which uses it to set the webhook Viber needs to talk to your integration. Setting this webhook is also what makes your bot's 1-on-1 conversation button appear.

3. Test it before you trust it. Pull up your bot's URI or QR code from the Admin Panel, message it yourself like a customer would, and confirm the conversation lands in your Intercom inbox. Then reply from Intercom and confirm your reply actually arrives back on Viber.

4. Go live. Publish the bot, then share the deeplink or QR code wherever your customers will actually find it, your website, your email signature, your support pages.

For the exact click-by-click setup, Octopods has a step-by-step Viber setup guide that covers every screen.

One thing that trips people up constantly: the bot has to be created from a phone with a verified Viber account. You can’t do this whole process from a desktop. Have your phone ready before you start.

How Viber messages appear in Intercom

Once you connect Viber to Intercom, a Viber conversation shows up exactly like any other conversation in your inbox.

Everything your team already relies on in Intercom just works: tags, saved replies, assignment rules, internal notes, and workflows all apply to Viber the same way they apply to email or web chat.

What actually comes through

On the way in, customers can send you text, images, video, files, stickers, and location, and all of it lands in Intercom the way you'd expect.

Outbound is a little more specific: carousels and other rich media go out through the Octopods API, so if your team wants to send something more visual than a plain reply, that's the path.

Segmentation and routing

When a contact reaches you through Viber, Octopods sets custom data attributes on that contact, and those attributes are what make filtering, segmentation, and automatic assignment possible. This is where Viber Business Messaging actually earns its keep operationally.

Say you've got separate support teams covering different regions: you can build an assignment rule that routes any conversation carrying the Viber channel attribute straight to the team that covers that market.

Workflows still apply, session rules and all

Your existing Intercom workflows fire automatically on Viber conversations too, including proactive messages and automated follow-ups.

The one thing to keep in mind: everything from the session rules covered earlier still applies here. A workflow that tries to send a follow-up outside an active 24-hour session becomes a chatbot-initiated message, and gets billed accordingly. So if you're building automation on top of Viber, design it with the session window in mind, not around it.

Why you'll want to report on Viber separately

Once volume picks up, segment Viber out from your other channels in reporting rather than lumping it into your overall numbers.

The reason is simple: response time expectations aren't the same across channels.

How Viber identity and contact matching works

Here's the part most teams don't think about: Viber Bots identify subscribers by a Viber ID, not a phone number. That means a customer who messages your bot arrives in Intercom without the one identifier your CRM is probably built around.

If you've already run into this exact problem with Telegram user identity, you're about to see the same story play out on Viber.

What you actually get, and what you don't

When someone messages your Viber bot for the first time, you get their Viber ID, their display name, and their profile picture if they've set one.

What you don't get is a phone number, an email address, or anything else that would let you automatically match them against a customer record you already have.

Why this creates duplicate contacts

TIf a customer emails you today and then messages your Viber bot next week, Intercom has no way of knowing those are the same person unless something explicitly ties the two together.

Instead, you end up with two contact records for one human: one built from their email, one built from their Viber ID.

Practical ways to handle it

You can't eliminate this entirely, but you can catch most of it with a few habits baked into your workflow:

• Ask for an identifying detail early, like an order number or the email address on file, right at the start of the conversation, before the chat moves into troubleshooting
• Record the Viber ID as a custom data attribute on the contact the moment it comes in, so it's searchable later even if you can't merge right away
• Merge contacts once you can confirm a match, using whatever identifier the customer gave you, rather than guessing based on name or timing alone

None of this happens automatically. It's a habit you build into how your team opens a Viber conversation, not something Octopods or Intercom solves for you out of the box.

Why VBM doesn't have this problem

TBecause VBM runs on phone numbers instead of Viber IDs, it matches cleanly against a customer database you already have, so if you're using VBM to reach an existing list, you skip this whole identity problem.

One thing worth flagging: data requests

A Viber ID still counts as personal data. If a customer sends you a GDPR-style access or deletion request, you need to be able to locate everything tied to their Viber ID, not just their email, which is exactly why recording it as a custom attribute from day one matters more than it looks like it does.

Does Viber allow proactive messaging?

Short answer: not to anyone who hasn't already messaged you first. If you're running a self-serve Viber bot, Viber doesn't permit unsolicited outbound messages.

You can't buy a list of phone numbers and start a bot campaign the way you might imagine doing with email. State that plainly now, before you build a campaign around an assumption that isn't true.

What you can actually do

Once someone has subscribed to your bot by messaging it first, you can message them proactively after that. Those messages are billed as chatbot-initiated whenever they land outside an active 24-hour session, the same billing rule covered earlier.

Consent still applies, even to subscribers

Even with an existing subscriber, consent isn't a one-time checkbox you get to ignore afterward. Users can opt out or block your bot at any point, and once they do, that's the end of that conversation thread, permanently, not until they reply again.

If you need real broadcast, that's a VBM capability

If your goal is closer to a marketing send, reaching a large existing customer list at once, that's not something Viber Bots are built for.

Broadcast at scale sits under Viber Business Messages, not Bots, which is the same Bots-vs-VBM distinction from earlier in this guide showing up again here.

Common Viber Intercom setup mistakes

Here's what trips teams up most often when setting up a Viber Intercom connection, and how to fix or avoid each one.

• Picking Bots when you actually needed VBM: Before you build anything, ask yourself honestly whether you're waiting for customers to message you first, or whether you need to reach people who haven't contacted you yet. If it's the second one, stop and look at VBM before you touch the Bot API.
• Expecting to message customers first: Build your rollout plan around driving customers to message you first (a link on your site, a QR code, a mention in your email signature), rather than assuming you can import a contact list and start messaging.
• Invalid auth token: Go back to the Viber Admin Panel and re-copy the token directly rather than retyping it from memory or a note. If it still fails, regenerate the token from the Admin Panel and reconnect with the fresh one.
• Messages suddenly stop reaching Intercom: Go to the channel's detail page and use the reconnect action there. It's built to resolve exactly this kind of dropped connection without you having to redo the whole setup.
• A weak bot profile: Treat this like you'd treat any other public bio. Write a clear, specific description, pick the category that actually matches what you do, and use a real avatar, not a placeholder.
• No plan for identity from day one: Put the identity approach from earlier in this guide (asking for an order number or email early, recording the Viber ID as a custom attribute, merging when you can confirm a match) into place before volume picks up, not after.
• Assuming rich media round-trips both ways: Remember that rich outbound media goes out through the Octopods API, not the composer. If your team needs to send a carousel, that's a workflow or API call, not a manual reply.

If you're running Telegram alongside Viber, Telegram Intercom integration has similar issues, often for near-identical reasons.

Wrapping up

Viber isn't complicated once two things click for you: the opt-in model that governs who you can message and when, and the split between Bots and VBM that determines which product fits what you're trying to do.

Get those two pieces straight, and everything else, the session rules, the identity quirks, the setup steps, falls into place around them. Once you're connected, a Viber conversation just shows up in Intercom like any other conversation, no separate inbox, no extra tab your team has to remember to check.

If you're ready to set it up, Octopods connects Viber to Intercom, and the full setup walkthrough covers every step from here.

Frequently Asked Questions