Sometimes we're having some issues where the caller lands into the queue instead of going directly to the extensions, so we're getting a missed call or there might be an issue with IP address level or something. That'll be honest. There are some concerns with respect to that type of integration. Aside from that, the reporting is great. It's a big-time limitation that we see today. We have contracted out to another partner of 3CX to start working on a separate instance of reporting because it is not that flexible. The partner that we are working with has quite a bit of experience in 3CX, so we don't have many pain points. Reporting and integration are the main challenges, which are at the mid-level or in the enterprise depending on the system that we choose. We have got three or four systems running 3CX and they are connected through a bridge. That's where integration becomes a challenge. 3CX has some other limitations. One of our teams totally stopped using 3CX because couldn't use it to capture the recordings of the conversations they were having with the client and also sync images on HubSpot CRM. 3CX native integration does not make it possible for us to restrict the HubSpot integration to a specific group of extensions. It can only be applied to the entire PBX or it is not applicable at all. On their own, they found another PBX system on the HubSpot marketplace that had native integration with HubSpot and just started using it. That particular system has fewer capabilities than 3CX, but then it has a very nice contemporary interface and it's extremely user-friendly. Also, 3CX no longer offers APIs. In absence of APIs, we can't do a lot of the things we would want to. For example, updating contacts is a limitation for us.
