This is actually a really, really good question!
When companies deliver beta software to the outside community, that always comes with a clear mechanism for filing bug reports. Many companies also support online forums where beta testers can compare notes.
During beta testing, companies will also notify the testers of what has changed in releases, and will often ask them to test certain areas and provide feedback, to verify new changes added to the software.
These mechanisms help the company identify problems in the beta software and quickly correct them, while the software team is actively working on that code.
That's not what Tesla does...
Tesla marks most of their software as "beta" - and instead of actually running beta tests, they appear to be doing this as a way to indicate the software is not fully baked - is missing obvious features and will likely have obvious bugs.
I've participated in many beta tests - and provided high quality bug reports. I used to do that with Tesla - methodically reporting each problem I encountered, when possible, providing enough information so they could reproduce the problem or look for it in our car's logs.
And, I've given up on doing that - because problems that were reported years ago still haven't been fixed - and Tesla provides no confirmation that the bug reports are actually going anywhere.
There's likely a high percentage of Tesla's current customers who are willing to be beta testers (beyond the small hand-picked group of beta testers Tesla is using - and who seem to miss many bugs during testing). And we're willing to provide Tesla quality feedback to help the find and correct problems.
But we don't have any mechanism for doing that...