TL;DR
- Rasayel is worth evaluating for a WhatsApp-centred sales team using HubSpot or Salesforce; its listed Grow plan requires at least ten team members.
- respond.io is a candidate for teams managing WhatsApp alongside other messaging channels; its HubSpot integration requires Growth or above.
- Wati offers a WhatsApp-focused inbox and CRM integrations. Confirm the exact HubSpot and Wati editions because its published guidance differs by workflow.
- Trengo is a shared-inbox option for teams managing conversations across channels. Verify the exact CRM connector, user capacity and conversation allowance.
- Test what happens to an incoming message, contact match, sales owner and activity record when a sync fails. A connection badge alone does not prove a usable sales process.
What does a useful WhatsApp CRM integration need to do?
A prospect messages a sales number after reading a product page. The team needs to identify the person, find the right account, give the conversation to an available rep and preserve enough context for the next interaction. A WhatsApp inbox that merely displays the message solves only the first part.
Map five events before comparing products: message received, contact matched or created, owner assigned, qualification captured and CRM activity written. For each, decide which system is authoritative. For example, if the CRM owns account assignment, the messaging inbox should not silently overwrite it with a round-robin assignment. Decide what happens when two CRM contacts have the same phone number or the CRM is temporarily unavailable.
These options provide sales or shared-inbox workflows around WhatsApp and CRM connections. They are not a comparison of developer APIs alone, and we have not run a comparative implementation test. Verify supported CRMs, plan gates and the direction of each sync against your own configuration. Our CRM activity sync guide addresses the wider problem of preserving activity across channels.
Four integrations at a glance
| Option | Starting fit | CRM and operations question | Cost boundary |
|---|---|---|---|
| Rasayel | Sales teams centred on WhatsApp | Which HubSpot or Salesforce objects, owners and activities sync? | Grow lists a ten-member minimum; Meta fees are separate |
| respond.io | Conversations across several messaging channels | Does the qualifying plan support the CRM and automation required? | Platform plan, capacity and applicable channel charges |
| Wati | WhatsApp-focused teams using a shared inbox | Which HubSpot edition and Wati plan support the desired workflow? | Subscription, agents, messaging and optional add-ons |
| Trengo | A shared inbox across sales and service | Is the specific CRM connector native, partner-built or custom? | Users, conversations, automations and channel fees |
A native integration may still have restrictions on custom fields, activities or direction. Ask for a field-level mapping and run the same handoff test before comparing a subscription price.
| Item to map | Suggested owner for the pilot | Question to resolve before go-live |
|---|---|---|
| Contact and account identity | CRM | How are shared numbers and duplicate contacts resolved? |
| Account or deal owner | CRM | Does the inbox read ownership, overwrite it or keep a separate assignee? |
| Conversation assignment and status | Inbox | Does a transfer preserve the thread and notify the next rep? |
| Messages and activity | Inbox as source; CRM receives agreed record | Is the CRM entry a transcript, summary or link, and what can be exported? |
| Opt-in and opt-out evidence | The organisation's designated policy record | Which system records changes and how are they applied across channels? |
| Sync attempt and final receipt | Integration owner | Can an operator find and reconcile one failed or uncertain write? |
These are suggested responsibilities, not universal vendor defaults. Mark each cell as native, configured, custom-built or unsupported for the proposed integration, and name an owner for every unsupported handoff.
1. Rasayel: for WhatsApp-centred sales
Rasayel positions its product around WhatsApp sales. Its pricing page lists HubSpot and Salesforce integrations on Grow, with a minimum of ten team members and a displayed rate of $40 per user per month. The five-member minimum belongs to the lower Start plan, which lists different integrations. At the displayed Grow rate, ten users would be $400 per month before applicable Meta messaging fees and other charges. The same page separately lists the Salesforce integration as a $300 monthly add-on: if that applies to this configuration, the ten-user Salesforce subtotal would be $700 per month before messaging and other charges. Confirm the add-on, billing term and current checkout in writing.
For an inbound sales team, the central question is whether a rep can see the right CRM context while answering, then leave an activity that another rep can understand. Ask Rasayel to demonstrate matching a new phone number to an existing contact, associating the conversation with the right company or deal, and changing the owner without losing the thread.
This is a focused candidate if WhatsApp is central to the team's sales motion. It may be less suitable if the primary requirement is a broad service desk across many channels. Verify how history, attachments and opt-in evidence can be exported if the business changes provider or number.
2. respond.io: for multichannel conversations
respond.io brings messaging channels into a shared conversation workflow and offers CRM connections. Its HubSpot integration documentation states that HubSpot is available on Growth and above. That gate is more useful to a buyer than a generic “integrates with HubSpot” claim.
Test the specific objects and properties your team relies on. Does a new WhatsApp contact become a CRM contact automatically, or does it require a workflow? Is the conversation stored in full, summarised as an activity, or linked back to the inbox? What happens when a CRM owner changes after a conversation is assigned? Answers can differ by integration and configuration.
For the documented HubSpot-to-respond.io contact sync, respond.io says matching uses email or phone and, if multiple respond.io contacts match, it selects the oldest. That is a specific sync-direction rule, not proof of how every inbound WhatsApp-to-CRM match behaves. Include duplicate identities in the pilot and agree how an incorrect link is detected and corrected.
The same documentation says HubSpot is the source of truth for mapped fields in that direction: clearing a mapped value in HubSpot clears it in respond.io too. Before enabling the sync, identify fields where a blank value should trigger review rather than propagate, and check what controls are available in the selected configuration. The reverse flow must be assessed separately.
It is a strong candidate when WhatsApp is one part of a broader inbound messaging operation. If a team only needs a simple one-to-one conversation inside its existing CRM, compare the qualifying plan and implementation effort with the CRM's own supported channel options.
3. Wati: for WhatsApp-focused teams
Wati describes a WhatsApp inbox and HubSpot connection. Its product page says the integration is available on Wati Pro and Business and distinguishes HubSpot Starter, Professional and Enterprise access from advanced workflow actions, which require HubSpot Professional or Enterprise. Its help-centre setup article likewise specifies a Professional-or-higher HubSpot subscription for the automated workflow it describes. Confirm the exact Wati and HubSpot editions for your connector and automation; basic connection availability does not establish that every action is included.
Give the provider your CRM edition, required properties and desired automation and ask for a written demonstration. Inspect whether incoming messages and outgoing replies are logged, whether contact creation is deduplicated and what the rep sees when a sync fails. Ask which charges apply for users, automation, messaging and optional AI features.
Wati is worth evaluating for an organisation that wants a WhatsApp-led workflow. A buyer needing extensive CRM customisation should confirm the exact scope and build responsibility before replacing a working process.
4. Trengo: for a shared multichannel inbox
Trengo offers a shared-inbox product across channels. Its published Base plan displays three included users, a maximum of five and 1,200 conversations per year in the visible pricing configuration. A ten-rep, high-volume operation therefore needs a different plan or configuration; ask for the qualifying quote in the correct currency and billing term.
Trengo is relevant when WhatsApp sales sits alongside support or other messaging channels and the business wants a common handling process. The CRM connection is still a separate evaluation: request the name and maintainer of the connector, supported CRM edition, field mapping, activity format and failure handling. A partner integration or custom automation may have a different support boundary from a native feature.
Check whether teams can separate sales and support queues, limit access to sensitive conversations and transfer an open thread without losing ownership. If the only requirement is a small WhatsApp sales team, the extra channels may not justify the broader platform. Compare the actual plan and the number of users who need access, rather than assuming the entry price covers all ten reps.
What will ten reps and 5,000 conversations cost?
Start with ten reps and 5,000 opted-in inbound conversations per month. These are planning inputs, not observed performance. Clarify how each platform counts an active contact, conversation or billable event: 5,000 conversations is not necessarily 5,000 unique contacts, 5,000 messages or 5,000 billable Meta templates.
A synthetic budget might allocate $500 per month to the inbox and eligible CRM connection, $150 to applicable message and provider fees, and four hours of administration at $50 per hour. The total is $850 per month, or $0.17 per conversation at 5,000 conversations. Add the CRM subscription, implementation, tax and any overages if they are incremental. These numbers illustrate a calculation; they are not a quote or a statement of any provider's charges.
For transition, if the team also spends 20 hours mapping fields, training reps and testing at the same assumed $50 per hour, add $1,000 once. The illustrative first month becomes $1,850, before any overlap with the old inbox or additional usage. Ask every candidate for the same ten-user, 5,000-conversation quote, including the plan that actually enables the desired CRM integration and workflow.
Separate WhatsApp charges from the platform subscription. Twilio's WhatsApp pricing explanation distinguishes its own per-message fee from Meta's applicable template fees and describes the customer-service window. Other providers may package or pass through fees differently. Template category, recipient country, the message timing and provider contract can change the bill; do not multiply a single assumed price by all conversations and call it the Meta charge.
In the synthetic budget, the $150 message allocation is $0.03 per conversation on average across 5,000 conversations; it is not a price per message or a published Meta tariff. To replace the assumption, estimate inbound and outbound message counts separately, group chargeable templates by destination and category, then add the chosen provider's fees. The number of messages in a conversation can vary, so the same 5,000 conversations need not produce the same bill.
Budget for quality as well as volume. If one option costs $200 less but requires ten hours a month of manual CRM repair at $50 per hour, the apparent saving becomes a $300 additional operating cost. That is a decision threshold to test, not a claim that any listed integration causes that workload.
How do you test the inbound handoff?
Use the same synthetic conversation with every shortlisted provider. The fixture below is a proposed evaluation, not a test we have performed.
- A prospect with a recorded opt-in sends a WhatsApp message. Record the source, time, phone number and consent evidence available to the team.
- The number matches two CRM contacts. The system should identify the ambiguity rather than silently merge or overwrite records. Agree which person can resolve it.
- A rep qualifies the prospect and assigns the conversation to a colleague. Confirm that the new owner sees the prior thread and the agreed CRM context.
- Simulate an unavailable CRM when the rep records the outcome. The inbox should make the failure visible, retain the action and offer a documented retry or recovery route; verify the behaviour rather than assuming it exists.
- Restore the CRM and check that the activity appears once on the correct contact and, where required, the correct deal. A retry that creates duplicates is a different failure from losing the activity.
- Test a follow-up inside and outside the applicable service window. Confirm the required template and opt-in policy with your provider; preserve the opt-out and stop further messages where required.
Before the test, put the expected field ownership in writing. The CRM might own account and deal, while the inbox owns conversation status and the currently assigned agent. Decide whether phone-number changes flow one way or both ways, what happens to blank values, and whether a message can attach to more than one deal. Ask each vendor to mark every row as native, configurable, custom-built or unsupported. Include timestamps and an integration event ID so the team can trace a message from inbox to CRM without relying on a rep remembering the conversation.
For example, a fictional prospect, Nia, messages from a number associated with two CRM contacts. The inbox assigns the conversation to Sam, but the CRM lookup is ambiguous, so no contact or deal activity is written yet. Sam confirms the correct contact and transfers the thread to Alex. When Alex records the qualification, the CRM is unavailable: the outcome remains marked pending rather than reported as saved. After the connection returns, the operator reconciles the pending event and verifies one activity on the approved contact. The contact match, inbox assignee and CRM account owner are three separate fields; transferring the conversation need not change the account owner.
Record the input event ID, match decision, assignee changes, intended CRM record ID, each sync attempt and the final CRM activity ID. If the provider cannot expose a particular identifier or retry state, document the manual recovery route and its owner. These are expected outcomes for the fixture, not claims that any named product already behaves this way.
Then inspect the audit trail. Who can see the phone number and message content? How are attachments handled? What can be exported if the relationship ends, and can access be revoked for one rep? Decide whether the CRM stores a transcript, a summary or a link to the source. The GTM engineering playbook provides a framework for assigning ownership of those data and recovery decisions.
Which integration should you shortlist?
Start with Rasayel when WhatsApp is the centre of the sales workflow, respond.io for a multi-channel operation with a qualifying CRM plan, Wati for a WhatsApp-focused team that has confirmed its edition requirements, and Trengo for a broader shared inbox. The winner is the option that preserves contact identity, owner and conversation history for your actual team at a workable cost.
If the team is also consolidating email and LinkedIn conversations, see our unified inbox comparison. A team building its own communication layer should separately evaluate the Unipile alternatives guide, which addresses developer infrastructure rather than only the sales inbox.
FAQ
Does WhatsApp need a separate CRM integration?
Not always. Some CRMs offer their own WhatsApp channel, subject to their product and plan requirements. A separate inbox may be useful for additional routing or channels, but compare the exact capabilities and costs with the CRM's supported option first.
Are WhatsApp conversations free inside a CRM subscription?
Do not assume that they are. The CRM or inbox subscription, channel-provider charges and applicable Meta template fees can be separate. Pricing depends on the provider, destination and message type; ask for a worked quote for your traffic mix.
What happens if the CRM sync fails?
That depends on the integration. Test whether the error is visible, whether the action is queued, how a retry is triggered and whether it can create duplicate records. Assign an owner to repair failures instead of relying on a silent background sync.





