It sounds like you are looking for a prioritization algorithm.  If this is for 
a sales system, I would want to rank the callers in order of most valuable to 
least valuable.  Some sources of data might be more valuable than others, 
better leads etc.  Do you have data to support this type of sorting?  

 

Otherwise, you might want to do a hybrid of alphabetic and days since 
contacted.  You could have them pick up where they left off (middle B’s, etc).  
You don’t want them to wait until they get to the Z’s before they start over, 
but when will the Z’s be contacted?  Is there a business justification for 
going in alphabetical order?

 

One alternative also might be to let the users sort and filter to determine who 
they call in what order.  Or does the customer have ideas for what would be the 
most effective?  

 

There are a lot of variables and approaches to what you want to do, I guess my 
first question would be, above all else, What Will Make the Business the Most 
Money.

 

Hope This Helps,

 

Seth

 

From: houcfug@googlegroups.com <houcfug@googlegroups.com> On Behalf Of Mike G
Sent: Wednesday, January 23, 2019 5:27 PM
To: houcfug@googlegroups.com
Subject: Re: [houcfug] Need some discussion

 

I don't really want them to start at A every day, and when they get to Z, want 
them to be able to restart at A.  I do record lastCallAttempt and lastCallReach 
timestamps.

 

I considered querying "where lastCallAttempt gt 30/60/90 days"...but with call 
lists ranging from 100 to 50000 records, isn't dynamic enough..

 

 

 

On Wed, Jan 23, 2019 at 5:22 PM Billy Cravens <bdcrav...@gmail.com 
<mailto:bdcrav...@gmail.com> > wrote:

We do a lot of work with queues and dates and workflows. The best pattern I've 
found is to have an attached events table. That's how you exclude (or if you 
want to be able to circle back around after you've gone through the list, group 
by record and sort by min(call_date) or something like that). I wouldn't sort 
by just name; I'd sort by the date the record was added and then name.




Billy Cravens

 

 

On Wed, Jan 23, 2019 at 4:48 PM Mike G <spi...@gmail.com 
<mailto:spi...@gmail.com> > wrote:

Working solo is tough sometimes, no sounding board for ideas; hoping y'all can 
help...

 

I am working on an app for a call center and my brain is out of ideas.

 

I am trying to figure out how to make and maintain a queue for calling.

 

So, I have a caller who has a territory, say zipcode 12345.

Query the database for all of 12345 sort alphabetically and in the morning give 
them record 1. Timestamp it.

 

They make it to the middle of B..

 

Tomorrow I don't want them starting at A again..now what?

Further, when I import new contacts, I don't want them to have to wait until 
they hit Z and start over to see them.

 

So, ideas on how to build a queue? I am all idea'd out...or over thinking it...

 

TIA

 

M

-- 
-- 
You received this message because you are subscribed to the "Houston ColdFusion 
Users' Group" discussion list.
To unsubscribe, send email to houcfug-unsubscr...@googlegroups.com 
<mailto:houcfug-unsubscr...@googlegroups.com> 
For more options, visit http://groups.google.com/group/houcfug?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Houston ColdFusion Users' Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to houcfug+unsubscr...@googlegroups.com 
<mailto:houcfug+unsubscr...@googlegroups.com> .
For more options, visit https://groups.google.com/d/optout.

-- 
-- 
You received this message because you are subscribed to the "Houston ColdFusion 
Users' Group" discussion list.
To unsubscribe, send email to houcfug-unsubscr...@googlegroups.com 
<mailto:houcfug-unsubscr...@googlegroups.com> 
For more options, visit http://groups.google.com/group/houcfug?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Houston ColdFusion Users' Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to houcfug+unsubscr...@googlegroups.com 
<mailto:houcfug+unsubscr...@googlegroups.com> .
For more options, visit https://groups.google.com/d/optout.

-- 
-- 
You received this message because you are subscribed to the "Houston ColdFusion 
Users' Group" discussion list.
To unsubscribe, send email to houcfug-unsubscr...@googlegroups.com 
<mailto:houcfug-unsubscr...@googlegroups.com> 
For more options, visit http://groups.google.com/group/houcfug?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Houston ColdFusion Users' Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to houcfug+unsubscr...@googlegroups.com 
<mailto:houcfug+unsubscr...@googlegroups.com> .
For more options, visit https://groups.google.com/d/optout.

The information contained in this e-mail message may be privileged, 
confidential, and/or protected from disclosure. This e-mail message may contain 
protected health information (PHI); dissemination of PHI should comply with 
applicable federal and state laws. If you are not the intended recipient, or an 
authorized representative of the intended recipient, any further review, 
disclosure, use, dissemination, distribution, or copying of this message or any 
attachment (or the information contained therein) is strictly prohibited. If 
you think that you have received this e-mail message in error, please notify 
the sender by return e-mail and delete all references to it and its contents 
from your systems.

-- 
-- 
You received this message because you are subscribed to the "Houston ColdFusion 
Users' Group" discussion list.
To unsubscribe, send email to houcfug-unsubscr...@googlegroups.com
For more options, visit http://groups.google.com/group/houcfug?hl=en

--- 
You received this message because you are subscribed to the Google Groups 
"Houston ColdFusion Users' Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to houcfug+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to