HI @gs1576, you can have one robot perform many different processes, which it will process sequentially depending on how the triggers are set up.
For the scenario you described, I would have the dispatcher being set off on a time trigger, so that it runs maybe each morning or multiples times during the day, and set the job to have a high priority.
Then set up the other 5/6 processes to run on the same robot but create their trigger to be based on queue items going into their respective queues, I would also set the queues to have unique references so you the dispatcher doesn’t accidentally put duplicates in there.
Depending on the volume of tickets this should work well, the dispatcher will take priority and then each of the other processes for the specific ticket types would be triggered only if there are items to process. If there are a large amount of tickets and the robot is struggling to keep up with all of the processes then you would then scale up the number of robots, maybe putting the highest priority or highest volume tickets being performed by an extra robot to manage the workload better.
Let me know how you get on