Perhaps you can provide a few examples which may lead to some productive changes. There are KB articles which you can find detail on many subjects but do keep in mind we do offer products on 150 different markets around the world and may miss some things but I think this page is a pretty good start:
Browse Our FAQs | Interactive Brokers Hong Kong Limited
@def, OP is correct: IB's KB, FAQ, how-to pages are indeed incredibly poor. Far below the standards of what any market participant of your size should tolerate. Here are two specific areas for improvement:
1) The 'Release Notes' that accompany every new TWS update or version are simply terrible (when they appear online at all, that is). Simply put: every single time TWS or the API software is updated, there needs to be a page explaining what has changed. I've lost track of how many times I've contacted support to ask why some feature no longer works, only to have them respond "
oh yeah, we removed/changed that in the last release". I ask where I can read about what changes were made, they poke around for a bit and then come back saying "
hm, I guess we didn't create a Release Notes for this version." (Translation: changes are documented
nowhere; there's literally nowhere online for users to read what's new or different.) This is software development 101. I understand that you have 3 versions of TWS: Stable, Latest, and Beta. But again: That's. The. Job. Keep a single Release Notes page. And every time any of those versions get updated -- even if it's just a small technical bug fix -- you document it on a Release Notes page.
2) Your KB pages are rife with links that lead to deprecated versions of the software and APIs. Again: I've spoken with support a dozen or more times about various issues, they've pointed me to a page with relevant information, and I'll send them a link to a different KB page that directly contradicts it. They'll usually respond with "
oh yeah, that actually pertains to a prior version; ignore it, and use the page I sent you." OK, all good and well, but you need to actually
remove the deprecated pages altogether. I get it: many markets! Many languages! Many websites! Again: That's. The. Job.
This is fundamental stuff. It's not like IB is, you know, a restaurant with a crummy website -- they're in the good food business; a buggy website isn't great but it's only tangential to their primary offering.
You're a discount brokerage whose chief product is customer-facing software. Fixing UX stuff like this should be at the very top of your list of priorities.