The plugin was not explicitly designed with your use case in mind, however there are certain situations where I would expect it to work.
Let me cover the situation where I don’t think it would work: the plugin can handle 3 format scenarios
1. .blm file and associated images (unzipped), i.e many files
2. .blm file unzipped – and associated images zipped i.e. two files
3. .blm file and associated images zipped into one file
The scenario where I think it would fail is if agents send in ANY of the above, e.g. one agent sends type 2 and one agent sends type 3 – as I don’t believe there is a combination of settings that allow this.
Assume then, all agents HAVE to provide type 3 i.e. a zip file, then you can use wildcards for the blm file name *.zip. As the program polls at the frequency you set (e.g. hourly) if two files are there at the same time the the first found will be processed and an hour later the second (I have never explicitly tested this, but that is the way the wild card processing is coded – pick up the first valid file ignore others – once processed the file gets moved, so the next one would be picked up)
So as long as the agents have different file names to each other and they use the same type i.e. fully zipped it should work
With setting of *.zip for blm and polling time hourly and wait time 15 minutes then you could in theory deal with 24 different agents per day
Of course, you will also have to code your all import pro mappings to handle different agent type, if required – e.g. if agent id = xxxx the contact number = yyyy etc (I have done similar where multiple agent codes have been in the same file ) – but of course such data processing is out of scope of the plugin and is where all import pro is very useful,