Freelance Writing Tip: Don’t Call People Names, Even When They Deserve It
Ever have one of those days where you just want to rip someone a new one?
Me too. Regularly.
Yesterday I was happily browsing along, applying to gigs. I sent an email to a potential client, (showcasing my rockstar writing skills) and moved on to the next job application.
Later in the day, I checked my email, to be greeted with a nasty reply about sending unsolicited email, the consequences thereof, and potential legal action.
HUH?
I fired off a quick but hateful response, pointing out that I paid for access to a list of jobs, had applied to one of them, and this was not my fault in any way. I believe the word asshole was used.
Ok, the word asshole WAS used – several times.
Then I thought better of myself, saved the email as a draft, and went to make a pot of herbal tea.
Later, feeling a bit calmer, I returned to the email.
I redrafted a polite reply <the word asshole was NOT included> explaining that I was feeling pretty upset by the situation myself. After all, I pay a yearly fee for access to writing jobs, and I had assumed that those jobs were all…um….people looking for writers.
My mistake.
List owner’s fault – not mine.
So, that was the gist of the email.
I recieved a response at the speed of lighting from the client who’s email had been on the list, apologizing for his grumpiness. Apparently nasty news in the mail and a flooded email inbox had made him a bit snarky. Again, the word asshole was used. As in, “Sorry, I was an…”
Crisis Averted.
Today, I got an email from the same gentleman, offering me work.
The moral of the story?
Don’t call people assholes. Even if they’re behaving that way – could just be a bad day.
The real moral?
Be professional in all your business communications, or it’ll bite you in the….





