Tidio WhatsApp Integration
WhatsApp is the dominant messaging platform in large parts of the world -- Latin America, Europe, Southeast Asia, Africa, India. If your customers are in those markets, WhatsApp support is not optional, it is expected. Tidio's WhatsApp integration routes WhatsApp Business conversations into the shared inbox alongside chat, email, and social channels.
The integration works through the WhatsApp Business Platform (formerly WhatsApp Business API), which means there are setup requirements and costs beyond what Tidio charges. This is the most complex of Tidio's channel integrations, and it is worth understanding what you are getting into.
Setup requirements
Unlike connecting Gmail or Messenger, WhatsApp integration involves multiple steps and external dependencies:
- WhatsApp Business account. You need a Meta Business account with a WhatsApp Business profile. This is separate from the standard WhatsApp app on your phone.
- Meta Business verification. Meta requires verification of your business entity before granting API access. This involves submitting business documents and can take anywhere from a few days to several weeks. Many users report this being the slowest part of the process.
- Phone number. You need a dedicated phone number for WhatsApp Business that is not already registered with the regular WhatsApp app. You cannot use the same number for personal WhatsApp and business API simultaneously.
- Connect in Tidio. Once your WhatsApp Business account is verified, go to Settings > Channels > WhatsApp in Tidio and follow the connection flow.
The total setup time ranges from 30 minutes (if you already have a verified Meta Business account) to several weeks (if you are starting from scratch and Meta verification takes time). Reviewers consistently call out the verification wait as frustrating.
How conversations work
WhatsApp Business conversations operate differently from web chat, and these differences matter:
The 24-hour response window. When a customer messages you on WhatsApp, you have 24 hours to respond with a "session message" (free-form text). After 24 hours, the window closes and you can only reach the customer using a pre-approved template message, which incurs a per-message cost. This is a WhatsApp platform rule, not a Tidio limitation.
Template messages. To message customers outside the 24-hour window (or to initiate conversations), you must use message templates that have been pre-submitted to and approved by Meta. Templates support variables (customer name, order number) but must follow Meta's content guidelines. Template review typically takes 24-48 hours.
Conversation flow in Tidio. Within the 24-hour window, agents reply to WhatsApp messages directly from the Tidio inbox, same as any other channel. The experience is seamless -- type a reply, hit send, customer receives it on WhatsApp. Outside the window, the agent is prompted to select an approved template instead.
What you can do
| Feature | Details |
|---|---|
| Reply to WhatsApp messages | Full two-way messaging within the 24-hour window |
| Send template messages | Pre-approved templates for outbound messaging |
| Assign conversations | Standard Tidio assignment and routing |
| Tag and manage contacts | WhatsApp contacts appear in Tidio's CRM |
| Send media | Images, documents, and files (within WhatsApp's size limits) |
| Chatbot Flows | Basic Flows work on WhatsApp conversations |
| Lyro AI | Available on supported plans for WhatsApp conversations |
Limitations
WhatsApp is a more constrained channel than web chat, and several limitations are worth understanding upfront:
- WhatsApp's own pricing. Beyond your Tidio subscription, WhatsApp Business Platform charges per conversation. Rates vary by country and conversation category (marketing, utility, service, authentication). Service conversations initiated by customers are currently free for the first 1,000 per month, but business-initiated conversations are not. These costs add up for high-volume operations.
- Meta verification delays. Multiple reviewers flag this as their biggest frustration. The verification process is opaque, and when it stalls, Tidio cannot help -- it is entirely on Meta's side.
- Plan gating. WhatsApp integration is not available on all Tidio plans. Check current plan requirements on Tidio's pricing page or see our Pricing overview.
- Limited Flow features. While basic chatbot Flows work on WhatsApp, rich interactive elements (carousels, complex button layouts) are limited by WhatsApp's message format constraints. Simple text and quick-reply buttons work; complex visual Flows do not.
- No group messaging. Tidio's WhatsApp integration handles one-on-one business-to-customer conversations. WhatsApp group chats are not supported.
- Number portability concerns. Moving your WhatsApp Business number between providers (if you switch from Tidio to another platform later) involves a migration process that can cause downtime.
Who benefits
The WhatsApp integration makes the most sense for:
- Businesses in WhatsApp-heavy markets. If you serve customers in Latin America, Europe (especially Southern and Eastern Europe), India, or Southeast Asia, WhatsApp is often the preferred -- sometimes the only -- way customers want to communicate. In these markets, not having WhatsApp support is a meaningful disadvantage.
- Ecommerce with international customers. Stores shipping globally often find that WhatsApp is the default communication channel for a significant portion of their customer base, particularly outside the US.
- Teams already using Tidio who want to avoid managing WhatsApp Business separately. Consolidating into one inbox is the core value.
For US-focused businesses where WhatsApp usage is lower, the complexity and cost of the WhatsApp integration may not justify the investment. Messenger and Instagram typically reach more US customers.
Review sentiment
WhatsApp integration feedback across G2, Capterra, and Trustpilot:
- Positive: Users in WhatsApp-heavy markets describe it as essential. "Finally can manage WhatsApp in the same place as chat" is a common sentiment.
- Positive: Once set up, the day-to-day experience is smooth. Agents report no issues with response speed or message delivery.
- Negative: Setup complaints dominate. Meta verification, number requirements, and the multi-step process generate the most frustration.
- Negative: WhatsApp's per-conversation costs catch some users off guard, especially those on Tidio's lower tiers who did not budget for the additional channel expense.
- Mixed: Some users wish Tidio offered more WhatsApp-specific automation (quick reply templates in the Flow builder, WhatsApp catalog integration) rather than treating it as another generic messaging channel.
WhatsApp vs other Tidio channels
| Aspect | Messenger | Web chat | ||
|---|---|---|---|---|
| Setup complexity | High (Meta verification) | Low (Facebook page admin) | None (built-in) | Low (OAuth) |
| Additional costs | Per-conversation fees | None | None | None |
| Response time constraint | 24-hour window | 24-hour window | None | None |
| Proactive outreach | Templates only | Limited | Yes (via Flows) | No (reply only) |
| Rich media | Images, docs | Images, buttons | Full widget features | Standard email |
| Global relevance | Very high outside US | High (Facebook-dependent) | Universal | Universal |
Bottom line
The WhatsApp integration is essential for businesses serving markets where WhatsApp is dominant, and it works well once you get past the setup hurdles. The day-to-day experience of managing WhatsApp conversations in Tidio's shared inbox is smooth, and basic automation through Flows adds value.
The honest challenge is everything that surrounds the core messaging: Meta verification delays, WhatsApp's per-conversation pricing, plan gating on Tidio's side, and the 24-hour response window that constrains your outreach. None of these are Tidio's fault specifically -- they are WhatsApp Business Platform realities -- but they make this integration meaningfully more complex and expensive than connecting Messenger or Gmail.
For other channel integrations, see Messenger and Instagram. For the full integration list, see Integrations.