WhatsApp, LINE and Viber in one inbox.

In much of Southeast Asia, the customer conversation does not happen in email. It happens in WhatsApp, LINE and Viber, often on a salesperson's personal phone. Leadership cannot see it. The CRM does not record it. When that salesperson leaves, the relationship leaves too.

Bringing messaging into the CRM is one of the highest-value projects a regional enterprise can run. It is also easy to do badly.

Why does messaging belong in the CRM?

Three reasons, in order of how quickly they hurt.

• Visibility. If most sales and service conversations sit outside the CRM, pipeline reports and service metrics describe a fraction of the business.
• Data protection. Customer personal data on personal phones is hard to secure, hard to retain correctly and hard to delete on request.
• AI readiness. An AI agent can only serve customers on channels it can see, using history it can read.

How do WhatsApp, LINE and Viber connect to HubSpot?

The channels do not connect the same way, and the difference matters for budget and timeline.

HubSpot's documentation lists team email, chat, Facebook Messenger, forms, WhatsApp Business and calling as native channels in the conversations inbox. WhatsApp Business requires a Marketing Hub or Service Hub Professional or Enterprise subscription (HubSpot Knowledge Base).

LINE and Viber are not native. HubSpot says you can “install existing apps from the HubSpot App Marketplace, such as WeChat, Telegram, LINE, Viber, Slack, or build your own integration from scratch via the custom channels API”. Custom channels require a Sales Hub or Service Hub Professional or Enterprise subscription (same source). SMS is available with Marketing Hub Professional or Enterprise and an SMS add-on.

In practice, plan WhatsApp as configuration and LINE and Viber as integration work, tested market by market. Our WhatsApp, Viber and LINE answer sets out the options.

What do the WhatsApp rules require?

Meta's WhatsApp Business Messaging Policy shapes the design. Three rules stand out (WhatsApp Business Messaging Policy):

1. Opt-in first. You may only contact people who have given you their number and from whom you have received opt-in permission.
2. The 24-hour window. Outside a 24-hour customer service window, which “opens and resets with each user message”, you may only send approved message templates.
3. Escalation and opt-out. Automated experiences need “prompt, clear, and direct escalation paths”, and you must respect every request to opt out.

Each rule becomes a CRM requirement: a consent property per channel, templates for follow-ups outside the window, an escalation route in every automated flow, and an opt-out process that updates the record everywhere. Local data protection law adds to this in each market. See data protection by country.

How should conversations be routed?

Routing decides whether a customer waits two minutes or two days. We design it around four questions:

• Which market and language? Route by number, channel or the customer's choice to a team that can reply in their language.
• Sales or service? An enquiry about a new product and a complaint about a delivery belong to different teams.
• Existing owner? If the customer has an account manager, the conversation should reach them, with cover when they are away.
• Working hours? Decide what happens out of hours: an agent, an auto-reply, or a promised callback.

Every conversation should end on the customer record, linked to the right contact, company, deal or ticket. That is what turns messaging from a channel into data.

Where do AI agents fit?

Only after the channel, consent and routing work. HubSpot's Customer Agent can be deployed to WhatsApp and to custom channels, among others (HubSpot Knowledge Base), and HubSpot's help desk documentation confirms the agent can respond on custom channels, with tickets reassigned by handoff settings if it cannot resolve them (HubSpot Knowledge Base).

That makes the sequence clear: capture the conversations, clean up routing and consent, then let an agent take the first-wave questions. We set out how in Customer Agent in practice.

How do you move teams off personal phones?

This is a change project more than a technical one. Salespeople guard their chats because those chats are their relationships. Three things help.

1. Make the CRM easier than the phone. Mobile access, templates, quick replies and full history in one place.
2. Move existing customers deliberately. Introduce the business number to each customer, with consent, rather than switching overnight.
3. Measure it. Track the share of conversations captured in the CRM by team and market, weekly, until it is the default.

Leaders should set a date after which customer conversations on personal numbers are not supported. Without a date, the old habit wins.

How do you roll out across markets?

Channel habits differ across the region, so the rollout should too. Start with one market and the channel that carries most of its customer conversations. Connect it, set consent and routing, train the team, and measure capture for a few weeks before moving on.

Then add the next market, reusing the same consent properties, templates and routing logic, and adjusting only for language, channel mix and local law. Each market needs a local champion who owns adoption. Avoid the temptation to switch on every channel in every market at once; integration issues and training gaps compound, and teams fall back to their phones.