Brad_Hoyle | 2019-08-20 07:58:34 UTC | #1
I am sending new contacts to outbound contact lists with a scoring column, however the contact list is working on a last in first out model therefore my scoring is not factored in the priority of outbound calls. The most recently added contact is first to be called.
Is there a way to re-prioritise the contact list when I insert a new record so the new record is added to the correct sequence based on its score?
anon28066628 | 2019-08-20 13:28:41 UTC | #2
See POST /api/v2/outbound/contactlists/{contactListId}/contacts. Seeing the 'priority' query parameter to true will add the prioritized contact to the front of the queue.
Note that the actual record is inserted at the end of the list. The 'priority' flag is transient - if you recycle the campaign, it has no special priority and behaves as if you'd added it to the end of the list.
Brad_Hoyle | 2019-08-20 22:39:56 UTC | #3
Thanks for the reply! So I can either add the contact to the front on the queue or the end but I can't insert it and have it prioritized to the middle of the list based on lead score?
Is there some way to insert and then prioritize the entire list? Will the recycle do this or will I risk recalling leads i have already dialed?
Brad_Hoyle | 2019-08-26 03:13:21 UTC | #4
Does anyone have a reply for this?
anon35336826 | 2019-08-26 18:24:59 UTC | #5
If you set up a contact sort (see step 21, this applies to all dialing modes), you can have your campaign sort contacts by the lead score. To enforce the lead score, you will need to recycle the campaign as well.
To prevent redialing of contacts after a recycle, you can either use a wrap-up code mapping to mark a contact or specific phone number uncallable after dialing it, or you can use attempt controls to limit the number of times a particular contact is dialed.
Peter_Dimatulac | 2019-08-27 00:24:48 UTC | #6
Hi Sean
What's the best way to automate a real-time (every few seconds) campaign recycle? I know you can create a rule to refresh based on completion % however I'd prefer to have a forced rule around x seconds.
anon35336826 | 2019-08-27 14:53:25 UTC | #7
A campaign rule can be set to recycle at a low percentage (as low as 1%), so unless the number of queued contacts is quite large, this should suit your needs. We don't allow recycling a campaign more frequently than every 5 seconds, so you may also want to set your campaign to always-running if the number of queued contacts is small. This will prevent it from completing while waiting to recycle.
That being said, we don't recommend recycling on such a short interval, but it can be accomplished via DELETE /api/v2/campaigns/{campaignId}/progress.
If you'd like to see time-based campaign rule conditions, please vote for this idea on Aha!
Mike.Chavez | 2019-08-29 20:28:17 UTC | #8
We ran into this issue and ended up just have to have a scheduled job run every "X amount of time" that recycles the campaigns. In our case we recycle our campaigns every 5 minutes to enforce our scoring column.
As already mentioned you could do this as frequent as every 5 seconds to get close to "real-time".
We also use Attempt Control to prevent calling the contacts again.
Brad_Hoyle | 2019-08-29 22:39:48 UTC | #9
Thanks Guys, we will look into a near real time refresh.
system | 2019-09-29 22:39:50 UTC | #10
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 5822