Hah, this is wise... and this whole conversation is evidence that tech does need the humanities, as many of these problems could be helped if more engineers spent more time reading Kafka...
Call centres are not a creation of engineers, but of suits - exploiting people on both ends of the phone to profit for themselves. Getting engineers to read works of Kafka won't do anything to solve this problem.
The "BAMF" booking agent however has a very important role in the API which isn't spelled out here: authentication. He's basically the sudo interface, with the power to rewrite flights at will. And for whatever reason our narrator has the right kind of speaking-to-manager powers to use him as the sudo interface.
Every bulk customer service process has its "exceptions", and this is clearly one of them. The role of humans is to understand the exception and turn it into pieces which the API will accept, either through the normal interface or the sudo interface.
See also http://www.harrowell.org.uk/blog/category/callcentre/ - it's a short series, start at the bottom.
" Asymmetric legibility characterises call centres, and it’s dreadful. Within, management tries to maintain a panopticon glare at the staff. Without, the user faces an unmapped territory, in which the paths are deliberately obscure, and the details the centre holds on you are kept secret. Call centres know a lot about you, but won’t say; their managers endlessly spy on the galley slaves; you’re not allowed to know how the system works.
...
Inappropriate automation and human/machine confusion bedevil call centres. If you could solve your problem by filling in a web form, you probably would have done. The fact you’re in the queue is evidence that your request is complicated, that something has gone wrong, or generally that human intervention is required."