Great responses already here on the quality/payment side. One thing that hasn't come up yet though: the tracking side of batching call-backs.
travisshepherd You mentioned batching non-urgent ones for a specific day, that's a solid approach, but the part that usually breaks down is remembering which ones are waiting and when that batch day actually comes around. If it's living in a notebook or your memory, it's easy for one or two to slip past the batch day entirely, and that's usually when a "minor touch-up" turns into an annoyed client who feels forgotten.
What's worked well for others I've talked to: tagging call-backs as their own job type the moment they come in, so they show up in a dedicated view instead of blending into the regular schedule. That way "batch day" actually means pulling up one list instead of trying to remember who called last week.
Are you're doing something similar, or handling the tracking piece a different way?.
