HubSpot and Zoho both push WhatsApp through official API partners. Smaller teams often bridge CRM data to a phone running WhatsApp Business on a real UK +44 eSIM. The number must survive Meta checks, which rules out 5sim-style virtual lines.
Integration patterns
| Pattern | Tools | Number needed |
|---|---|---|
| Native API connector | HubSpot + BSP | Verified any type |
| Webhook to human send | Zoho Flow + phone | Real mobile +44 |
| Zapier draft message | CRM event triggers SMS app | Real mobile +44 |
Why real eSIM for the phone path
When a rep taps send from a notification, WhatsApp sees a normal mobile session. BuyUKeSIM lines are prepaid UK carrier stock ($25, crypto, no KYC). Warm each line 2 weeks before CRM-driven volume hits about 200 messages per day. Guide: warm-up.
Sample Zoho workflow
- Deal stage moves to "Proposal sent"
- Zoho sends Slack alert with contact name and template snippet
- Rep opens WhatsApp Business on UK line, personalizes, sends
- Log activity back in Zoho manually or via note automation
Register the line first: WhatsApp UK eSIM setup. Never use VOIP: virtual failures.
Disclaimer
CRM automation must respect opt-in consent stored in your CRM. Bulk unsolicited WhatsApp violates ToS regardless of tooling.
FAQ
Does HubSpot sync chat history natively without API?
No. You need Cloud API or manual logging for full sync.
One UK number for whole sales team?
WhatsApp Business supports linked devices but one primary phone. Scale with multiple eSIM lines rotated by territory.
