I was initially skeptical of the idea of "Tech Support: Error Unknown" but Giguere's (OP author) description intrigued me for two reasons.
First, the game narrative is novel and might appeal to industry types who only indirectly interact with CSR teams (i.e. not people who staff CSR or support but who familiar with or work in an industry that requires support). "Tech Support: Error Unknown" has the potential to create a myth structure around tech support and that is just hands down cool. :) But, the title really should move out of the realm of genericism. It should be evocative like "Tech Support Nightmares", "Bug not a Feature", or just "Error Unknown".
Second, wow what a novel idea for a game. I wonder if the procedural "adversary"/interlocutor/chatter function were abstracted if a different algorithm could be used. For example, the algorithm for "Error Unknown" would be suitable for his game but a different algorithm might be better suited for actually simulating training for companies that need to train CSR reps.
That could lead to a secondary (or primary) market of companies looking for ways to assess or train their reps.
I also wish Giguere the best of luck and will be interested to try his new game when it's available.