Zoho SalesIQ WhatsApp Integration, 11 Field Edges and 2026 Pricing

TL;DR

A SalesIQ WhatsApp integration connects a business’s WhatsApp Business number to Zoho SalesIQ, so inbound WhatsApp messages land in the same operator queue as web chat and other channels, the Zobot automates the first stretch of the conversation, and the transcript can push to Zoho CRM when the operator finishes. For a business already running on Zoho, the integration turns WhatsApp from a side channel into a tracked, routed, reportable surface.

The sequence - Choose the path first. Design the handoffs second. Treat pricing and roadmap claims as time sensitive.

This guide gives a business reader the mental picture, a technical reader the field edges Zoho’s own setup guide does not foreground, and both a short pre launch test plan. CRM direct WhatsApp and Marketing Automation campaigns are separate Zoho paths with different setup models and sit outside the scope of this guide. Shared bundle configurations are covered here only where they affect SalesIQ behavior.

What a SalesIQ WhatsApp integration gives the business

Four concrete capabilities land once the integration is live:

• Inbound WhatsApp in the operator queue - A customer sending a WhatsApp message to the business number lands in the SalesIQ operator queue alongside web chat. For non template service replies inside Meta’s 24 hour customer service window, and within the current monthly service message allowance set by Meta, SalesIQ carries the conversation without an additional per message Meta charge on the business side. Beyond the allowance, Meta bills the standard recipient country rate. Utility and Marketing templates sent inside the window are billed separately at their own category rates.
• A chatbot in front of operators - The Zobot handles the opening exchanges, qualifies the request, and escalates to a human only when needed. Operators spend less time on repetitive intake.
• Outbound WhatsApp from the same console - Operators can send proactive template messages to known phone numbers, and marketing can run broadcasts against a filtered audience of SalesIQ Users who have previously interacted, all from the SalesIQ Outbound module. The Import Contacts beta extends broadcasts to CRM contacts who have not interacted yet, with support enablement required. Summer ’26 added operator level initiation by phone number without a prior contact record.
• CRM transcript push - When a conversation closes, and both the CRM integration and transcript synchronization are enabled, the transcript, the attendant and visit context, operator notes, and an automatic activity note can push to Zoho CRM against the matched Lead or Contact. The WhatsApp conversation then appears on that CRM record alongside other channel activity for the contact.

Fig 1 – How a SalesIQ WhatsApp integration connects a business number to the operator console and the CRM record

The practical effect is that WhatsApp becomes a measurable channel. Inbound traffic reports alongside web chat. Outbound campaigns report Delivered, Seen, and Reply metrics, and after Summer ’26 also clicks, response rate, and a response volume heat map through Reports 2.0, available on eligible Professional and Enterprise plans. That measurability is the operational difference between the free WhatsApp Business mobile app and a SalesIQ WhatsApp integration.

How Pieces From SalesIQ and WhatsApp Integrate Together

A SalesIQ WhatsApp integration has four moving parts on the Zoho side plus Meta on the outside.

The WhatsApp Business number sits in Meta’s system through a WhatsApp Business Account (WABA). SalesIQ connects to that WABA through Meta Business Manager during onboarding, and one WABA number can now sit across multiple Zoho products at the same time, shipped in the Summer ’26 release.

SalesIQ owns the inbound side. Routing rules place incoming messages in operator groups. The Zobot runs the automated opening of each conversation. A pre chat form and Visitor Fields card capture identity before or during the operator handoff.

Templates and outbound run through Meta’s template approval surface. SalesIQ supports Marketing and Utility categories today, and Summer ’26 shipped multilingual template support in 70+ languages along with a Channel Message card inside the codeless Zobot builder for triggering templates from a flow.

CRM push and the Desk ticket surface sit beside SalesIQ. A SalesIQ to CRM mapping handles field mapping, Lead and Contact creation, and transcript attachment. A SalesIQ to Desk link, where configured, can turn a missed WhatsApp chat into a Desk ticket.

Zoho’s SalesIQ WhatsApp setup guide handles the step by step install for the WhatsApp channel itself. CRM mapping, Desk integration, and Zobot design each live in separate Zoho documentation, so readers starting from scratch should begin with the channel guide and reach for the others as the build moves across parts. Between those parts sit the operational edges the channel guide does not foreground. That is what the next section covers.

What Zoho’s Official SalesIQ and WhatsApp Integration Guide Does Not Foreground

Eleven field findings from Clixlogix engagements. Each one is a thing the standard SalesIQ WhatsApp setup guide treats lightly or not at all. Status labels mark what has shipped and what has not.

Zoho and Meta’s Pricing for SalesIQ and WhatsApp Integration

A SalesIQ WhatsApp message carries Meta’s recipient country rate plus a 3 percent credit purchase fee that Zoho charges when the business tops up the credit balance. Meta’s rate flows through the Zoho credit mechanism; the 3 percent fee is the only separate Zoho cost.

Meta charges per message, with the rate set by the recipient country and the message category of Marketing, Utility, or Authentication. From 1 October 2026, the first 1,000 service messages per WhatsApp Business phone number each month are free. Additional service messages are charged at the applicable recipient country rate. The Meta pricing updates page carries the current rate behavior, and teams should verify the live figures before any customer facing cost example.

Outside the 24 hour customer service window, the business can send only an approved template. Sending that template does not reopen free form messaging. The customer must reply for a new 24 hour service window to open.

SalesIQ credits sit on top at 2 US dollars each with a 3 percent processing fee. Each chargeable WhatsApp message deducts credits based on the Meta rate for the recipient country. A balance that cannot cover a chargeable message prevents that message from being sent, which turns a credit shortfall into a silent broadcast failure. Discrepancies tend to appear after a tier change or a new country enters the audience.

Tip - Reconcile SalesIQ credit consumption against the Meta pricing table monthly. Clixlogix engagements run this on a fixed monthly cadence.

Prelaunch Checklist For Your WhatsApp and SalesIQ Integration

Eight tests. Each one is cheap to run and expensive to skip. Each test names what breaks if it fails on the live build, so a reviewer can tell whether to launch or hold.

1. Hidden message risk - This test confirms that mandatory pre chat form fields do not block an inbound WhatsApp message from reaching the operator queue. Send a WhatsApp message from a fresh phone number without answering any mandatory field the Zobot presents. The message should still appear in the operator queue or an unassigned view. If it does not, operators will miss WhatsApp traffic the moment the pre chat form carries a required field, and the business will not know messages were lost until a customer calls to complain.
2. Phone number matching to CRM - This test confirms the SalesIQ to CRM mapping finds the correct existing Lead or Contact on inbound WhatsApp messages. The phone number value SalesIQ exposes to the mapping varies by flow. It can arrive as a formatted international string with a plus sign and country code, as digits only without a plus sign, or inside a session field whose presence depends on the Zobot path. Inspect the actual value in the current build first, confirm its format, then normalize to the international E.164 format of plus sign, country code, and the full number before matching. CRM records often store the same number in a local format, or with spaces, or without the country code, so the normalization step runs on both sides. Run the test against duplicate records, converted Leads, and the ownership rules in play. A mismatched format can cause failed matches or duplicate records when automatic record creation is enabled, which breaks attribution and the salesperson’s view of history.
3. Name Card prompt in every supported language - This test confirms the Zobot accepts a typed response at the Name Card step across every language the business supports. Type a name in each language, without tapping a button. The typed name should save without re-prompting or looping. Older bot configurations that forced a button tap should be simplified to match the current behavior, since the forced tap now adds friction without serving a purpose.
4. Location card for pins and typed addresses - This test confirms the Zobot handles both a WhatsApp pin attachment and a typed address. Send a pin from WhatsApp first, then send a plain typed address from a second test. The pin should proceed through the Location card without issue. The typed address should route through a Visitor Fields free text card without re-prompting on the Location card. Without this split, a user who types an address, with no pin, stalls inside the bot.
5. Single choice list cap and pagination - This test confirms long dynamic lists stay inside the single choice interaction and never degrade into a text wall. Run menus at 10 items, 11 items, and several dozen items. The 10 item cap still holds, so lists over 10 need the paginated approach. The community practitioner workaround Clixlogix has tested paginates CRM derived lists into 8 choices plus Next and Previous controls, generated through a Deluge plug, so the user traverses the full list without losing the single choice flow. The approach is community tested and carries no Zoho support, so plan to maintain it.
6. Desk timer precedence over the WhatsApp channel timer - This test confirms which setting actually controls when missed WhatsApp chats close. Configure the Zoho Desk missed chat behavior and the SalesIQ WhatsApp channel timer to visibly different values, for example 60 seconds and 10 minutes. Send a test message and leave it unanswered. Record which timer closed the conversation. Align both settings before launch so closure behavior is predictable in production and reports match the configured policy.
7. Timeout audit for closed WhatsApp chats - This test confirms reporting can tell agent closed and timeout closed WhatsApp conversations apart. Close one test chat by agent action and another by timeout. Open the reporting view and confirm each closure type is distinguishable through the SalesIQ Data Workflow tag described in the auto closed chats finding above. Without the tag, SLA reporting treats both closures as the same event and CRM follow up logic that depends on the closure reason runs on the wrong set of conversations.
8. Shared number portal eligibility and cross app behavior - This test confirms what the shared WhatsApp number actually gives the business. Confirm whether the portal is an eligible connected bundle such as Zoho One or CRM Plus, where Zoho documents unified conversation context, or a standalone portal or one upgraded from standalone, where each app maintains its own channels. Reply from each app and record transcript visibility, Zobot activation, and closure behavior for the portal type the business actually operates. For eligible bundles, extend the test to three further checks that Zoho’s shared number guide documents: masked cross service replies, so the recipient sees one unified sender identity across apps; agent pickup warnings and conversation locking, so two services do not pick up the same conversation at once; and parent service precedence, so the correct service wins when both try to act on the same thread. Launch assumptions built on the wrong portal type break reporting and handoff workflows on day one.

Talk to Clixlogix