Similar to what Jim was alluding to....
To get around the issues with using Outlook on the "back-end" at all (No Outlook server side vs. client side rules processing needed, no Outlook/security/redemption issues etc.)
... if, as you say, they have provided you with an
email account, then it is probably hosted on a local Exchange server. If so, then you should be able to talk to it with clients other than Outlook.
That way, you don't have to use Outlook to see, read, and process the returned emails at all.Only the users who are sending you the requests and receiving the results would continue to use Outlook as they normally would for all their email including this stuff.
Depending on what the Exchange server makes available to you, you could use POP or IMAP (postie can do that) to talk
directly with that account.
Also, for more granular IMAP needs, if you have a newish version of WinBatch that supports CLR/.Net stuff, you can use some good 3rd party IMAP components (I have recently done something similar with an Avaya voicemail server using
https://mailsystem.codeplex.com/). Deana was very helpful in providing me with the beginnings of the .NET handling I needed... there are a couple of examples in the Tech Database.