While I understand the desire to strengthen the connection between the AE's and QA, it would seem that the missing piece here, when functionality doesn't meet expectations, is the documentation provided to the Developer.
If that isn't spot on, thenone can only HOPE that the product that is delivered meets the expectations of the AE.
The linchpin here is the business analyst, or some "translator" between the high level view espoused by the AE, and the actual product functionality (read details) of what is desired.