Moving off Kaleyra — 3 recurring reasons
Kaleyra (now Tata Communications) is a strong SMS + voice CPaaS with a WhatsApp Business API on top. Teams that adopted it for SMS often hit three limits once they pivot to WhatsApp as the primary channel.
WhatsApp is a bolted-on channel, not the core product
Kaleyra was built around SMS and voice. WhatsApp Business API is solid as a send-channel but shared team inbox, broadcast throttling, CTWA attribution, Shopify/Odoo native flows, and AI-drafted replies are either add-ons or not there at all.
API-first, not platform-first
You get a strong HTTP API and decent developer docs. You don't get a no-code template library, visual flow builder, drag-and-drop broadcast manager, or shared inbox with assignment rules out of the box — you'd need to build those on top or contract a partner.
Pricing is enterprise / quote-led
Kaleyra's WhatsApp rates aren't publicly listed. Commercial teams comparing vendors on a spreadsheet end up frustrated by back-and-forth with sales just to get a comparable number.
If any of these sound like your team, the next section is the honest side-by-side.
Kaleyra vs Go4whatsup — side-by-side
Fifteen capability rows that teams evaluate us on during Kaleyra migration calls. We've tried to keep this honest — if Kaleyra genuinely wins on a row, we say so in the copy.
| Capability | Kaleyra | Go4whatsup |
|---|---|---|
| Positioning | SMS + voice CPaaS, WhatsApp add-on | AI WhatsApp platform, WhatsApp-first |
| Product shape | API-first | No-code platform + API |
| Pricing transparency | Quote-led | Published AED/INR tiers |
| Meta conversation markup | Typically platform markup | Pass-through, Meta-based |
| Visual flow builder | No / limited | Yes |
| Shared team inbox | No (API only) | Yes — with assignment rules |
| Broadcast manager (no-code) | API-driven | Full — throttling, retries, AI copy |
| Template library | API-manageable | GUI library + AI copy generator |
| Shopify / Odoo / Zoho native | Partner / custom | Native |
| AI auto-reply | Via add-ons / partners | Yes — 4 AI capabilities included |
| Auto-translation | Via add-ons / partners | Yes — 20+ languages included |
| CTWA attribution | Custom build | Native, UTM-aware |
| Time to first live campaign | Dev-cycle dependent | Hours, no-code |
| Green-tick assistance | Enterprise CSM | Free onboarding, MBP team |
| Meta Business Partner | Yes | Yes (verified) |
The 7-day migration plan
This is the literal sequence our onboarding squad runs on a Meta Business Partner track. Day numbers flex for larger enterprise setups, but the order is consistent.
Audit your current setup
Export what's running today: active WhatsApp number(s), template list, contact segments, CRM integrations, automation flows, agents on the shared inbox. We'll run this with you on a free 30-minute discovery call.
Prepare your Meta Business Manager for transfer
Confirm you own the Meta Business Manager (not a reseller). Verify business documents are current. Remove stale permissions. Our Meta Business Partner team handles the escalations if Meta flags anything.
Initiate the WABA transfer + re-submit templates
Day 1–2. We submit the WABA transfer request to Meta. Meanwhile, we copy your existing templates (text, media, buttons, category) and resubmit under the transferred WABA. Standard templates are re-approved in 2–12 hours; marketing promos sometimes need a rewrite.
Import contacts and rebuild segments
Day 3. Export your contact list as CSV (phone, name, tags, consent status, lifecycle stage, custom fields). Import into Go4whatsup. Rebuild segments and lists 1:1 with your previous setup.
Rebuild flows + re-wire CRM integrations
Day 3–5. Your top 5–10 flows (support entry, order status, lead qualification, abandoned-cart, post-purchase) get rebuilt by our onboarding team in Go4whatsup's flow builder. Shopify/Odoo/Zoho/HubSpot/Salesforce integrations wired during the same window.
Parallel-week test broadcast
Day 6. Run a test campaign on the new Go4whatsup stack to a 500-person segment. Monitor delivery, read, reply, agent CSAT and cost-per-conversation. Fix any flow gaps before full cutover.
Cutover + monitoring
Day 7. Point production traffic fully at Go4whatsup. Our team stays online for the next 72 hours to catch edge cases. Post-cutover review at day 14 confirms you're operating cleanly.
Pre-flight checklist
Tick these off before the first onboarding call and we'll cut 1–2 days off the timeline. If you're missing anything — not a blocker; our team fills the gaps.
Pre-flight checklist
- Meta Business Manager is owned by your company (not a reseller)
- Business verification documents (GST / trade license / utility bill) are current in Meta Business Manager
- You have admin access to the current WhatsApp Business Account (WABA)
- You've exported your contact list as CSV (phone, name, tags, consent status, lifecycle stage, custom fields)
- You have an inventory of currently-approved WhatsApp templates (text, media, button structure, category)
- You have a list of active automation flows and which integrations/CRMs they touch
- Your Shopify/Odoo/Zoho/HubSpot/Salesforce CRM admins are looped in (we'll need 1–2 integration calls)
- You've identified a pilot-segment (500–1,000 contacts) for the parallel-week test
- You've communicated the cutover date to your support team + key stakeholders
- You've agreed a 72-hour post-cutover monitoring window with our onboarding squad
How we hit zero-downtime cutover
The classic fear with a WhatsApp platform switch is a dark number — hours or days where campaigns pause, agents can't reply, and conversations spill to email. Here's how we avoid that.
- Meta-side WABA transfer is instant on Meta's side. The number keeps sending on Kaleyra right up to the transfer moment, and resumes on Go4whatsup within minutes of the transfer completing.
- Templates are re-submitted in parallel under the transferred WABA while the old platform is still live. By cutover, the new library is already approved.
- Contacts import happens before cutover, not after — so agents log into Go4whatsup on day 7 and already see the segments they're used to.
- Flows are rebuilt in staging, tested against a pilot segment, and only enabled on cutover day once the pilot numbers match or beat Kaleyra.
- 72-hour onboarding hand-holding means the same team that ran your migration is on WhatsApp for the first 3 days post-cutover.
When to run parallel vs immediate cutover
Two patterns, both work.
Immediate cutover (most teams). Day 7 flip-the-switch. Works for teams under 100k active contacts, under 20 active templates, fewer than 5 complex flows, and one primary WhatsApp number. Fastest path to Go4whatsup's cheaper conversation pricing.
Parallel operation (large teams + mid-contract teams). Provision a secondary WhatsApp number on Go4whatsup, mirror 2–3 highest-volume flows, route a pilot segment there for 2–3 weeks, measure CSAT / resolution / cost-per-conversation side-by-side, then cut over once you're confident. Best for Kaleyra accounts mid-contract where a price-match on the overlap is preferred over breaking the contract.
Frequently asked questions
We have a lot of custom code on Kaleyra's API — does that port to Go4whatsup?
Yes, in most cases. Go4whatsup exposes a REST API and webhook system that covers message-send, template management, contact CRUD, campaign trigger, webhook-in, and conversation state. Teams migrating from Kaleyra's API usually swap endpoints in a day and keep their webhook logic unchanged. We run a free API-mapping session during onboarding.
How long does a Kaleyra → Go4whatsup migration take?
6–10 working days, depending on API depth. Day 1–2: Meta WABA transfer + templates resubmitted. Day 3: API key swap and webhook redirect. Day 4–5: contact + segment migration, flows rebuilt (or API-driven flows repointed). Day 6: parallel-week test. Day 7–10: cutover and monitoring. Teams with heavy Kaleyra SMS usage often keep Kaleyra for SMS and run Go4whatsup for WhatsApp — a clean split.
Can we keep Kaleyra for SMS and use Go4whatsup only for WhatsApp?
Yes — common pattern. Kaleyra remains your SMS gateway; Go4whatsup becomes your WhatsApp stack with its own WABA. Most teams route critical OTPs/transactional through whichever channel is cheaper per market. Our onboarding team helps you design the routing logic.
Will our WhatsApp number and green tick move?
Yes. The WABA is on your Meta Business Manager, independent of Kaleyra. We initiate a Meta-side transfer; number, green tick, display name and verified business profile all move to Go4whatsup in 24–48 hours. Current number keeps sending through the window.
How does Go4whatsup pricing compare on WhatsApp specifically?
Kaleyra publishes INR-only on request. Our published AED/INR tiers are typically 30–55% lower per-conversation once you factor in platform markup. Teams tell us the bigger cost saving is actually developer time — the no-code flow builder, template library, and broadcast manager replace sprints of internal build.
Does Go4whatsup handle OTP / authentication templates like Kaleyra?
Yes, natively. Authentication templates route on Meta's auth-category pricing (cheapest conversation category). We support the OTP auto-fill button format, region-specific templates, and per-template analytics. Zero markup on auth category — you pay Meta's rate.
Are you a Meta Business Partner like Kaleyra?
Yes, verified. You can check the Meta Partner Directory directly. BSP status means we handle green-tick applications, template escalations, and Meta account reviews on your behalf — included in onboarding, not a paid add-on.
What about compliance — GDPR, DPDP, Tata-style enterprise audits?
DPA published, sub-processor list public, GDPR-aligned, DPDP-aware, UAE PDPL-aware, no training on customer messages. SOC 2 Type II and ISO 27001 certification roadmap on our Security page. Large-enterprise procurement teams can book a 30-minute security review before committing.