- 08 Mar 2024
- 1 Minute to read
- Print
- DarkLight
How to report on DDI calls missed by users
- Updated on 08 Mar 2024
- 1 Minute to read
- Print
- DarkLight
This is just for DDI calls - meaning just phone numbers assigned as DDIs to users from the Phone Numbers tab.
If a call does not connect to a user, the To Natterbox User field is not populating on the call reporting record. This means you would have to report on the From Dialled Number to see who the DDI belonged it. To resolve this, you can add some apps to the DDI Calls policy to amend this.
Navigate to the ‘Routing Policies’ tab
Select the ‘DDI Calls’ policy - this is one of the default policies installed with the package.
Cut (double-click) the connector between the pink ‘DDI Numbers’ container and the ‘Connect a Call’ app.
Add an action container with a query object app and a manage properties app beneath it
Configure the query object app like this:
Name this item: Find DDI Owner
Result Set: DDIOwner
Trigger When: Make sure only ‘Records not found’ and ‘Error Returned’ are checked
Record Type: Phone Numbers
Filter results:
Number = $(E164CalledNumberIn)
AND (make sure it’s not OR)DDI Number = true
Return fields: Natterbox User
Configure the manage properties app like this:
Name this item: Update 'To Natterbox User'
Select Custom Properties
Property: To_AVS_User (this is the field label for To Natterbox User field)
Value: $(SForce_DDIOwner.nbavs__User__c)
Please note: this needs to manage the result set from the query app. To make sure it is correct, find the macro by selecting the macro icon on the field and adding from there.
After that, connect both of the red plus icons, back to the ‘Connect a Call’ app.
Please note: we recommend doing this out of working hours and testing thoroughly because it could mean calls are lost. You can export the policy or make a screenshot so you remember how it was originally configured.Then click ‘Save’.