Obtaining phone source number used to make outbound calls

Hello,
There are multiple phone numbers that we would use in a number pool to perform predictive dialling in outbound campaigns. I would like to obtain the following

  1. Phone source number used to connect to the person we are dialling
  2. Phone number displayed on phone when user receives the call

This will help us do analysis related to connection rates on the source phone number level.
Not sure if this is retrievable in any APIs? Thanks!

You should be able to obtain this from POST /api/v2/analytics/conversations/aggregates/query grouping by participantname, ani, outboundcampaign, outboundcontactid, outboundcontactlistid with a filter criteria of whatever campaign or contact lists you're interested in and a direction of outbound and purpose of outbound. You'd have to have to a lookup to translate the GUIDS to their text but if your volumes are small enough you can probably add conversationid to the group by to see call by call results rather than true aggregates and throw in whatever metrics you're interested in.

If you want more raw detail you can POST /api/v2/analytics/conversations/details/query with similar filters and mine those elements from the raw conversation tree.

Hello Rios, quick check: If we have many numbers put in a single SIP trunk, would this way of filtering still work?

I currently send many numbers up on the contact list tied to an outbound campaign and these are being dialed by randomised numbers which could encompass one more more SIP trunks. Within each SIP trunk, there are multiple numbers put in the same pool, randomised by Telco

The 'From phone number' used by telco to call the targetted phone numbers, is this information passed back to Purecloud by any chance?

Unfortunately I can't answer that, only your telco can.

They're either transparently passing back the real ANI from the pool or using a vanity ANI so all callbacks go to your preferred number. If the ANI isn't capturing it you can also check the dnis to see if it's capturing there in an outbound, but those are the only two places I can think of to look for it.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.