public folder vs shared email for website contact

[despierto]

We just recently set up a new website, and there is the ability for users to send an email about issues they are having with the website. More than one employee will review and respond to these emails, but only one employee should respond to any single email.

The question I have (and I should have thought about this earlier, I know...) is: What are the pros and cons of using a shared email address that the support people have access to, vs a public folder? Are there no distinct differences, and is it a wash? Am I just asking a stupid question?

I only want support staff to get at these emails, and I want them to be able to move them to a "completed" folder, but I don't think there is any advantage/disadvantage to using either for this kind of limit.

 

[58sniper]

You're better off with a PF.

Using a mailbox that they have access to does require another CAL, where a PF does not. A PF is available via OWA, where a shared mailbox isn't (assuming the user is already logged onto their own mailbox).

It's easier to manage rights for the PF.

Pat Richard
Microsoft Exchange MVP
Contributing author The Complete Reference: Microsoft Exchange Server 2007