We have multiple lead partitions and work spaces set up. We have leads coming in from Facebook into the Default workspace, which then are added to a shared list under the default partition. Once the lead is added to the list (shared with NZ workspace), we have a campaign under default workspace to trigger the change of partition to NZ, this seemed to be working initially but it has stopped working now.
I tried running a batch campaign to change the partition, but that didn't work either. Does anyone know what the issue is or what we are doing wrong, or a way we can set this up that would work?
Thanks a bunch!
Remember one key rules of partition/workspaces: a smart campaign located in a given workspace can only process leads accessible from that workspace. In other words, if the leads are no longer in a partition that can be accessed from the default workspace, the smart campaign will not process that lead.
This being said, I am not sure this is the problem with you. Please provide some screenshots of your workspace / partition setup and of the smart campaign, so that we can investigate further
Thanks for your response Greg, the smart campaign is in the Default workspace and the leads are sitting in the default partition as well (shared with NZ workspace).
As you can see it says this is set to affect 286 leads but once I run the batch campaign, nothing happens.
Partitions - the blurred list is shared with the NZ workspace.
The fact that the list is shared with the NZ workspace has no Impact and is in fact not relevant to your issue.
Are the leads you are monitoring part of the 285 that will be member of the SC?
In your case, you write that the default parition is shared between the workspaces, but the way we usually set this up is the opposite: we have a "global" workspace that "sees" all partitions. and I run lead assignment rules in this workspace.
Yes the leads that I am trying to move to the the NZ workspace are the 285 from the SC. The SC is sitting in the Global workspace, so technically it should see all workspaces and have no problem changing the partition to the Nz workspace, right? But this is not what's happening.
It could be, but normally, for 285 leads, that should not be a problem, unless many other things are happening in your instance.
Nope, have already checked that. Seems like all partition assignment campaigns have stopped working, so I think we will just see what support has to say.
Thanks for all your help and suggestions. I will update you when I hear back from support.
Give a last try:
Select one of the 285 leads and right click it, then manually trigger the partition change. Then look at the activity log and see what pops up.