Timeline for Buying a domain for your client

Current License: CC BY-SA 3.0

6 events

when toggle format	what		by	license	comment
Oct 13, 2016 at 14:12	comment	added	jammypeach		I don't agree with blaming it on anyone - I simply meant that it could be put down to an administrative error - in no way should the OP dodge responsibility for that, or name some poor underling to take responsibility. Just that it could help the client take the news in a way that doesn't destroy the relationship.
Sep 6, 2016 at 20:26	comment	added	PaulD		Well, I doubt from the tone of the OP they were being 'evil', and truth is always the best policy. The other day I overslept and told a meeting, that I was late to, that the traffic had been bad. The OP asked if they had crossed the line and they had. The suggestion was then made to save face a bit and I agreed. Blaming it on a junior developer comment should have had a smiley face at the end of it, Tongue in cheek comment but although the OP crossed the line, they did not mean to trap the customer or scam him, so face saving allowed IMHO. I think everyone has agreed that they should retract.
Sep 6, 2016 at 17:52	comment	added	Steve Jessop		When the question was "is this immoral?" I'm not sure that advising to falsely blame someone else for your own decision cures the problem. Probably best stick to the apology and resist the urge to cover-up ;-)
Sep 6, 2016 at 12:38	comment	added	PaulD		Agree entirely, blame it on an over zealous junior developer.
Sep 6, 2016 at 9:47	comment	added	jammypeach		+1. To save some face, the OP could word the apology to suggest there was an error and they hard started the standard setup for that client preemptively due to marking them down as a client when they're not yet... so long as this kind of thing doesn't happen again, it may help smooth things over. But please, please don't do this kind of thing.
Sep 5, 2016 at 18:57	history	answered	PaulD	CC BY-SA 3.0