" /> Creating a Follow-Up Calling List - Genesys CTI User Forum

Author Topic: Creating a Follow-Up Calling List  (Read 3186 times)

Offline JTL

  • Full Member
  • ***
  • Posts: 123
  • Karma: 2
Creating a Follow-Up Calling List
« on: July 24, 2013, 02:32:34 PM »
Advertisement
Hopefully a simple request, but some advice needed!

We are dialling customers, and a percentage of the "Updated -> Answer" records will have an additional custom field (e.g. Follow-Up) set to 1 if we want to follow-up, or 0 if we don't.

Previously, when following up, we've done a largely manual process - exported the original Calling List, reset to "Ready" and "Unknown Call Result", reset "attempt" to 0, and then imported to a different Calling List of the same format (actually in a different Campaign too as we want to do these as Preview not Predictive) and processed the calls.

That works quite well, but is slow and relies on a lot of manual intervention, so I'm looking for a way to automate it as much as possible.

I think the most complex way would be to have the Agent Desktop use the "AddRecord" to add a new record to a new Calling List - but from what I could make out, this is usually (only?) used to add records into the same Campaign / Campaign Group - and we actually want to add records to a completely separate List. So I want to avoid this route...

The other way I considered was having a Stored Procedure running on a Schedule on our DB. This would run every X minutes and would:

- look for all records in the table for Calling List A with follow-up = 1
- insert them into the table for Calling List B, changing the record_status and call_result accordingly
- update each of these records in Calling List A, setting follow-up = 2 (to prevent them being inserted more than once)

The final suggestion (though I've never written one) was to use a DB Trigger - so that when the record was written to the table for Calling List A (follow-up = 1) this triggered a new record to be written into the table for Calling List B, in a similar way to the above.

Does anyone do any of these methods, and can give any pros / cons?

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Creating a Follow-Up Calling List
« Reply #1 on: July 24, 2013, 04:05:13 PM »
Well the pro/cons will depend on your infrastructure, time to deploy, time to modify, etc.
All are valid approaches. Even you could add a record using IRD on LOADED campaigns. But again all Pro/Cons will be dependent exclusively on your environment. For example, I tried the IRD add record, works but then couldn't apply it because a business CON. But for someone else it would have worked with other environment probably.

Offline smile

  • Sr. Member
  • ****
  • Posts: 286
  • Karma: 6
Re: Creating a Follow-Up Calling List
« Reply #2 on: July 25, 2013, 12:29:00 PM »
we have similar task, but i decide to use another solution. I'm planing to run scxml strategy on ORS (or it can be done on URS as well) and set trigger on event on call released. Then this strategy will collect all userdata from call and check the business result field (followup in your case). In case of =1, scxml make request to http OCS interface to add record into new call list.
I think this solution is more flexible and easy to support rather than triggers on db.

Offline JTL

  • Full Member
  • ***
  • Posts: 123
  • Karma: 2
Re: Creating a Follow-Up Calling List
« Reply #3 on: July 25, 2013, 02:09:10 PM »
[quote author=smile link=topic=7917.msg34664#msg34664 date=1374755340]
we have similar task, but i decide to use another solution. I'm planing to run scxml strategy on ORS (or it can be done on URS as well) and set trigger on event on call released. Then this strategy will collect all userdata from call and check the business result field (followup in your case). In case of =1, scxml make request to http OCS interface to add record into new call list.
I think this solution is more flexible and easy to support rather than triggers on db.
[/quote]

I did think of scxml and advanced treatments, but I'm not quite there with those yet...

In the end, I decided to go for the Stored Procedure route, which sets a new record_id and chain_id to be the next in series in the new Calling List, and resets attempt, call_time, campaign_id etc, and it resets my custom field to "2" in the original calling list, so that the records aren't duplicated.

Works ok :)