whoisjohngalt — 2010-12-05T12:56:28-05:00 — #1
I have a recurring issue that I'm sure others run into.
So a client calls, and they have a "quick" question, and so I start to help without a clear (and awkward?) "you're on the clock now" statement.
Then, what I thought would be a 5 min conversation ends up to be 20 min., plus I end up do a little research and follow up via email to document what they should do. Now I'm easily up to 45 to 60 min.
To avoid this, I'd like to:
* Present a clear guideline of what/when activities are on the clock, vs. just "customer service" that they feel they're nickle and dime on.
* Have a non-awkward to state, "you're on the clock"
Any "best practices" or suggestions out there for what's worked for you?
sagewing — 2010-12-05T16:31:18-05:00 — #2
I would advise against providing client with an explicit policy, and instead trying to manage it on your end without their specific knowledge.
I usually simply tell clients that while I'm happy to answer ad hoc emails and phone calls, if there is request that requires us to 'do something' such as research, development, a quick tweak, document updates, etc. then it's billable. That is a bit vague, but it works well. The rule of thumb being, if you could fill in a distinct task on a timesheet beyond 'answering emails', then bill for it.
Then rather than tasking the client with understanding your threshold for billable work, just don't engage in the constant emails and phone calls. If a client emails me repeatedly during the day, I stop answering and get back to them in single email at the end of the day. Same with phone calls, if a client constant wants to chat I'll quickly become too busy to speak with them and ask them to schedule a meeting.
But never tell them that they are 'on the clock'