How to perform a matching scenario after getting the results from an initial matching scenario?

[greychain]

In Bitrix24 I want to be able to return the extension of the person responsible for the incoming call. So I can use a matching scenario to get the ID of the responsible person. Bitrix 24 has 3 different phone matching scenarios, which are searched by LookupOrder. How do I perform a matching scenario after getting the results from an initial matching scenario?
Once I get the ID of the person that should handle this call I need to then return the extension of that user, so I need to do another matching scenario.

Are the scenarios handled from top down, so if I place my agentID matching scenario after the last of the phone number matching scenarios will it take the results returned by the phone matching scenarios?

I have tried the chain option but that seems to call the required scenario for each of the initial lookup scenarios.

 

[edossantos]

You will need to chain the scenario using the <Output/> element. But I don't understand what you will do with this extension number afterwards. The information will not be stored in 3CX, and you can't do anything with that. For example, you can't tell 3CX to transfer the call to that number.... So I don't see the point on doing this....

 

[Evolute IT]

In Bitrix24 I want to be able to return the extension of the person responsible for the incoming call. So I can use a matching scenario to get the ID of the responsible person. Bitrix 24 has 3 different phone matching scenarios, which are searched by LookupOrder. How do I perform a matching scenario after getting the results from an initial matching scenario?
Once I get the ID of the person that should handle this call I need to then return the extension of that user, so I need to do another matching scenario.

Are the scenarios handled from top down, so if I place my agentID matching scenario after the last of the phone number matching scenarios will it take the results returned by the phone matching scenarios?

I have tried the chain option but that seems to call the required scenario for each of the initial lookup scenarios.

I would do a regular contact lookup, and then, from a CFD configured as inbound routing, query the CRM using the session.ani and get that field manually. From there, you can transfer directly or if not set, send to a queue for example.

We have a base CFD built for that. It's called "CRM Routing".

 

[edossantos]

I would do a regular contact lookup, and then, from a CFD configured as inbound routing, query the CRM using the session.ani and get that field manually. From there, you can transfer directly or if not set, send to a queue for example.

We have a base CFD built for that. It's called "CRM Routing".

I understand, but in this case you don't need the matching scenario to return anything. When you invoke the contact lookup from a CFD app, there is another scenario that is used, and all the contact details are returned, which might include the information you need. If the information you need is not included, you will need to adjust the scenarios that are being used for contact lookup by CFD apps.