First, you have to provide really bad support when a company's website goes down. This includes, but isn't limited to the following:
- Take four days to call back after multiple emails and voicemails with no valid reason for doing so.
- After switching webhosts, take a few extra days to provide company with updated DNS address after moving webhosts.
- Take another week to provide new FTP information.
- Claim that the problem with emails coming through from the website lies with your client's email server.
- After having explained to you why the problem doesn't and can't lie there by your client's MIS, argue for two days with your client's MIS through email and phone conversations.
- After doing research admit the problem isn't with your client, but rather, with you not moving everything over to the new webhost properly.
- Don't fix the problem correctly on the first two tries.
Secondly, after finding out that the client is starting to look for a new webmaster, beg for forgiveness but don't accept any blame yourself. Throw your fellow employees under the bus.
Thirdly, schedule a meeting with the client's MIS to discuss lack of satisfactory service. Show up 30 minutes late without calling him.
Anyone looking for a webmaster job?
August 29, 2006 at 9:04 am
[...] There’s many things that I regret that I didn’t bring up during my hiring negotiations. I wish that I had negotiated an extra week of vacation, and I also wish that I had the authority to dump our webmaster without having to get approval from the owner. By the way, yes, this is the same guy. [...]