What exactly are you looking for or expecting? In general, beta test feedback is always a one-way street. You encounter issues, you report them. They may or may not be fixed at some point in time. Very occasionally you will get contacted about reproducibility, but that is (by definition) something that is unlikely with stacks such as this.
I've seen a number of things appear in the beta which were disliked and subsequently disappear (the wide swings on making curb-hugging turns comes to mind). I've no idea if this was a direct result of the feedback, but its unlikely it had no effect at all.
A well designed customer facing beta test should never be a one-way street.
It should be designed to attracted detail orientated customers, and customers who are fans of the product.
The tool for reporting feedback should designed to allow a customer to easily communicate the severity of the problem, and what kind of problem it was.
- Was it a problem with an interface or control? For example I feel as if its dangerous to have Adaptive Cruise control continue to function despite using the steering wheel to disengage FSD.
- Was it a problem with the Maps/Navigation? This is such a serious problem in so many cases that it prevents FSD Beta from being full leveraged.
- Was it a problem with the base SW that doesn't even include FSD, but impacts the version of firmware installed on the vehicle. I've had Tesla's since 2015, and I've never seen so many bugs as I see now. Things that have lasted build after built as there is no good way of reporting bugs. It used to be that you could email them, but they took that away.
- Was the issue a safety one that required a disengagement or a comfort level?
If you did studies on people reporting issues/bugs I'm sure you'd see steep decline in the quality of the reports if the person doing the testing doesn't feel like anyone is listening or cares about their feedback. People enjoy finding bugs, but not when there is no one to acknowledge it. Imagine using TMC and never getting a like, a dislike, a love, or even a laugh.
The quality of my own reporting would be vastly improved if there was a Web interface for it that included the clips I clicked on so I could reference them. It would also be a lot better if they responded to suggestions even in a "Yeah, we've gotten a lot of this request and we're investigating it" kind of way.
The other thing is having some level of engagement helps guide beta testers.
Like if they said "we know we have a problem with false FCW" I would stop reporting them.
There are also cases where a persons specific HW might be at fault. The last thing you want is FSD beta customers disrupting the service centers.
That's why I would recommend regional representatives that helped filter issues, and helped with customer engagement. One of their primary tasks would be getting maps issues sorted out to enable FSD Beta owners to more fully leverage FSD. I don't know if you've seen it, but TMC has an entire thread with people trying to figure out how to get the maps updated. If I was the manufacture of the product I'd find this inexcusable because it means your customers are desperate for a fix.
