How Freshchat's WhatsApp Business integration really works in 2026 — setup, the full cost stack (seat + add-on + Meta), the feature limits nobody lists on the pricing page, and when a WhatsApp-first BSP is the better fit.
Freshchat is an omnichannel support suite from Freshworks. WhatsApp is one channel inside it — connected via Meta's Cloud API and surfaced inside the agent inbox alongside email, web chat and Messenger. It is not a WhatsApp-first product; WhatsApp inherits the agent-seat pricing model of the whole platform.
You connect a verified Meta Business Manager, embed-sign into Freshchat with the WABA, point a phone number at the WABA, and Freshchat becomes the BSP-of-record. Template submission goes through Freshchat → Meta. Plan 2–5 business days for the first green tick / display name approval. Most delays are Meta-side, not Freshchat-side.
(a) Per-agent seat on Growth/Pro/Enterprise. (b) WhatsApp add-on charge on top of the seat. (c) Meta's per-conversation pricing (Marketing / Utility / Authentication / Service), billed by Meta directly via the WABA. Teams budgeting only the seat price routinely undershoot total cost by 40–60% in month one.
Expect: solid shared inbox, decent canned responses, basic bot flows, Freshworks CRM ties. Expect gaps in: native click-to-WhatsApp ad attribution, deep template manager with variable testing, broadcast scheduler with audience segmentation, and WhatsApp-specific analytics (read-rate by template, opt-out velocity).
You are already on Freshdesk / Freshsales, your team handles WhatsApp as one of many channels (email is still primary), and you do not run WhatsApp marketing campaigns at scale. The unified inbox value outweighs the WhatsApp feature gap.
WhatsApp is your primary revenue channel, you run broadcasts above ~10k contacts/month, you spend on click-to-WhatsApp ads, or your agent count is growing — per-seat economics on Pro/Enterprise compound fast. A flat-fee WhatsApp-first BSP like LandinChat usually wins on both cost and feature depth.
Indicative 2026 numbers. Meta conversation pricing varies by country — figures shown are India.
| Line item | Typical cost |
|---|---|
| Freshchat Growth seat | ≈ $19/agent/mo (annual) |
| Freshchat Pro seat | ≈ $49/agent/mo (annual) |
| WhatsApp add-on | Variable, on top of seat |
| Meta marketing conversation (IN) | ≈ ₹0.78 each |
| Meta utility conversation (IN) | ≈ ₹0.115 each |
| Meta authentication conversation (IN) | ≈ ₹0.115 each |
Compare against a flat-fee model on the LandinChat pricing page — unlimited agents, WhatsApp API included, only Meta conversation fees pass through.
Yes. WhatsApp is a paid add-on on top of the agent seat on Growth, Pro and Enterprise tiers, and Meta's per-conversation fees are billed separately through the WABA.
Freshchat supports outbound template messages, but the broadcast UX is lighter than dedicated WhatsApp BSPs — limited segmentation, no per-template read-rate analytics, no native A/B on template variants.
Freshchat connects through Meta's Cloud API and is recognised as a tech partner. LandinChat is an Official Meta Tech Partner specifically focused on WhatsApp.
Typically 2–5 business days end-to-end: Business Manager verification, WABA creation, embedded signup, display name approval, and first template approvals. Delays are usually Meta-side.
Yes — you re-host the same WABA under LandinChat as the BSP-of-record. Customers see no number change. Plan 5–10 working days end-to-end with a 48-hour parallel run.
