I've had good experience with a rotating on-duty developer in at least two different companies I've been at. The developer would be the only person that CS (an

I've had good experience with a rotating on-duty developer in at least two different companies I've been at. The developer would be the only person that CS (and others) can come to with questions. He would not be expected to be very productive and would generally deal with small ad-hoc bug fixes when not acting as internal support (Which it really is). He'd also be responsible for various ad-hoc and maintenance tasks. The rest of the team would then be free to work uninterrupted on development tasks. We'd have some sort of token (a teddy bear or whatever) at the designated developers desk, so everybody would know who to go to. Of course it does cost a full developer "resource" at all times, so this probably only makes sense once your team reaches a certain size.