Ingredients
One user
One IT support geek
One email system
One Potion of BullHeadedness
Method
User sends email to Service Desk requesting change. Geek responds, explaining that this cannot be done under IT policy (see also: no), but alternatives A, B, and C are available instead.
User retorts with email, finely rewording their original request. Geek politely responds, reiterating IT policy (see also: no), and provides alternatives A, B, and C again, as per the previous email.
User consumes Potion of BullHeadedness. User retorts, again, with another rewording of their original request. User clearly believes that IT have not understood them, and are taking pains to make their request clear.
Geek responds, again. Geek has double and triple checked with the administrators responsible for this policy (in a careful measure ensuring that none of the vast acreage of available backside is exposed); Geek thus knows well that the answer is No, No, No, No, and NO. Geek endeavours to make this painfully clear in the response. Geek also provides alternatives A, B, and C, provides option D for good measure, and closes with an invitation to discuss the policy further with the administrators.
User retorts with a demand to see a paper copy of this policy.
Geek politely explains that, if user has any questions, they may discuss them with the administrators, as made clear in the previous email.
User requests that a ticket be raised in the call logging system, so that they may obtain a copy of the precious policy.
Geek responds with a finely crafted volley; Geek leaves desk, visits with the administrators, and watches them enact a phone call wherein they deliver an authoritative “no!”
User retreats from the field in high dudgeon.
Geek wins.
