No I'm not trying to assign agents to pools - I just need clients in pools, then the agent can select which pool they want to work out of (I can filter views for this). Does that sound like it'll work?
Can you please clarify when you say pools how you will create that?
- What post types you create?
- What post relationship you will use?
When you say Pools, the another way to create such poos is a Pools post type and add repeating field group that holds the client information. Then you list that Pool entries which contain the repeating field group items.
For example:
- Pool 1
-- client 1
-- client 2
-- client 3
- Pool 2
-- client 4
-- client 5
-- client 6
Then you should have a post relationship between post type Pools and Agents.
But this is a whole scope - We are not Analyst here as it may work for one function but for other function it will have a limitation and so that is why I offer you the option to create a test site and play with it and go for the best feasible option. I again would like to admit that best feasible option would be to test and play by build the test site and see if thats the exactly thing you would like to go with otherwise it will be useless for you in such a way that at one point it will work as per your requirement and at another section it will not.
I have two custom post types, one for client and the other for client notes connected in a one->many post relationship. I'm going to add the pools radio to the client notes then add it to the view so users can move a client from one pool to another without updating the main client record. Then I can create a filtered view for each pool and the agents can choose which one to work from.
Just an update that I managed to work out a solution - I put the clients in to queue groups then used filters so agents can work in any number of queues. Then installed a simple chat plugin that allows them to communicate internally so they know who is working which queue.
