Support multiple "certified" interaction models and allow to switch between them quickly
This will solve several pain points:
Developers will have full control over when the update goes live. After the certification is complete, the interaction model does not go live automatically, but is simply added to the list of "Certified" models. After that, the developer is able to switch to live model when they want. Today, the developers have no control and no good ETA for the submitted model to go live.
Instant rollback. If the new model does not perform well, the developer will be able to instantly rollback to the previous model. Today, rolling back a model takes a re-certification, which, depending on the number of supported locales, could take several weeks (with customers suffering every day).
A/B testing. If a developer is able to split the traffic between the previous model and the newly certified model, he or she will be able to compare the metrics. Of course, this would require the model ID to be passed as part of the request to the skill. Today, there is no good way to A/B test interaction models.