List access per agent

All installation and configuration problems and questions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

List access per agent

Postby hashtagjet » Mon Jul 30, 2018 12:50 am

Hi,

Before I begin, I'd like to start with the big picture.

Basically sometimes, we have agents get better success with certain lists. We have multiple lists per campaign though and on a special day, we sometimes like to have x agent only call a X list from the campaign and Y agent only call Y list from the same campaign.

I can't seem to figure out the flow without creating separate campaigns per list. Is there a way I can do that without separating campaigns?

Regards,
Jet
hashtagjet
 
Posts: 30
Joined: Thu Jul 12, 2018 3:16 am

Re: List access per agent

Postby williamconley » Mon Jul 30, 2018 1:07 am

1) Welcome to the Party! 8-)

2) As you are obviously new here, I have some suggestions to help us all help you:

When you post, please post your entire configuration including (but not limited to) your installation method (7.X.X?) and vicidial version with build (VERSION: 2.X-XXXx ... BUILD: #####-####).

This IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "manual/from scratch" you must post your operating system with version (and the .iso version from which you installed your original operating system) plus a link to the installation instructions you used. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

3) To directly answer your question: No. That's what campaigns are specifically designed for: differentiating who gets what outbound auto-dialed calls. For manually dialed "territory" calls or for inbound calls you can segregate them. Unless you can turn these outbound auto-dialed calls into inbound calls or manually dialed "territory" calls, the answer is ... no.

4) Well: No without a $10k budget, essentially. And in the end, you'd have what "appears" to be one campaign, but is actually one per agent (in the background, where you can't see it). You'd be paying for a coder to make the system lie to you. It would be purely cosmetic.

5) That being said: If you wanted to invest some $$ in creating a "per list preference/ranking" system, that could be done. If more than one agent is available at the time a call is answered, the system would "prefer" agents assigned to that list over other agents. That could be done.
Vicidial Installation and Repair, plus Hosting and Colocation
Newest Product: Vicidial Agent Only Beep - Beta
http://www.PoundTeam.com # 352-269-0000 # +44(203) 769-2294
williamconley
 
Posts: 20018
Joined: Wed Oct 31, 2007 4:17 pm
Location: Davenport, FL (By Disney!)


Return to Support

Who is online

Users browsing this forum: Bing [Bot] and 69 guests