Your healthcare chatbot should be available on Viber and Line

Updated on July 28, 2026

If your patient support chatbot only lives on your website and WhatsApp, you’re already excluding a meaningful slice of the population you serve.

Healthcare providers with a diverse international audience miss this in two common ways:

1. A hospital network serving Eastern European, Russian-speaking, or Filipino communities will have patients who default to Viber for messaging.

2. A clinic with a significant Japanese, Thai, or Taiwanese patient population will have patients who use Line.

Viber has hundreds of millions of active users concentrated in specific regions, and Line is the dominant messaging platform across much of East and Southeast Asia. If your chatbot isn’t there, you’re asking those patients to switch apps just to talk to you, and a lot of them won’t.

These channels can be onboarded without changing anything on your backend. This article covers why these platforms matter and how to add them:

1. The channel gap most healthcare providers don’t notice

2. You don’t need an IT team to build Viber or Line chatbots

3. How to connect a patient support chatbot with Viber and Line

4. How to track if the new channels are working

5. Conclusion

The channel gap most healthcare providers don’t notice

Most healthcare organizations build out their patient communication channels in a predictable order. 

1. Website chat first
2. WhatsApp (because patients ask for it directly)
3. SMS or email

Viber and Line rarely make that list, not because they’re unimportant, but because nobody on the team is actively using them, so nobody thinks to ask.

This is a visibility problem. The issue is not that messages arrive on those apps and sit unanswered. Patients never start the conversation at all. They call your front desk during business hours instead, or ask a family member to translate and relay a message through WhatsApp.

That friction shows up as call center load and as no-shows from patients who couldn’t easily confirm an appointment. It also shows up as lower satisfaction scores from a group of patients you might not be measuring separately.

The scale here isn’t trivial:

1. Rakuten’s own most recent monthly active user figure for Viber sits at roughly 209 million, and the app claims close to 90% phone penetration in Greece, Bulgaria, Serbia, and Belarus. It is the leading messaging app in Ukraine and Moldova, and the Philippines ranks among its top five markets worldwide.

2. Line’s numbers are better documented: LY Corporation reported 194 million monthly active users as of March 2025, and it remains the leading messaging app in Japan, with significant reach across Taiwan, Thailand, and Indonesia.

The fix starts with a simple check: pull your patient demographic data and see it against where Viber and Line have strong regional penetration.

• If you serve patients from Russia, Eastern Europe, Greece, or the Philippines, Viber is worth a look.
• If you serve Japanese, Thai, Taiwanese, or Indonesian patients, Line almost certainly matters. 

That data tells you which channels are worth adding. And adding them, as the next section covers, is far lighter work than most teams expect.

You don’t need an IT team to build Viber or Line chatbots

Once the demand case is clear, the next question is usually about effort: what does it actually take to get a bot live on Viber or Line?

For most teams, the honest expectation is that this looks like a project. A timeline, a developer, a sprint to rebuild the intake flow and FAQ logic for the new channel, then QA to make sure it behaves the same way it does everywhere else.

That expectation is what keeps Viber and Line off the roadmap, even after a team agrees the patients are there. Nobody wants to open a new workstream for a channel that might only serve a fraction of their patient base.

With Kommunicate, the bot you’ve already built for your website or WhatsApp doesn’t get rebuilt or recreated when you add a new channel. 

The same Kompose flow, built once in our no-code bot builder, runs on every channel you connect. Connecting Viber or Line is a configuration step, not a development project. You’re not maintaining three versions of your appointment scheduling flow or your insurance FAQ logic. You’re maintaining one, and it shows up everywhere your patients already are.

This matters specifically for healthcare, where a wrong answer about medication timing or pre-appointment instructions carries real consequences. A patient asking whether to fast before a blood test gets the same answer on Line as they would on your website.

How to connect a patient support chatbot with Viber and Line

Both Viber and Line follow the same basic pattern, and neither requires touching your bot’s underlying logic.

Viber

1. Start by creating a bot account at partners.viber.com, which generates an API token. 
2. Enter that token into the Viber integration section of your Kommunicate dashboard.
3. Once connected, you publish the bot from within the Viber app.

Line

1. In the LINE Developers Console, set up a Messaging API channel and copy the Channel access token and Channel secret.
2. Enter those credentials in the Line integration section of your Kommunicate dashboard, and the connection is active from there.

In both cases, the work is account setup and credential entry, done once. There’s no flow-building step, because the flow already exists. 

For a team that’s already comfortable navigating their Kommunicate dashboard, this is realistically a sub-hour task per channel, including the time spent setting up the bot account on the Viber or Line side itself.

If you want to build a chatbot using Kompose, we also have a guide that will help you through each step of the process.

How to track if the new channels are working

The metrics worth watching are the same ones you’d track for any channel. What’s different with a newly launched channel is the baseline.

What’s different with a newly launched channel is the baseline. Don’t expect Viber or Line to match your website chat volume in week one. The patients who’ll use these channels are often the ones who weren’t engaging with your existing channels at all, so this channel adds to your total volume rather than pulling it away from somewhere else.

If resolution rates on the new channel lag behind your established channels while running the identical flow, the cause is usually the channel’s UX rather than the bot logic. How messages render and how quickly patients expect replies both differ by app.

The patients reaching you through Viber or Line were often the hardest ones to reach before. Getting the channel connection right is the easy part. Making sure those patients get the same quality of support as everyone else is the part worth paying attention to.

Conclusion

For healthcare organizations serving diverse populations, channel coverage is part of equitable access. If a patient can only reach you through an app they don’t use, they’re effectively locked out of support, even if your bot is excellent everywhere else.

Extending to Viber and Line doesn’t have to compete with your other priorities for engineering time. Since your existing bot flow carries over automatically, the work is mostly about connecting the channel and watching how patients respond.

If you’d like to see how this works with your own bot flows, book a demo with Kommunicate, and we’ll walk you through connecting a new channel end-to-end.