Recently active topics in Get Satisfaction tagged with duplicate

What should a company do if it fully acknowledges that some of it's customers have created questions on Satisfaction for it's products, but for various (legitimate) reasons it does not wish to have it's support dialog with it's customers semantically forked on Get Satisfaction from the rest of the conversation on the company's main site?

My point is, for companies that do not have the infrastructure, resources or forsight to engage with it's customer base, Get Satisfaction is a great tool. And frankly, as a customer myself, it's great to help 'push the membrane' a little when a given company point-blankly refuses to engage (you know this, it's why you created it!).

BUT there are companies that actually take such customer dialog seriously already and have invested in similar setups on their own site.

The reasonable assertion then might be that by having the conversations taking place in one place, customers benefit from the archive of answered questions and threads. If said company was to engage with users on Get Satisfaction then those threads are semantically forked and customers visiting the main site miss the good points raised elsewhere. The support cost is also raised, as duplicate threads are raised and customer service members have to monitor more sites (assume there is competition to GetSat'n too which could also have a section for same company)

You could argue that if the support is so great on-site, why did a customer(s) feel the need to create a GetSat'n site - but people do stuff just to try it out.

Bottom line: there are a small number of companies that have their support and customer discussion sorted out correctly, what is Get Satisfactions policy when such a company raises the above concern