in reply to sequential file handling (again)

This is to evenly distribute email messages from customer_service@fsdf.com to salesperson1, 2, 3 etc.

Looks to me like someone may have made a couple of (bad?) simplifying assumptions:

  1. That there will always be exactly 3 salespeople available to service requests
  2. That all customer service messages are equivalent in terms of complexity
  3. That each salesperson services equivalent requests at the same rate

The approach you're taking hard-codes these assumptions.

Wouldn't it be better to provide a queue that the salespeople could take the next request from? That would let the salespeople load balance amongst themselves, and would still provide management metrics (e.g., the rate at which different salespeople absorb requests).