WATI

A WhatsApp Business API platform offering multi-agent support and a no-code chatbot builder for customer communication.

Primary category: communication

About this data

This page reflects public online discussion, collected and scored by automated systems and summarized using AI. It is not a statement of fact, not an audit, and not our own opinion of the product. Automated analysis can be incomplete or wrong, and scores carry the limitations described in our methodology. Companies can respond with their own perspective. See how this is calculated.

Updated June 22, 2026

Overall Pulse Score

Pulse Score

+6 over this period

A 0-100 index summarizing the tone of 11 relevant public mentions gathered from public online communities across 7 weeks in the selected period. It measures online sentiment, not a rating of the product's quality.

Weekly Sentiment Trend

Pulse Score by week over the selected period. Each point is one complete week of mentions.

This week in public discussion

Discussion around WATI over the recent period was largely negative, with commenters repeatedly raising concerns about bugs and reliability across multiple threads. A notification ordering problem and webhook security issues drew particular attention, with one commenter noting that inbound webhook signature verification was absent entirely. Integration gaps also came up, including mentions of a missing WhatsApp Business Platform connection blocking staff workflows. Overall community sentiment remained low and showed little sign of improvement from the prior period.

AI-generated summary of public online discussion during this period. It reflects the tone of that discussion, not facts about the product or our views.

Sentiment mix by week

How the tone of public discussion splits each week.

PositiveMixedNeutralNegative

Most-discussed praise

Good integrations1

Feature requests1

Strong features1

Most-discussed complaints

Bugs6

Reliability6

Missing features1

Lacking integrations1

Security praise1

Themes across the selected period, with mention counts.

Sample public mentions

Showing 5 of 11 analyzed public mentions in this period, with links to the original source. We do not reproduce full threads.

“fix(wati): notificaciones de nueva reserva llegan en orden incorrecto. ## Resumen Al crear una **nueva reserva** (status reservado), las tres notificaciones de WhatsApp (WATI) llegan al cliente en orden incorrecto. El mensaje con la información de la reserva (nueva_reserva_5, "Ho...”

githubMay 22, 2026

“bug(wati): notificación post-recogida (post_reserva) bloqueada por Meta — evaluar cambio de texto. ## Contexto La notificación de WhatsApp **post-recogida** está siendo **bloqueada por Meta**, por lo que no se está entregando a los clientes después de la recogida del vehículo. Pl...”

githubMay 9, 2026

“[Bug]: zeroclaw-channels does not compile with --no-default-features. ### Affected component channel Severity S2 - degraded behavior Current behavior zeroclaw-channels does not compile with default features disabled: The crate gates channel modules in crates/zeroclaw-channels/src...”

githubApr 27, 2026

“[Feature]: Read gateway webhook signing secrets from AppState.config at handler time instead of caching at startup. > Follow-up from the review of #7367 (per-alias webhook routing, #6312), requested by @WareWolf-MoonWall. Suggested label: enhancement (filed by a non-maintainer wh...”

githubJun 9, 2026

“docs(send): outbound list/button reply unblockable for Cloud-API peers — root cause MessageContextInfo strip (#165/#166 lineage close-out). ## Summary The chain #161 → #163 → #165 (StanzaID + Participant + QuotedMessage + RemoteJID populated on ContextInfo) brought the outbound l...”

githubMay 20, 2026

Deeper analysis

Bugs and reliability complaints dominated nearly all recorded discussion with no praise themes surfacing to offset negative sentiment.
Sentiment direction trended downward across the window, ending the most recent period at its lowest tracked score despite brief mid-period recoveries.
Opinion was divided on security, with webhook verification gaps framed as a concern by some commenters but tagged with a security-praise signal by others.
Low mention volume meant individual negative posts had an outsized effect, making the overall tone feel more concentrated and consistently critical than a high-volume product discussion might.

Praise theme	Mentions
Good integrations	1
Feature requests	1
Strong features	1

Complaint theme	Mentions
Bugs	6
Reliability	6
Missing features	1
Lacking integrations	1
Security praise	1

Public discussion of WATI over the recent four-week window was sparse in volume but consistently leaning negative in tone. Commenters concentrated almost entirely on complaint themes, with bugs and reliability each surfacing across multiple mentions, leaving no recorded praise themes to balance the conversation. The overall mood was one of frustration with foundational functionality rather than dissatisfaction with surface-level features.

The score trajectory told a choppy story with a clear downward pull at the edges. An early low point in late March gave way to a brief spike in mid-April, which several observers might read as a momentary lift in sentiment, possibly tied to discussion of new platform capabilities like WhatsApp Coexistence. However that optimism did not hold. Scores retreated through late April and dropped sharply into late May before a modest one-week recovery, only to slide again into the most recent readings, finishing at the lowest point in the entire tracked window. The overall direction over recent weeks was decisively downward.

Bug-related frustration dominated in tone. A representative mention described notifications arriving to end users in the wrong order, a complaint that commenters framed as a concrete reliability failure affecting real customers. Integration gaps also drew pointed commentary, with at least one discussion flagging a missing platform connection as a productivity blocker rated at a significant internal priority tier.

Security drew divided attention. One thread noted that inbound webhook signature verification is opt-in and that WATI reportedly performs no verification at all, a detail that commenters framed as a concern rather than a feature. This stood out as a rare area where sentiment was split between those treating it as a functional gap and at least one data point that tagged it under security-praise, suggesting some observers viewed even partial coverage as a positive.

With only seven total mentions across the window, the discussion sample was thin enough that individual posts carried outsized weight on the score. Still, the absence of any recorded praise themes and the late-window score decline gave the aggregated tone a notably pessimistic character.

AI-generated summary of public online discussion during this period. It reflects the tone of that discussion, not facts about the product or our views.