The support is helpful, and it’s easy to configure the full setup. The value is well aligned with what we're paying. 360Dialog provides a reliable WhatsApp infrastructure that saves us development and maintenance time while allowing us to scale our messaging and automation workflows. Overall, we feel the operational value and reliability justify the cost. Review collected by and hosted on G2.com.

Some bugs could be fixed by the user, but sometimes I still need to contact support for help. In those cases, the issue can often be resolved with a single button. Review collected by and hosted on G2.com.

What I like best is that 360dialog adds very little on top of Meta's WhatsApp Cloud API. You authenticate with one API key per channel, call one base URL, and the requests, responses and webhooks use the same format as Meta's own Cloud API. Code written against Meta's documentation works almost unchanged. You don't have to manage a separate Meta access token, because the same key also fetches media such as images, documents and voice notes.

It's fast, both to start with and in production. In the sandbox we went from getting a key to real messages delivered and read on a phone within minutes, with no WhatsApp Business account, Hub account or Meta verification needed. In production, our first template message came back with sent, delivered and read receipts within about four seconds. Later, sends from our sales tool were usually delivered within 2 to 7 seconds. We created six templates through the API, and Meta approved all six within 14 minutes. The template list endpoint shows each template as approved, pending or rejected, so we poll it every 15 minutes to catch changes.

We keep our own data. In coexistence mode, 360dialog forwards every incoming message, and every message our salesperson sends from the phone app, to a webhook we run. When we connected the number, about 9,800 messages of history, going back four and a half months, arrived at our webhook the same day.

The operational tools are good too. The /health_status endpoint shows the state of the phone number, the WhatsApp Business account, the business and the app. When something is blocked, it gives an error code and a suggested fix. The documentation is easy to read and easy to automate: adding .md to any page URL gives clean markdown, so we saved all 386 pages with no failures. Pricing is simple: €49 per number per month, with Meta's message rates passed through. Support over WhatsApp answered within minutes. When I sent detailed written questions, they answered each point in order and said plainly when something was not supported. Review collected by and hosted on G2.com.

The biggest problem is how little we can see when something goes wrong. The Hub's channel status often disagreed with what was actually happening. It showed a number as not connected while messages and media were still going through. It showed "Error / Inactive" without a clear reason. Once Meta had permanently disabled the account, /health_status kept reporting AVAILABLE, so we couldn't rely on the health check at the moment it mattered most. No webhook fires when the phone-app side of a coexistence number goes under review, support confirmed that no endpoint gives the number's quality rating, and we got no event when the account was disabled. Each time, we learned about a restriction from the salesperson's phone or from Meta, not from 360dialog.

Recovering from a restriction is slow and done by hand. After each one, 360dialog's access to our WhatsApp Business account was removed, and someone had to run "Fix Channel Setup" before we could manage templates again. Support said they cannot trigger a reconnection from their side. Their support team also said inbound messages sent during an outage would arrive once we reconnected. In our data, they did not.

Coexistence did not fully work as described. Messages we sent through the API did not show in the salesperson's WhatsApp Business app until the customer replied, and then only as a bare number. The coexistence documentation says they should appear. We asked support about this on 16 September and still had no answer on 22 September. Onboarding was hard as well. Our first support session lasted from 07:53 to 13:31 and ended with no number onboarded. The new signup flow later opened the wrong Meta variant, which has no coexistence step. Review collected by and hosted on G2.com.

I like that 360Dialog is easy to implement. I also appreciate its clean and standard API, which makes it easy to handle and connect with other systems. The fact that they offer a flat monthly rate and the freedom to use different frontends is also quite beneficial to me. Performance and AI uses. Review collected by and hosted on G2.com.

I have issues with technical support because I write to them in Spanish and the responses come in English, despite knowing that I am from a Spanish-speaking country. Also, the management panel is quite basic; it doesn't allow certain things like changing currency. Review collected by and hosted on G2.com.

We had some questions about the service’s billing; it was a bit of a struggle to get to grips with everything ourselves, but special thanks go to the support team, who showed us how it works, where to check things and which sections to refer to. The communication was great and the interface user-friendly, whilst the integration process right from the start was as straightforward as possible. Definitely recommend them as a partner! Review collected by and hosted on G2.com.

It’s not so much about 360dialog specifically, but rather that the issue as a whole was challenging to understand. The documentation is extensive, but along with the support team, they highlighted the key points that were important. Review collected by and hosted on G2.com.

What I value most is the direct access to the API and the quality of human support during business verification. As an independent operator setting up WhatsApp Business API for the first time, I encountered a verification issue with Meta that became quite complicated. The support team (Ali, Rommel, Juhi, and Amanda) followed up in several rounds, accurately pointing out what to correct in each attempt, and we ended up achieving full business approval. That level of attention was what really made the difference compared to other options I evaluated. Review collected by and hosted on G2.com.

The business verification process (PLBV) feels more reactive than preventive. Key requirements, such as the legal business name must match exactly across all documents and the website, are not communicated in advance — you find out only when Meta rejects the attempt, and only three attempts are allowed per business. A checklist prior to the first submission, with these explicit consistency points, would have avoided a complete round of back and forth. Other than that, the support was solid, but the time between responses within the same ticket sometimes felt slower than what a process with limited attempts warrants. Review collected by and hosted on G2.com.

The support, without question. We run the WhatsApp Business API in coexistence mode (native Business App plus Cloud API in parallel) for our e-commerce, and that setup surfaces genuinely tricky edge cases. Every time we raised something — coexistence quirks, webhook delivery, linked-device behavior — the 360dialog team replied fast, in plain language, and actually engaged with the technical detail instead of sending canned answers. They took our diagnostic evidence seriously and helped us reconcile the documentation against real API behavior. Number provisioning was clean and the pricing is transparent for a Meta Business Solution Provider. Review collected by and hosted on G2.com.

Honestly little on 360dialog's own side. The real friction is coexistence itself: some inbound messages sent from a customer's linked or companion devices arrive to the API as "unsupported" with no text body, so an automation can miss content that shows up fine in the native app. That's a Meta-platform limitation rather than something 360dialog controls, and to their credit they were upfront about it instead of overselling. My one suggestion would be tighter alignment between first-line documentation and support answers — we once got info from general WhatsApp support that contradicted 360dialog's own coexistence docs, and it was the 360dialog team that ended up clearing it up. Review collected by and hosted on G2.com.

The best thing about 360Dialog is how easy it is to access the WhatsApp Business API without relying on a lengthy integration process. The number registration and verification were quick, the dashboard is clear, and the documentation allows us to connect the API with our internal tools in no time. Message delivery is stable even at high volumes, and the pricing is transparent, which makes it easy to calculate costs per conversation. Support responds helpfully when any questions arise regarding templates or the status of the number. Review collected by and hosted on G2.com.

There is little to criticize. If anything, the panel interface is quite basic and a dedicated module for analytics and more detailed reports within the platform is missing, as today one has to rely on external tools. Also, the initial setup can be somewhat technical for teams without a development profile, although the documentation helps to resolve this. Review collected by and hosted on G2.com.

I like 360Dialog because of its simple and well-documented API, which allowed me to connect WhatsApp to our inbox quickly even as the only developer. The coexistence feature is great since we kept our existing number and phone app, which meant no disruption for our guests or team. The template management in the hub is super helpful as we can follow up with the guest after 4 hours and send confirmations or vouchers easily. I appreciate the clear reporting because our agents can immediately see if a message failed and why, so they can contact the guest in another way. The fair and transparent pricing with a fixed monthly plan plus a prepaid balance helps keep costs predictable for our small business. Plus, the support is really helpful, with quick, clear answers that aid in planning our next steps. Review collected by and hosted on G2.com.

Nothing, I like it better, it works for us Review collected by and hosted on G2.com.

The official WhatsApp Business API and Coexistence setup is the biggest benefit for us. We were able to keep the WhatsApp Business mobile app and chat history while connecting the same number to our CRM. The dashboard is straightforward, the API and webhook setup is practical, and the support team escalated a difficult Meta-side onboarding issue until it was resolved. Review collected by and hosted on G2.com.

Onboarding was more complicated and slower than expected. A Meta-side Coexistence issue and the payment pre-authorisation cycle caused several retries, and the HUB briefly showed no number after pairing. Support ultimately resolved the issue, but clearer status messages, better billing-state visibility, and more proactive progress updates would reduce uncertainty. Review collected by and hosted on G2.com.

What do you like best about 360Dialog?

The customer support is what stands out most. When we hit a technical wall — every template message failing with a generic "Bad request" error and zero diagnostic detail — the support team read our exact request/response data and identified the real cause (a deprecated API endpoint) almost immediately. It wasn't a canned troubleshooting checklist, it was a specific, technical answer to our specific problem. Beyond that, the WhatsApp Business API integration itself is straightforward once configured correctly, and the account dashboard (quality rating, messaging limits) gives clear visibility into account health. Review collected by and hosted on G2.com.

What do you dislike about 360Dialog?

The main pain point is error messaging on the API side. When something goes wrong with a message send, the response is often just a generic error like "Bad request" with no error code or additional detail. This made it hard to self-diagnose an issue on our end and meant we had to open a support ticket for something that a more descriptive error response could have resolved in minutes. More granular error codes or a hint pointing to the actual cause (deprecated endpoint, malformed payload, template mismatch, etc.) would go a long way in reducing back-and-forth with support for straightforward technical issues. Review collected by and hosted on G2.com.