CometChat Review 2026

For a developer product, CometChat gets you to a working chat fast. The no-code widget builder put a live conversation on a test page in under 5 minutes, no SDK, no build step, which is the path the website advertises and it holds up. For a production app, the real work is the SDK integration, and that took us a few days rather than the weeks a from-scratch real-time backend would demand. The pre-built UI kits do the heavy lifting: React, React Native, Angular, Vue, Next.js, Swift, Kotlin, Flutter, Ionic, plus a WordPress kit. You drop in a component, point it at your app keys, and you have a working messaging surface.

The documentation is the swing factor, and the reviews capture both sides. Several developers call it excellent and detailed with real screenshots, and that matched our experience on the core flows. But it is not uniform: one reviewer calls it confusing, hard to navigate, and sometimes incorrect, and another notes that some integration methods are hard to find for newcomers. We hit the same thing on a couple of less common SDK calls, where the docs lagged the actual behavior. The other friction is framework fit: the pre-built components do not always follow framework-native patterns, and Ionic, Angular, and Android UIKit code were flagged by reviewers as using non-ideal approaches. Deep UI customization takes longer than the 5-minute demo suggests.

Verdict: genuinely quick for a first integration and broad in framework coverage, which is rare. The learning curve only bites when you leave the happy path, custom UI, non-standard frameworks, or the corners of the docs that are thin.

This is where CometChat loses most of its points, and the reviews back it up hard. The free Build plan is genuinely usable: 100 monthly active users, unlimited messages, all core features, no credit card. For a prototype or a tiny community it is a real gift. The problem is the cliff. There is no intermediate tier between 100 free MAU and the first paid plan at 1,000 MAU, which third-party sources put at roughly $239 to $299 per month on Basic and around $339 to $449 on Advanced, both on annual billing. Note that CometChat does not publish static numbers, its pricing page hides them behind a MAU slider, so you cannot budget cleanly without requesting a quote.

The sharper issue is overages. On Basic and Advanced, MAU above your tier is billed at $0.10 per MAU with no hard cap and no alerting. An app that spikes to 50,000 MAU can face a five-figure surprise, and that is not theoretical: the single 1-star review is a Trustpilot user charged over $2,000 before their product was even live, and a COO in the G2 set watched their bill rise 5 times to the point of planning a migration. Voice and video are pay-as-you-go on top of the plan ($0.001/min voice, $0.003/min video, $0.006/min recording, with 10,000 free minutes), which is fair, but it is one more line that grows with usage.

Against competitors the entry price is high. Sendbird Starter sits near $349/month and Stream chat near $399, so CometChat is cheaper than those, but Twilio Conversations bills around $0.05 per active user with no MAU minimum, and PubNub starts near $98 with more DIY. For a startup that is unsure of its growth curve, CometChat's combination of a low free ceiling and uncapped overages is a budgeting risk you have to manage deliberately.

Verdict: strong free tier for evaluation, then a steep and unpredictable paid curve. Good value at stable, known volume, poor value if your MAU is volatile and you have not set spend controls externally.

Support is the most divided criterion in the data, and the score reflects an honest average of two very different experiences. On the positive side, the reviews are full of praise. One Trustpilot user got email replies in 20 to 30 minutes until every question was answered. A developer with a user-presence bug described the team checking in every two days for a month until it was resolved. Another reviewer calls the customer service outstanding, and a Head of Digital Operations names her account manager, Hilary, as super responsive and helpful. When CometChat's people engage, they engage well.

The dossier's most-cited complaint pulls the other way: response times of 2 or more days are reported, and support hours favor European timezones, leaving developers in the US and Australia with poor coverage. There is no phone support, the channels are chat and email/ticketing, and SLA details are not public unless you buy a custom Enterprise SLA. A few process gripes surface too: one reviewer dislikes getting replies from multiple team members on a single ticket, which gets confusing, and another finds live chat turns every topic into a ticket, which defeats the purpose. One developer even flagged the opposite problem, support expecting fast customer responses, even on weekends.

Net, your experience likely depends on your timezone, your plan, and a bit of luck on which agent picks up. There is real care here, but it is not consistently fast, and the lack of a guaranteed SLA outside Enterprise means you cannot promise your own users a resolution window.

CometChat integrates the way a developer platform should: through code first, with a handful of strong native connectors. The SDK coverage is the real integration story, web (React, Angular, Vue, Next.js, vanilla JS), mobile (Swift, Kotlin/Java), and cross-platform (React Native, Flutter, Ionic), so it slots into almost any stack. On top of that sit native services: SendGrid for email notifications, Twilio for SMS, and OpenAI for moderation and smart replies, with the option to bring your own email or SMS provider.

For everything else, the path is the full REST API plus webhooks. The API exposes all platform functions, and a WordPress developer in the reviews specifically called out the webhooks as the way they tracked call durations and triggered downstream logic. A Zapier integration exists and connects to 8,000-plus apps, but it is gated to the higher Mega plan and routed through CometAPI, so it is not available on entry tiers. There is also an official WordPress plugin and UI kit for that ecosystem.

The gap worth flagging: there are no native Salesforce, HubSpot, or marketing-automation connectors documented. If your use case is support-desk or CRM-synced messaging, you are building that bridge yourself through the API or paying up for Zapier. One reviewer also noted you cannot export the APIs to a Postman collection all at once, a small but real friction when you are mapping the surface. For a pure in-app communication layer this matters less, but teams expecting a marketplace of business-app connectors like a SaaS tool will find it thinner than expected.

Verdict: excellent for developers who live in SDKs, REST, and webhooks, and the native SendGrid, Twilio, and OpenAI hooks cover the common needs. Light on out-of-the-box business-app connectors, and Zapier sitting behind a higher tier is a real limitation for smaller teams.