That sounds much more reasonable, not to mention that you won't use your email address as the single contact, rather you will set up a different one that will act as a dispatch.
- productA-support (which is really just "support@")
- productb-support
- info/hosting/privacy/twitter/etc (not all aliases are publicized, but tend to match what people would make up when attempting to send email to us)
The support aliases forward to me and to a dedicated support account. I always use the "Send As" feature so that nothing has my name on it unless you're nosy & look at the headers.
The info and other aliases go to both myself and to my partner. We both want to catch biz dev inquiries and any special snowflake requests, but I handle all support to ensure morale stays high.
If we add staff, we can add them to the groups pretty easily. Though at some point thereafter, we'd likely need some solution for determining what's been handled. It's a little hokey, maybe, but cost-to-benefit works well right now.
I actually set up multiple email addresses for support in this way on purpose, based on platform. I find I'm far more efficient if platform 1 goes into folder 1 and platform 2 goes into folder 2. No need to make giant cognitive leaps in jumping from one message to another, and you can sit down and respond to everything all at once, not interrupting your flow...you're more productive, less overwhelmed, and contacts get their answers faster (and their emails don't get buried in your overwhelmed primary inbox).
If you are a consumer Internet startup and have a single downtime, you will completely understand where I'm coming from here...