Solved Custom CRM integration

[Kristy_jbe]

Hi,


I try to configure out a custom CRM solution with the 3CX application (XML generator?) and i'm facing some difficulties. I'm only interest in the call journaling feature currently.

My goal is to display a "pop-up" on my CRM with the client information in. This pop-up was working historically with our old VOIP solution with some custom VBscript.

First of all, is there a condition on the contact lookup to run the "call journaling" ?

My tests prove me that if the contact lookup is KO, i never see an API call on my tools responsible of displaying the "pop-up". Is that the normal behaviour?


Secondly, when the contact lookup is OK (i hardcode it for the test) i have my "call journaling request" but this request happen at the end of the call and not at the begginning. Is that a miss-configuration on my side or is that just the way it should work?

In my CRM we tape the duration of a call, so i want the "call journaling request" to be post at the start of the call, is that possible?

Thanks for you help, if needed i can send you the XML i generated but i will hide my organisation information obviously.

 

[Evolute IT]

The way the integration works does require a Contact Lookup. This is done by a REST API or database access and only then, you can use the call journaling, as it requires a contact to log into. The journaling does happen only at the end because of the fact that it is when you have all the call details.

The popup itself is opened by the 3CX Webclient/Browser Extension, not by your CRM. Note that this requires the CRM to be web-based.

If your CRM is a Windows app, you'll need to use the TAPI integration with the 3CX Windows Client.

 

[Kristy_jbe]

Hi,

Thanks for you reply, you answer on all my questions.

I think there is a little missunderstand on the "pop-up" subject i have a specific pop-up on my CRM which appear from the call journaling request, i wasn't speaking about the 3CX webextension.

Anyway, thanks !

P.S: i didn't find the way to mark this post as "SOLVED".