The enterprise support channel's internal process for escalation is often opaque, but from my experience, product teams do review aggregated forum links when a ticket is tagged for technical review. The link serves as an evidence appendix, demonstrating that a workflow issue is not an isolated incident. A support rep might not validate the link themselves, but they will include it in the escalation package.
For your specific case about generation parameters, I'd recommend creating a detailed forum post first. Structure it with a clear problem statement, your CI/CD context, and the quantifiable impact on your pipeline as others have suggested. Then, when you open the enterprise support ticket, reference the forum post URL and explicitly note that it documents a pattern affecting pipeline efficiency. This creates a closed loop between public demand signaling and a formal, trackable ticket.
Agreed on the closed loop, but you're still relying on the internal escalation process to function. That's the weakest link.
My experience is that you need to make it easier for the first-line rep to escalate. Don't just "reference" the forum post. Quote the specific metrics from it in the ticket description and attach a screenshot of the post itself. They copy-paste the whole thing into the escalation form. The link is a bonus.
Also, if you know the exact product or engineering team name from a public roadmap, include that in the ticket title. Makes routing less of a guess.
Trust but verify, then don't trust.
That's a great list of channels you've identified. I'm in a similar situation trying to provide feedback on workflow integration, but from a project management angle with Jira and Asana.
You mentioned the official in-app feedback form. I've used it for a few UI suggestions, but I never received any confirmation it was logged or reviewed. Has anyone actually gotten a follow-up through that method, or is it more of a sentiment gauge? Compared to something like Linear's public roadmap, that process feels a bit opaque.
For the enterprise support route, do you know if the effectiveness differs between having an Adobe Creative Cloud for teams plan versus a full Adobe Experience Cloud enterprise agreement? I'd assume the latter gets more direct access to technical account managers who could escalate.
Forget the forums for actual feature resolution. They're a voting booth, not a support channel.
Your best bet is the enterprise support ticket, but *only* if you frame it as a cost-to-them issue. Like others said, quantify your extra API calls. Then go a step further: calculate the extra infrastructure load *Adobe* incurs because your workaround requires polling or multiple generations. Tie your technical snag directly to their scaling inefficiency.
The in-app feedback form is a black hole for metrics. Save it for UI complaints.
show the math