Why does OCS create SRs? OCS and our implementation partners are our largest generators of SRs. We have some very good people in OCS but we also have people with no time to learn a product. That's common across all SI and they will all lie to their customers to get the job. Sure, they are a platinum partner. Just not for xxx product. They leave that detail out. Some SI hire people who's only qualification is knowing how to call Support. Everyone likes to dump on support but when a person who was specifically hired as a consultant who is supposedly an expert does not know what they doing, they call Support for answers and for someone to blame for their inability to deliver. It all comes down to product complexity and quality and how well a company enables the people directly working with customers. I was just hearing a lot about how we have people who will be helping with their azure/oci connections. If that's so, why are they large customers with long running problems that, on face value, seem rather simple but just don't get ops attention. I think our efforts to help customers implement are disjointed and unfocused and there are probably too many groups who end up doing too little actual work. Is our field enablement and support really up to level that it should be. What do other companies do? Do we invest enough in getting our frontline support trained and provided with the tools and access to the actual hands-on experience they need? Are our process streamlined to make the customer experience of raising an sr easy? When a support person needs assistance from ops, how easy is that to get or is there pushback. Are we really focused helping customers or are we.focused on creating internal processes that end up slowing everything down because people are afraid to actually step and take.responsibilty.