joshuao3
Customer
- Joined
- Jan 11, 2013
- Messages
- 23
- Reaction score
- 1
I hope that a manager of some sort reads this post.
Last night I finally bit the bullet and upgraded to v15 from v11. I was pleased with everything until I clicked on a phone number in my CRM and my phone didn't ring with the usual "Make Call" on the display. I did some searching and lo and behold, it turns out that the HTTP API was dropped a few versions ago.
My first thought was, "That can't be right. HTTP APIs are what every major platform implements to make application integration easier." A bunch more googling and I felt a pit in the bottom of my stomach ball up. OMG, what a HORRIBLE situation. I read HUNDREDS of posts of people complaining that their CRM was broken now, or that they refused to upgrade to the newer versions of 3CX because of this. I can't say I blame them. The decision to not only stop developing a more robust HTTP API, but to drop it altogether... mind boggling. I can't even imagine how many clients you've lost because of this.
I implore you, please bring it back. No, do better than that! Bring it back and then make it even better. Heck, why not even flip the script and do something AMAZING--optionally post the keypresses at each IVR (along with the CID, DID, and current IVR extension number) to a URL of our choosing, and let the response of that post dictate what happens with the caller next... Holy cow, could you only imagine what kind of functionality that would create? Most people wouldn't even need the Voice Application Designer if you'd just do that one simple thing! I bet your developers could knock out an upgrade like this in half a day--another week for beta testing. Then boom, you've just released the next killer feature.
Anyhow, please bring back the HTTP API. Pretty please. (and think about my idea above)
Thanks.
Josh
Last night I finally bit the bullet and upgraded to v15 from v11. I was pleased with everything until I clicked on a phone number in my CRM and my phone didn't ring with the usual "Make Call" on the display. I did some searching and lo and behold, it turns out that the HTTP API was dropped a few versions ago.
My first thought was, "That can't be right. HTTP APIs are what every major platform implements to make application integration easier." A bunch more googling and I felt a pit in the bottom of my stomach ball up. OMG, what a HORRIBLE situation. I read HUNDREDS of posts of people complaining that their CRM was broken now, or that they refused to upgrade to the newer versions of 3CX because of this. I can't say I blame them. The decision to not only stop developing a more robust HTTP API, but to drop it altogether... mind boggling. I can't even imagine how many clients you've lost because of this.
I implore you, please bring it back. No, do better than that! Bring it back and then make it even better. Heck, why not even flip the script and do something AMAZING--optionally post the keypresses at each IVR (along with the CID, DID, and current IVR extension number) to a URL of our choosing, and let the response of that post dictate what happens with the caller next... Holy cow, could you only imagine what kind of functionality that would create? Most people wouldn't even need the Voice Application Designer if you'd just do that one simple thing! I bet your developers could knock out an upgrade like this in half a day--another week for beta testing. Then boom, you've just released the next killer feature.
Anyhow, please bring back the HTTP API. Pretty please. (and think about my idea above)
Thanks.
Josh